Documentation

• ✓ Node.js 18+ installed
• ✓ Claude Code, Cursor, Windsurf, Antigravity, or another MCP-compatible agent installed
• ✓ Orbiter Dev mobile app (iOS)

Create or edit .claude/settings.json in your project root:

{
  "mcpServers": {
    "orbiter-dev": {
      "command": "npx",
      "args": ["-y", "@orbiterdev/mcp-server@latest"],
      "env": {
        "ORBITER_SERVER_URL": "https://api.orbiterdev.ai"
      }
    }
  }
}

For Cursor: Settings → MCP → Add Server. For Windsurf: use MCP settings panel.

When an agent uses the MCP tools, it will prompt you to pair:

1. The agent calls orbiter_auth with the code from your mobile app
2. Open Orbiter Dev app → Settings → Pair IDE
3. Copy the pairing code (e.g. ORBIT-K7N3) and provide it to the agent
4. The agent verifies — you're connected!

Recommended for Claude Code users. The MCP server exposes tools; hooks add lifecycle capture so Orbiter can route risky shell activity, permission prompts, completion signals, and session changes to mobile.

Start with the public CLI permission hook in .claude/settings.json. The full beta hook pack adds the remaining lifecycle hooks after the Orbiter bridge is installed.

{
  "hooks": {
    "PermissionRequest": [
      {
        "matcher": "Bash",
        "hooks": [
          {
            "type": "command",
            "command": "npx -y @orbiterdev/mcp-server@latest permission-check"
          }
        ]
      }
    ]
  }
}

The tested beta pack currently covers PermissionRequest, PreToolUse, PostToolUse, Notification, TaskCompleted, SessionStart, and SessionEnd.

Codex requires users to review newly installed or modified hooks before they run. After installing Orbiter Codex hooks, open the workspace in Codex and use the new-chat banner or go to Settings → Hooks to review them.

• • The new-chat composer can show “hooks need review before they can run” with Trust all and Review hooks.
• • Settings → Hooks lists each workspace and the number of hooks needing review.
• • Trust is per workspace. Repeat review for each project where Orbiter hooks are installed.
• • Codex may ask for review again after an Orbiter update because hook commands are hashed for safety.

Pair Codex separately from Antigravity or generic MCP entries. Orbiter’s managed Codex setup uses a dedicated Codex credential profile so the iOS app can show Codex as its own paired system.

Install Orbiter Dev from the marketplace for your editor:

1. Open command palette: Ctrl+Shift+P
2. Run: Orbiter: Login and choose GitHub or Google
3. Direct commands are also available: Orbiter: Login with GitHub and Orbiter: Login with Google
4. Run: Orbiter: Connect Device to pair your phone
5. The onboarding walkthrough will guide you through mode selection

Change anytime via: Ctrl+Shift+P → Orbiter: Set Approval Mode

Available on TestFlight (iOS). Request an invite from the beta form on the homepage or from the extension command Orbiter: Get iOS App (TestFlight).

1. Open Orbiter Dev app → login with the same GitHub or Google account
2. Go to Settings → Pair IDE
3. A pairing code appears (e.g., ORBIT-K7N3)
4. Enter this code in your IDE when prompted
5. Your devices are now synced!

• 🛡️ FaceID for high-risk approvals (production deploys, data deletion)
• 📊 Agent HUD — real-time heartbeat, progress checkpoints
• 🎚️ Risk Rules — scoped auto-approval and manual-review controls
• 🔗 Paired Systems — manage trusted IDEs and desktop agents from mobile
• 🌙 Offline Queue — approvals cached locally when offline