Connect a Coding Agent
A prompt is only useful if something can run it. Orbit calls that something a coding agent, and you need at least one registered before any prompt will execute. There are three ways to provide one, explained in plain terms on the Icons Ready screen during onboarding and any time afterward under Settings → Coding Agent. None of them is pushed on you.
The three options
Section titled “The three options”Apollo default. The simplest path. Orbit’s own co-pilot can run prompts for you, covered by the Sivants subscription. Nothing to install, nothing to configure.
Claude Max-Pro subscription. If you already pay for Claude Max or Pro, you can authorize Orbit to drive Claude Code through your subscription using OAuth, rather than an API key. This keeps heavy Claude usage on the plan you already have. Reviews and other manual steps stay under your control.
API key. Bring an Anthropic, OpenAI, or Google key and Orbit uses it directly. Keys live in the Vault, never sent to Sivants, and BYOK usage bypasses Sivants Credits entirely.
Guided Phase 3 setup guide
Section titled “Guided Phase 3 setup guide”During guided onboarding, Apollo also surfaces a Phase 3 card for connecting your own AI to Orbit through MCP. Pick Claude, ChatGPT, or Cursor, then drag the provider-specific setup guide from Apollo into that AI’s chat. The guide walks the AI through the connection steps, including current caveats for provider UI changes and free-trial tunnel behavior.
Routing agents to tiers
Section titled “Routing agents to tiers”Once you have one or more agents registered, you decide which agent and model handles each kind of work under Settings → Model Tiers & Agents. Each complexity tier — Low, Medium, High (UI), High (Backend), Coordinator — routes to a specific agent and model, with its own effort and authentication settings. At least one agent must be registered before any prompt can run.
You can also route any tier to a local or custom OpenAI-compatible endpoint — DeepSeek, MiniMax, Ollama, LM Studio, or your own base URL. The API executor runs with a curated, safe subset of Orbit’s tools (file reads, shell, git, context) and blocks the sensitive ones (vault, deploy, billing).