ORBIT

A cockpit for the agents that write your code.

It runs the coding CLI you already use, each task in its own worktree, and writes down what every run did.

curl -fsSL https://getorbit.sh/install | bash

macOS and Linux.

Stay in the loop

  1. Orbit in three minutes

    2:54

    What Orbit does, start to finish: running the work, reading what it did, supervising it, and making it yours.

    Learn more in the docs →

Get started2 videos · 1:44

  1. 01

    Orbit in a minute

    0:45

    A minute of the recordings below, without sound.

    Learn more in the docs →
  2. 02

    Getting started

    0:59

    Install it, open it where your repositories are, and write the first task: it runs and stops where you decide.

    Learn more in the docs →

Run the work8 videos · 5:43

  1. 03

    A run, end to end

    0:58

    A task moves through its flow phase by phase, stops at the gate you set, and goes on when you let it; then every tab of what it did.

    Learn more in the docs →
  2. 04

    Many tasks at once

    0:36

    Several tasks run side by side, each in its own worktree and branch, in one window.

    Learn more in the docs →
  3. 05

    One change, several repos

    0:43

    A task can span your backend and frontend: one diff per repository, all in the same task.

    Learn more in the docs →
  4. 06

    Ten agents, four percent

    0:52

    Ten agents run at once while Orbit uses 4% of one core; an IDE doing the same uses about half of one.

    Learn more in the docs →
  5. 07

    What each agent costs your machine

    0:30

    Press % to see each agent's memory and CPU, and kill one that hangs.

    Learn more in the docs →
  6. 08

    Autopilot

    0:26

    One key and Orbit works the queue on its own; a task that needs a person stops and waits for you.

    Learn more in the docs →
  7. 09

    The guard

    0:35

    When an agent loops, hangs or spends too much, Orbit stops it and hands the task back to you.

    Learn more in the docs →
  8. 10

    The CLI, both ways

    1:04

    Press c and your own CLI opens in the task's worktree, already told the task: Claude Code, Codex, opencode, Cline or Antigravity. Quit it and the session is in the task's notes.

    Learn more in the docs →

Understand what it did4 videos · 3:06

  1. 11

    Reading what it did

    0:46

    A finished task: how the prompt became the diff, what the agent says it did and did not, the diff itself, and where in the repository it went.

    Learn more in the docs →
  2. 12

    Inside a task

    0:56

    The fourteen tabs a task opens to, one at a time, each with what it is for.

    Learn more in the docs →
  3. 13

    Files, like an editor

    0:37

    The checkout as the task left it: choose lines and copy them, or open a file's menu for its patch, its path, your editor or Finder.

    Learn more in the docs →
  4. 14

    The map of a change

    0:47

    Every route a change touches, drawn down to the query it runs.

    Learn more in the docs →

Supervise and learn2 videos · 1:14

  1. 15

    The supervisor

    0:38

    A second agent reads each finished run against what was asked, and takes directions in a thread you write into.

    Learn more in the docs →
  2. 16

    What Orbit knows

    0:36

    Rules about your code reach every prompt; each one keeps its source, and you can narrow it or pause it.

    Learn more in the docs →

Make it yours3 videos · 1:47

  1. 17

    Flows you write yourself

    0:31

    A flow is a list of phases, each with its own engine, model and permissions; five ship built in, the rest you write.

    Learn more in the docs →
  2. 18

    Describe a flow in one sentence

    0:31

    Say what the flow should do; Orbit drafts its phases, and you read them before you save it.

    Learn more in the docs →

Long sessions2 videos · 1:06

  1. 20

    Compact a session

    0:38

    When a session's context fills up, compact it and keep going.

    Learn more in the docs →
  2. 21

    Out of tokens? Switch provider

    0:28

    When an engine runs out, autopilot moves the task to another one, which continues from the step it stopped at.

    Learn more in the docs →

Fewer tokens1 video · 0:36

  1. 22

    The agent asks Orbit for the code

    0:36

    The agent asks Orbit for the code it needs, and understands it faster with fewer tokens.

    Learn more in the docs →

Connect it3 videos · 1:14

  1. 23

    Orbit by chat

    0:24

    On Telegram: a task that stops sends you a message, and you answer with the same commands as the terminal.

    Learn more in the docs →
  2. 24

    A task from an issue link

    0:23

    Paste a Linear, Jira or GitHub issue link and the form takes its id; with LINEAR_API_KEY set, it also reads the Linear issue's text.

    Learn more in the docs →
  3. 25

    jev judges each gate

    0:28

    jev is the decision engine that judges each gate: in shadow it writes its verdict and acts on nothing, and with the setting on it acts when it is sure.

    Learn more in the docs →

The web1 video · 0:44

  1. 26

    Orbit in the browser

    0:44

    orbit web shows the same board in a browser: open a task to read its diff, its timeline, its report and where the change went.

    Learn more in the docs →

How to use Orbit

From installing it to running your first tasks.

01Install

Install Orbit and open it on your projects.

  1. Install it. macOS and Linux.

    curl -fsSL https://getorbit.sh/install | bash
  2. Open it over your repositories.

    orbit top ~/code
  3. Press N to write a task, n to run it.

What you'll seeEvery git repository under ~/code.

  • Needs one coding CLI: Claude Code, Codex, OpenCode, Antigravity or Cline.
  • Update with orbit upgrade.

02How it works

Each task runs in its own worktree, through a flow of phases.

  1. Press N: title, what to do, repository, flow.

  2. Pick a flow. F edits them.

    orbit flows
  3. Press n. It stops where the flow says.

  4. Export the record of every run.

    orbit export ~/orbit-record
  • Nothing reaches your branch until you say so.

03The board

Every task, in four bands: To do, Running, Needs you, Done.

  1. Press ⏎ on a task.

  2. Switch tabs: diff, review, prompts and eleven more.

  3. Press m for what you can do here.

  4. The same board, from the shell.

    orbit board list
  5. Work in another repository too: the task's id, then the repository's name.

    orbit join CHK-4 ledger
  • Needs you: stopped for a review, a failed check or a pause.

04Engines

Pick the engine and model for each phase.

  1. See which engines you have.

    orbit engines
  2. Set the default.

    orbit settings set engine codex
  3. Out of tokens? n goes on with another engine.

  4. Context full? ctrl+K goes on in a clean session.

  5. See what each agent costs your machine (%); ctrl+T kills one that hangs.

    orbit board meter
  • Cost per phase is on the cost tab; Q shows what is left.

05Autopilot and the supervisor

Autopilot works the queue; the supervisor checks each finished run.

  1. Turn autopilot on (A).

    orbit settings set autopilot on
  2. Tell the supervisor what to watch (S).

    orbit supervisor say "…"
  3. Read the rules it learned (K).

    orbit knowledge
  4. Cap what one task may spend: the guard stops it at $3.

    orbit settings set guard.task-spend 3
  • It never overrides your pause or a critical task.
  • The guard stops a call that hangs or loops, and says why.

06Connect it

Telegram, Linear, jev and your coding CLI.

  1. Telegram: export your @BotFather bot's token.

    export ORBIT_TELEGRAM_TOKEN=…
  2. Start the chat. It answers with your chat id.

    orbit chat -on telegram
  3. Save the id it answered with, the number in place of 7912204269. Only that account can give orders.

    orbit settings set chat-id 7912204269
  4. Linear: paste an issue URL in the new-task form (N). The key brings its text.

    export LINEAR_API_KEY=…
  5. jev: record its verdicts, acting on nothing. Needs TYPESAFE_API_KEY.

    orbit settings set decisions shadow
  6. Let your coding CLI read the board.

    orbit mcp install
  • In Telegram, anything irreversible asks for /yes.

07The web

The same board in your browser, on your machine only.

  1. Start it.

    orbit web
  2. Or press o on a task.

What you'll seehttp://127.0.0.1:7777, with the same bands, tabs and keys.

  • The review tab maps the change down to the query.

08Keys

Small letters act on the task; capitals open a screen.

  • ? lists every key, m what applies here, : takes a command.
  • D and the pull request keys are capitals that act on the task.

Moving around

↑
Up
↓
Down
g
First
G
Last
PgUp
Page up
PgDn
Page down
⏎
Open
esc
Back
tab
Next tab
⇧tab
Previous tab
←→
Scroll sideways
@
Which repository

Starting work

n
Start a run
N
Write a task
m
Task menu
M
Board menu

The task in front of you

p
Pause
r
Resume
s
Skip this phase
ctrl+K
Compact
ctrl+R
Run the failed phase again
x
Cancel
b
Back to to do
t
Take the keyboard
h
Hand it back
ctrl+O
Watch the phase
a
Ask
d
Mark read
D
Delete
o
Open in the web

Screens and switches

/
Filter
:
Commands
c
Interactive CLI
!
Shell
R
Repositories
F
Flows
K
What orbit knows
E
Engine & model knobs
Q
Quota
S
Supervisor
A
Autopilot
%
Memory and CPU
ctrl+T
Kill a stray process
L
Language
?
Help
q
Quit

Taking text out

ctrl+S
Select text with the mouse
ctrl+Y
Copy what is under the pointer

The pull request

P
Create PR
U
Update PR
J
Merge PR
X
Close PR
C
Fix checks
T
More tests
O
Resolve comments
V
Deep review

What's new

Newest first.