Choose the work
Start with a ticket or a prompt. Pick the repository and agent.
FLEET EARLY ACCESSRun in parallel.
Run in parallel.
Stay in control.
The desktop workspace for developers running Claude Code and Codex. Move tickets from first prompt to reviewed code, without losing the thread.
Explore the demo ↗ INTERACTIVE PRODUCT TOURSimulated workspace · 4 work items
Work4 items
ORB-142 / orbit-web
Add keyboard navigation
In review1 workstream · 1 agent sessionClaude CodeLatest exchange
Arrow keys move between results; Escape closes the command menu. Implementation and tests are ready for review.
- Repository
- orbit-web
- Branch
- feat/orb-142
- Workspace
- Isolated git worktree
- Verification
- 12 tests passed · typecheck passed
Open Activity for the session trace, or Review diff to inspect changes.
Find what needs you. Follow a session. Review changes and queue feedback.Based on Fleet’s desktop workflow.
YOUR TOOLS, WORKING TOGETHER✳ Claude Code⌘ Codex⑂ Your repositories◈ Your workflow
Product preview · illustrative workspace with synthetic data
FROM INTENT TO LANDED CODELess juggling.
Less juggling.
More moving work forward.
A clear place for the work, the agents doing it and the decisions only you can make.
Run in parallel
Give each change an isolated worktree and watch its progress.
Keep the judgment
Answer questions, inspect diffs and send focused feedback.
Verify and land
Use checks and configured gates to move reviewed work forward.
A WORKSPACE THAT HOLDS THE CONTEXTYou steer.
You steer.
Fleet keeps the work in view.
Noticing what needs you is part of the workflow.
◈ Orbit1 needs input
◇ Developer tools2 building
◇ Infrastructure1 in review
More projects.
Less context switching.
Keep repositories, work items and project defaults together. Return to the work and its decisions, even after an agent session ends.
⑂ Branch review+24 −8
+ await verifyChanges();
+ return result;↳ Add a test for the empty response.
See the change.
Make the call.
Read branch diffs alongside the conversation. Send specific feedback and use local verification to inform your next decision.
Build ✓
Review ✓
Land ◈
PR checks and feedback stay attached to the work.
Keep PR follow-up
from becoming a job.
Watch checks and review feedback after a build. Fresh landing sessions continue the work, with configured gates and conflict recovery.
More ways to keep work moving
Queue the next steps
Use queued prompts, flows and scheduled launches to prepare follow-up work. Launch readiness and permissions still apply.
Move around quickly
Use the command palette and bulk session actions to supervise work without opening every conversation.
Automate with boundaries
Mapped autopilot can launch eligible tracker work using configured repositories and conventions. Keep verification and landing gates explicit.
Keep usage in perspective
Inspect available agent usage and spend history. Values depend on the provider and are not invoices or hard budgets; Codex cost estimation is planned.
BEYOND A WALL OF TERMINALSParallel is easy to start.
Parallel is easy to start.
It’s harder to supervise.
Keep using the agents you know. Add a workspace that connects their output to the work you’re trying to finish.
See the workspace in action ↗A place for every change
Projects, work items and isolated branches.
A signal when you’re needed
Questions, review states and early overlap notices.
Context that outlasts a session
Conversation history, handoffs and PR watching.
BUILT AROUND REAL REPOSITORIESDifferent hats.
Different hats.
The same need for control.
For solo builders, technical leads and the people who keep software working.
Ship the backlog
Run a feature, a bug fix and a refactor in separate worktrees.
Turn findings into fixes
Reproduce a regression, add a test and review the patch.
Review infrastructure changes
Update CI and deployment configuration with repository checks.
Remediate with context
Review a reported finding and supervise a targeted code change.
THE DIRECTION AHEADMore connected work.
More connected work.
Still your call.
Planned capabilities, separate from the current product. No promised delivery dates.
One launch. Multiple repositories.
Coordinate a change across the frontend, API and infrastructure.
Agents that coordinate the edges.
Negotiate ownership and interfaces, then verify the combined result.
A shared view of team work.
Bring cross-person visibility and overlap awareness to the workspace.
Explore more of what’s next +
Also planned: broader browser/app evidence, session templates, existing-session import, hard session budgets, Codex cost estimation, finer notification routing, automatic build closure after PR creation and workstream grouping across more views.
KNOW WHAT YOU’RE STARTINGYour workspace.
Your workspace.
Clear boundaries.
Local worktrees and a local working database. Optional cloud sync. Agent context goes to your chosen provider under its settings and terms.
Bring alongGit + a local repositoryClaude Code or Codex, installed and authenticatedYour own agent subscription or usage billing
A few good questions.
When can I try Fleet?
Join the waitlist and we’ll email you when early access is available. There’s no announced launch date yet.
What am I signing up for?
An early-access invite to Fleet. We store your email address, signup time and where you joined on this page in Supabase. Joining does not create an account or start a paid subscription.
What will I need to use Fleet?
Git, a local repository and an installed, authenticated Claude Code or Codex CLI. You bring your own agent subscription or usage billing.
Can I use Claude Code and Codex together?
The current app supports both in the same workspace, with agent/model switching and usage-limit handoff. Each provider needs its own supported authentication. Models and usage limits depend on your provider account.
Do I need a ticket tracker?
No. Start with a prompt and repository. Configured Jira, Linear, GitHub Issues and Notion connections can bring ticket context into your work; their capabilities depend on the adapter and permissions.
How much control do I keep?
Review questions and branch diffs, send feedback and configure verification and landing gates. Automation depends on your settings, provider permissions and repository checks. Overlap notices do not replace reviewing the combined changes.
Your next few tickets.
One place to move them forward.
Fleet is getting ready for early access. Get an invite when it’s your turn.
Explore the demo ↗