Orbit

io.github.constellation-worksPublished by GitHub account constellation-worksv0.19.0Updated Oct 24, 2026

Orbit's local-first task and workflow registry for coding agents.

VerifiedSTDIODesktop onlyProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Orbit is a local-first task queue and delivery pipeline that lets coding agents file, plan, execute, and review code changes with approval gates.

What you can do
Orbit runs locally and gives coding agents a durable task registry: agents file proposed tasks with acceptance criteria, then queue them for plan, execute, and review runs in locked, isolated worktrees. It adds a gated delivery pipeline, an audit log, and a dashboard, and it can open pull requests for review. A bundled orchestration skill splits larger specs into parallel tasks and diagnoses failures.
When to use it
Use it when you already drive an authenticated coding agent CLI and want traceable, approval-gated changes with parallel runs and a review step before delivery. It suits teams that want the prompt, plan, and review kept behind every workflow commit without adopting a hosted service.
Requirements
macOS or Linux (x64 or arm64; Windows via WSL2), Node 18+, an authenticated agent CLI, and authenticated gh for pull requests. Installed as the npm package @orbit-tools/cli over stdio. State lives in ~/.orbit and .orbit/; no API keys or environment variables are declared.
Before you install
Orbit writes to your repository: it creates worktrees, commits, and pull requests, and local delivery refuses tracked changes, merge conflicts, and overlapping untracked paths. Nothing starts without approval, but PR runs can proceed to completion if you authorize --complete. It is pre-1.0 and breaking changes ship in minor releases, so review the checkout files listed by workspace init before the first ship.

Installation

In SourceWeft

  1. Open Orbit in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[Orbit]

Agents write. Orbit delivers.

[Release] [npm] [License: MIT] [Docs]

[Animated tour of the real Orbit dashboard while Orbit's agents work on Orbit itself: a proposed task waiting for approval, 16 tasks running at once across two hosts with 100 files locked so overlapping work waits its turn, an auto-drain with 12 running and 19 admitted that pauses new starts while the host runs hot, and auto-concurrency forecasting CPU and memory for each admission; a Codex pull-request pipeline run from isolated worktree through implement, commit, validate, review gate and push to an open pull request, 21 steps in 24 minutes 15 seconds; routines on a host clock and 22 auto-task definitions that keep the queue fed; analytics showing 3,277 tasks done in 30 days, 167% more than the 30 days before, and each model's implementation times; and the codebase view ranking the paths agents struggle with across 6,002 tasks.]

Orbit is a local-first runtime for coding agents. Keep using your authenticated agent CLI; Orbit adds a durable task queue, sandboxed worktrees, file locks for parallel runs, a gated delivery pipeline, and an audit log.

Why: fast agents make planning, review, and traceability easy to lose. Orbit keeps the prompt, plan, and review behind every change, with a task ID on every workflow commit.

  • Single binary, no cloud. State lives in ~/.orbit and .orbit/; Orbit sends no telemetry.
  • Bring your own agents. Use the provider CLIs you already have authenticated, without giving Orbit API keys.
  • MIT licensed. No paid tier or hosted offering.

How it works

text
You:    The fsProfile lookup is undocumented. Get that fixed.Agent:  Files a proposed task with acceptance criteria. Approve it and ship?You:    Yes.Agent:  Queues it, then runs plan → execute → review in a locked, isolated worktree.        Opens a pull request. Review and merge it, then approve the task to close it.

Nothing starts without approval; PR runs stop for your review unless you authorize --complete. The task record keeps the prompt, plan, execution trace, and review. For larger specs, ask your agent to orchestrate: the bundled orbit-orchestrate skill splits the work, queues it once approved, runs it in parallel, and diagnoses failures (delivery workflows).

Quick start

You need: macOS or Linux (x64 or arm64; Windows uses WSL2), Node 18+, an authenticated agent CLI, and authenticated gh for pull requests.

bash
npm install -g @orbit-tools/cliorbit init    # machine name, task-ID prefix, agent skills, and Linux sandbox setup

Open your agent in the repo and ask it to “set up Orbit for this repo”. The bundled orbit-setup skill registers it, connects MCP, runs orbit doctor, and asks for choices such as the PR target branch. Start a fresh agent session, then ask: “Add a hello.txt file containing hello; file it as an Orbit task.” Approve and ship the task when prompted, review and merge the PR, then approve the task to close it. Watch with orbit web serve.

Prefer a plugin? Install Orbit for Claude Code, Codex, or Cursor. Every MCP tool has a CLI twin; for the same loop without an agent, see your first task from the terminal.

Set up the repo by hand
bash
cd <repo> && orbit workspace init --mcp    # add --ship-mode local to skip PRsorbit doctororbit web serve

Review and commit the checkout files listed by workspace init, including MCP client files, before the first ship. Local delivery refuses tracked changes, merge conflicts, and untracked paths overlapping incoming changes.

orbit doctor checks CLI presence for default, system, and complexity-routed crews and warns when no MCP client is registered; it does not check provider sign-in or MCP connectivity. Use orbit doctor providers for all executor definitions. See Linux sandbox readiness and distro coverage.

To…Run
Inspect a task or runorbit task show <ID> · orbit run show <RUN_ID>
Open the dashboardorbit web serve (remote: orbit web connect <host>)
Open the dashboard in a desktop windowBuild the app in desktop/
Pick the default crew (provider and model)orbit config set workflow.default_crew <crew>
Route tasks to crews by complexityorbit config set --global workflow.hard_complexity_crews '["opus"]' (more)
Upgradenpm install -g @orbit-tools/cli@latest (orbit update --check shows what's new)

Features

Crews and complexity routing

Crews name a provider, model, and effort level; complexity pools choose one for a task without an explicit crew. See crew definitions, init's seeded pools, and complexity routing, weighting, and overrides.

MCP and authority

Connect your agent explains operator and agent-only authority; federated MCP connects multiple machines.

Where state lives

Scoping rules explain machine and workspace state. See the runbooks for backups, recovery, and upgrades.

Learn more

Contributing

Pull requests are welcome, from typo fixes to new executors. Small fixes can go straight to a PR; bigger changes start with an issue. See CONTRIBUTING.md.

License

MIT

Source: README.md at commit 47ed566

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.19.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts