Orbit MCP server

Orbit — Your agent files the work. Orbit ships it. You review the pull request.

The Orbit dashboard (orbit web serve) — task backlog, live audit log, per-agent scoreboard.

Say what you want in the coding agent you already use. Over MCP it files a task with acceptance criteria, Orbit runs it in an isolated worktree with the task's file scope reserved and a gated pipeline, and a pull request comes back for you to review. Every tool call, provider exchange, and task transition lands in a joined audit record. Local-first, driving the provider CLI you already have.

You drive Claude Code, Codex, Grok Build, or Gemini CLI against real code, often in parallel. Agents make it easy to skip the disciplines that keep code maintainable, and six months later nobody can reconstruct why an agent wrote a given line. Orbit makes those disciplines cheap without making you the clerk: the agent files the task before it edits, every tool call goes into a structured audit log, parallel runs are sandboxed into worktrees with file-level locks, and your own design docs are retrievable by the agents doing the work.

What a session looks like

Two commands set Orbit up. After that you talk to your agent, and Orbit does the filing, isolation, and delivery.

$ orbit init                                 # global state in ~/.orbit
$ cd my-repo && orbit workspace init --mcp   # .orbit/ here; operator-authorized MCP server
                                             # registered with your installed agent CLIs

You:    The fsProfile lookup is undocumented. Get that fixed.
Agent:  Filing it as a task with acceptance criteria.
        orbit.task.add → ORB-1042 · proposed
        Filed. Approve it into the backlog and ship?
You:    Yes.
Agent:  orbit.task.update   → ORB-1042 · proposed → backlog
        orbit.workflow.ship → run jrun-… · file scope reserved · worktree isolated
        Shipping. The run is asynchronous; I'll check on it.
        orbit.workflow.run.show → plan · execute · review settled · PR opened · ORB-1042 · review
        Pull request open. The diff and the merge are yours.

$ orbit task update ORB-1042 --approve       # after you merge the PR: review → done

Illustrative session, not captured output. Tool names are real; identifiers are placeholders and arguments are omitted.

Three things to notice:

• The agent asks before the work starts. orbit.task.add lands the task in proposed. Moving it to backlog is the approval, a separate governed write that accepts nothing but a note. No agent session can skip it.
• The run stops at a pull request. orbit.workflow.ship is review-only: it opens or updates a PR and leaves the task in review with the PR unmerged. Orbit and GitHub stay separate: approving the task never merges the PR, and merging the PR never completes the task.
• Every step is on the record. orbit task show ORB-1042 reconstructs the prompt, plan, execution trace, and review thread months later, and every commit carries its task ID.

Features

Shortened. The full README is on GitHub.