How jp290/claude-fleet works
Claude Fleet is a self-hosted browser dashboard for coordinating persistent coding-agent sessions. The main workflow is owner authentication, session or task creation, isolated lane execution, then server-controlled rebase and verification before landing; optional post-land audits and conflict review extend that lifecycle. The graph retains documented UI, adapters, queue/program, sharing, and remote-helper capabilities. Sampled server and helper code support selected connections; unsampled capability wiring is kept conservative.
Main entry points: server.ts HTTP and WebSocket server · proc.ts Isolated lanes · daemon.ts Pull-based helper daemon · client.ts Fleet dashboard UI
Components 25
Dashboard and access
- HTTP and WebSocket server
server.ts - Token and share auth
server/auth.ts - Fleet dashboard UI
src/client.ts - Read-only share UI
src/share.ts - Share service
server/transport.ts
Agent execution
- Persistent slots
server/tmux.ts - Agent harness adapters
server.ts - Isolated lanes
server/proc.ts - Transcript and conversation
server/transcript-read.ts
Task delivery
- Task queue
server.ts - Lane dispatcher
server.ts - Supervising programs
server.ts - Rebase and land gate
server.ts - Verify command
Review and support
- Post-land audit
server.ts - Conflict and lane review
merge-prompt.ts - Lane outcome ledgers
server/persist.ts - Remote helper portal
server.ts - Pull-based helper daemon
helper-daemon/daemon.ts
Other components
- Owner
- Git repositories
- tmux
- Agent CLI
- Verify suite
- Remote helper machine
Connections 29
- Owner → Fleet dashboard UI: uses
- Fleet dashboard UI → HTTP and WebSocket server: API requests
- HTTP and WebSocket server → Token and share auth: checks access
- HTTP and WebSocket server → Persistent slots: manages sessions
- Persistent slots → tmux: controls sessions
- HTTP and WebSocket server → Agent harness adapters: starts agents
- Agent harness adapters → Agent CLI: spawns
- HTTP and WebSocket server → Isolated lanes: creates worktrees
- Isolated lanes → Git repositories: checks out branches
- HTTP and WebSocket server → Transcript and conversation: reads output
- HTTP and WebSocket server → Task queue: files and releases
- Task queue → Lane dispatcher: released tasks
- Lane dispatcher → Isolated lanes: starts lanes
- HTTP and WebSocket server → Supervising programs: supervises
- Supervising programs → Task queue: files tasks
- HTTP and WebSocket server → Rebase and land gate: runs land
- Rebase and land gate → Git repositories: rebases and advances
- Rebase and land gate → Verify command: runs command
- Verify command → Verify suite: executes
- Rebase and land gate → Conflict and lane review: routes conflicts
- HTTP and WebSocket server → Post-land audit: schedules audit
- Post-land audit → Git repositories: audits main
- HTTP and WebSocket server → Lane outcome ledgers: records outcomes
- Read-only share UI → HTTP and WebSocket server: requests shared view
- HTTP and WebSocket server → Share service: serves sharing
- Share service → Token and share auth: checks share access
- HTTP and WebSocket server → Remote helper portal: serves helper jobs
- Pull-based helper daemon → Remote helper portal: pulls jobs and reports
- Pull-based helper daemon → Remote helper machine: runs suite remotely