REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Orbit's local-first task and workflow registry for coding agents.
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
One time only; it works for every server that needs Node.js
SettingsDeveloperEdit Config
{
"mcpServers": {
"orbit": {
"command": "npx",
"args": [
"-y",
"@orbit-tools/cli",
"mcp",
"serve"
]
}
}
}Use Orbit and tell me what you can do for me, then show me one thing✓ If Claude says it is using Orbit or shows a Orbit tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Orbit yet
Orbit runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Orbit
B · Others in Developer tools that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
One time only; it works for every server that needs Node.js
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user orbit -- npx -y @orbit-tools/cli mcp serveYou should see Orbit listed as connected
Use Orbit and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Orbit or shows a Orbit tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
One time only; it works for every server that needs Node.js
Use Orbit and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Orbit or shows a Orbit tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
One time only; it works for every server that needs Node.js
Use Orbit and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Orbit or shows a Orbit tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Claude Code
claude mcp add --scope user orbit -- npx -y @orbit-tools/cli mcp serveClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"orbit": {
"command": "npx",
"args": [
"-y",
"@orbit-tools/cli",
"mcp",
"serve"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"orbit": {
"command": "npx",
"args": [
"-y",
"@orbit-tools/cli",
"mcp",
"serve"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"orbit": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@orbit-tools/cli",
"mcp",
"serve"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 14, 2026
The registry name was verified with the GitHub account constellation-works, which owns the repo
Code last changed yesterday
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed yesterday, and the latest version (0.19.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: REA, GitHub, Serena MCP: the IDE for your agent
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
A powerful toolkit for coding, providing semantic retrieval and editing capabilities.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Agents write. Orbit delivers.
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.
~/.orbit and .orbit/; Orbit sends no telemetry.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).
| Platform | Support |
|---|---|
| macOS and Linux | Supported on x64 and arm64 |
| Windows | Via WSL2; not yet verified on a Windows host. Native Windows is not supported. |
You need: a supported platform, Node 18+, an authenticated agent CLI, and authenticated gh for pull requests.
npm install -g @orbit-tools/cli
orbit 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
cd <repo> && orbit workspace init --mcp # add --ship-mode local to skip PRs
orbit doctor orbit 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 run | orbit task show · orbit run show |
| Open the dashboard | orbit web serve (remote: orbit web connect ) |
| Open the dashboard in a desktop window | Build the app in desktop/ |
| Pick the default crew (provider and model) | orbit config set workflow.default_crew |
| Route tasks to crews by complexity | orbit config set --global workflow.hard_complexity_crews '["opus"]' (more) |
| Upgrade | npm install -g @orbit-tools/cli@latest (orbit update --check shows what's new) |
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.
Connect your agent explains operator and agent-only authority; federated MCP connects multiple machines.
Scoping rules explain machine and workspace state. See the runbooks for backups, recovery, and upgrades.
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.