FleetThe open-source alternative to GitHub · Vercel
Every Claude Code session on your computers, also inside Orca, shows up as a card with its status, its pull request and its deploy. Answer an agent from a chat and it gets your message the next time it stops. Reads GitHub and Vercel, never writes to them.
Fleet, inside.
fig. 1 · fleet, interactive viewTry Fleet
Everything your agents are doing.On one board, live.
A card per agent session
Working, waiting for you, done or failed, with the last thing it said, its folder and branch, and the pull request and deploy of that branch. Grouped by project, with filters.
Now, at a glance
How many agents are working, how many are waiting for you, open pull requests, failing checks and deploys in progress. The board updates live as the hook sends events.
Several GitHub accounts
Connect accounts and organizations with read-only tokens and pick the repositories. Open pull requests with author, checks, auto-merge and conflicts, recent workflow runs and releases.
Several Vercel teams
Deploys from every account and team with their state, branch, commit and pull request, and the deploy that serves production in each project.
Talk to your agents
Each session is a WhatsApp-style conversation with your prompts and its answers. Reply and the Claude Code Stop hook hands your message to the agent, with ticks for queued and delivered.
In Inbox, Lines and on your phone
An Agents row at the top of Inbox and Lines, and an optional WhatsApp message to yourself when an agent finishes or waits for you. Reply quoting it and the answer goes to that agent.
How it works.
Install the hook
One command per computer. It keeps your other Claude Code hooks, Orca's included.
Connect GitHub and Vercel
Read-only tokens, as many accounts and teams as you use.
Watch and answer
Cards update live, and your replies reach the agent when it stops.
Fleet next to GitHub · Vercel.Our count, capability by capability.
parity with GitHub · Vercel
58%of what GitHub · Vercel does, by our count
- Included
- 5
- Partial
- 4
- Missing
- 4
We measured 13 GitHub · Vercel capabilities: each one we have scores 1, a partial one 0.5 and a missing one 0, with double weight for the core ones; this is our own assessment, checked against the code on November 15, 2026. See the changelog
- GitHub65%
- Vercel60%
- Local agents0%
- Board and platform50%
Everything Fleet includes16
[x] Included[+] Better[~] Partial
| Capability | Fleet | GitHub · Vercel |
|---|---|---|
| GitHub | ||
| Open pull requests with author and branch | Included | GitHub · Vercel: Yes |
| Checks status of each pull request | IncludedThe combined status of the last commit. Individual check names and logs are not shown | GitHub · Vercel: Yes |
| Auto-merge and mergeable state | Included | GitHub · Vercel: Yes |
| Recent workflow runs | PartialThe last 10 runs per repository, without logs or jobs | GitHub · Vercel: Yes |
| Releases | PartialThe last 5 per repository | GitHub · Vercel: Yes |
| Instant updates from GitHub | PartialEvery 5 minutes and on Refresh. No GitHub webhooks yet | GitHub · Vercel: Yes |
| Several accounts and organizations together | Better | GitHub · Vercel: No |
| Vercel | ||
| Deploys with state, branch, commit and pull request | Included | GitHub · Vercel: Yes |
| Which deploy serves production | Included | GitHub · Vercel: Yes |
| Several accounts and teams together | Better | GitHub · Vercel: No |
| Local agents | ||
| Claude Code sessions with live status | BetterThrough a hook installed with one command, also inside Orca | GitHub · Vercel: No |
| Answer an agent from a chat | BetterDelivered by the Stop hook when the agent stops, or with the next prompt | GitHub · Vercel: No |
| WhatsApp message to yourself, and reply from it | BetterThrough the WhatsApp you connected in Inbox | GitHub · Vercel: No |
| Board and platform | ||
| A board of everything in progress | Better | GitHub · Vercel: No |
| Notifications | PartialWhatsApp to yourself. No email or push yet | GitHub · Vercel: Yes |
| Run it on your own server | Better | GitHub · Vercel: No |
Where we go further
- Several accounts and organizations together
- Several accounts and teams together
- Claude Code sessions with live statusThrough a hook installed with one command, also inside Orca
- Answer an agent from a chatDelivered by the Stop hook when the agent stops, or with the next prompt
- WhatsApp message to yourself, and reply from itThrough the WhatsApp you connected in Inbox
- A board of everything in progress
- Run it on your own server
Still missing (4)
GitHub · Vercel has these and we don't yet. If you need one, vote for it on the public board.
- Review, comment, merge or close from the appVote on the board
- Build logsVote on the board
- Redeploy, promote or roll backVote on the board
- Other agents (Codex, Cursor, cloud routines)Vote on the board
Fleet questions.Migration, limits and API.
What does the hook send from my computer?
The event type, the session id, the folder name and git branch, Orca's ids when present, and your prompt and the agent's last message cut to a few thousand characters with common secrets removed. Never file contents, full paths or the transcript.
Does it work with Orca?
Yes. Orca runs Claude Code with its own hooks, and Claude Code runs every hook of an event, so both work at once. When the agent runs inside Orca, sessions carry the pane and worktree.
How does my reply reach the agent?
It waits in a queue. When the agent finishes its turn, the Claude Code Stop hook asks Fleet for queued messages and, if there is one, tells Claude to keep going with it. If you write while it is idle, it gets it with your next prompt.
Can Fleet change my repositories or deploys?
No. It reads pull requests, checks, workflow runs, releases, projects and deploys with the tokens you give it, and never writes to GitHub or Vercel.
Who sees my agents?
Only you. Tokens, sessions and conversations belong to your person in the workspace, and the ingest token is stored as a hash.