Open source · macOS / Linux / WSL2

One terminal.
A whole fleet.

Give each coding agent its own worktree. Run Claude, Codex, and OpenCode side by side, and keep their sessions alive after you close the window.

npx ghostfleet-cli
Have your coding agent set it up.
Read the setup prompt
Install ghostfleet (https://github.com/PabloG55/ghostfleet) for me and set it up the way I want.

Before running anything, ask me these in ONE numbered list, with your recommended default in brackets, and wait for my answers:
1. Install missing dependencies (tmux, jq) for me? This may use brew or sudo apt. [yes]
2. Jarvis (experimental): one session above every project's lead that I can type or talk to from my phone. Enable it? [no]
3. If Jarvis: voice input with whisper.cpp plus a speech model, about 550 MB, transcribed locally? [no]
4. Kokoro, a natural voice (about 350 MB) for reading replies aloud on the phone, falling back to the phone's own voice if I say no? [no]
5. fleet-shots (experimental): record a flow as video with the request behind each step, so I can review it? [no]
6. Do I want the fleet on my phone (uses Tailscale)? [later]
Only if $EDITOR is unset AND nvim isn't installed, add: which terminal editor should Ctrl-N open (nvim, vim, hx, micro, nano, emacs -nw)? [nvim]

Then:
- Run `npx ghostfleet-cli --yes` if I said yes to 1, otherwise `npx ghostfleet-cli`. The --yes goes AFTER the package name.
- Then run only the steps I said yes to:
  2: fleet-experimental enable jarvis
  3: fleet-jarvis voice --install
  4: fleet-jarvis voice --kokoro --install
  5: fleet-experimental enable shots
  6: run `fleet-phone` and walk me through the one next step it prints
  editor: add `export CLAUDE_FLEET_EDITOR=<editor>` to my shell rc and tell me which file you changed
- Never launch the interactive `ghostfleet` screen yourself (it needs a real terminal and will hang). When you're done, tell me to run `ghostfleet` in my terminal.
- Finish with what got installed, what you skipped, and any warning the installer printed. Quote the warnings; don't summarise them.
ghostfleet · Claude / OpenCode / Codex

Actual Ghostfleet session · three interactive agents, visible at once.

Parallel work without losing the thread

Different tasks.
Room for each one.

Worktrees, not collisions.

Each agent gets an isolated Git worktree. Keep tasks on separate branches instead of asking multiple agents to edit the same checkout.

Sessions that stick around.

Per-project tmux sessions keep your terminals alive. Close a window, come back later, and reconnect to the work already in progress.

See the whole fleet.

Stack interactive agents in one view. Watch their output, answer a question, or switch focus without hunting through terminal windows.

From a task to a working session

Give the work
its own workspace.

Create a worktree, launch an agent, and return to the project when you need to. Reuse existing worktrees and keep your sessions tied to the repository.

Resource and budget controls help you manage a growing fleet.

Your fleet, away from your desk

An agent is waiting.
You don’t have to be.

The mobile web app brings session chat and terminal access to your phone. Check progress, answer an agent, and unblock a task without returning to your computer.

Set up mobile access

Before you launch.

Which agents can I use?

Claude, Codex, and OpenCode are supported. Install and authenticate the agents you want to run; Ghostfleet organizes their sessions.

What do I need installed?

Node.js, Git, tmux, jq, and curl. The repository setup guide covers prerequisites and configuration.

Does it work on Windows?

Use WSL2. Ghostfleet supports macOS, Linux, and WSL2; native Windows is not supported.

Can I try the interface first?

Use ghostfleet demo after installation to explore its demo mode. The source and setup instructions are available on GitHub.

Give your agents a home.

npx ghostfleet-cli
Have your coding agent set it up.
Read the setup prompt
Install ghostfleet (https://github.com/PabloG55/ghostfleet) for me and set it up the way I want.

Before running anything, ask me these in ONE numbered list, with your recommended default in brackets, and wait for my answers:
1. Install missing dependencies (tmux, jq) for me? This may use brew or sudo apt. [yes]
2. Jarvis (experimental): one session above every project's lead that I can type or talk to from my phone. Enable it? [no]
3. If Jarvis: voice input with whisper.cpp plus a speech model, about 550 MB, transcribed locally? [no]
4. Kokoro, a natural voice (about 350 MB) for reading replies aloud on the phone, falling back to the phone's own voice if I say no? [no]
5. fleet-shots (experimental): record a flow as video with the request behind each step, so I can review it? [no]
6. Do I want the fleet on my phone (uses Tailscale)? [later]
Only if $EDITOR is unset AND nvim isn't installed, add: which terminal editor should Ctrl-N open (nvim, vim, hx, micro, nano, emacs -nw)? [nvim]

Then:
- Run `npx ghostfleet-cli --yes` if I said yes to 1, otherwise `npx ghostfleet-cli`. The --yes goes AFTER the package name.
- Then run only the steps I said yes to:
  2: fleet-experimental enable jarvis
  3: fleet-jarvis voice --install
  4: fleet-jarvis voice --kokoro --install
  5: fleet-experimental enable shots
  6: run `fleet-phone` and walk me through the one next step it prints
  editor: add `export CLAUDE_FLEET_EDITOR=<editor>` to my shell rc and tell me which file you changed
- Never launch the interactive `ghostfleet` screen yourself (it needs a real terminal and will hang). When you're done, tell me to run `ghostfleet` in my terminal.
- Finish with what got installed, what you skipped, and any warning the installer printed. Quote the warnings; don't summarise them.