Orbiter Dev — Mobile Approval for AI Agents
Approve, reject, and monitor AI coding agent actions from your phone. Works with Antigravity, VS Code, Codex, Cursor, Windsurf, Claude Code, and any MCP-compatible agent.

Why Orbiter?
Your AI agent has root access to your codebase. Without guardrails, a single hallucination can rm -rf your project, push secrets to GitHub, or deploy broken code to production — while you're making coffee.
Orbiter adds a mobile oversight layer. When your agent attempts a risky operation, Orbiter pauses execution and sends a push notification to your phone. You review the command, approve with FaceID, and the agent resumes. No context lost.
How It Works
🤖 Agent 🛡️ Orbiter 📱 You
│ │ │
├── risky action ───────────→│ │
│ ├── push notification ────────→│
│ ⏸️ PAUSED │ │
│ │←──── Approve / Reject ───────┤
│←── resume / abort ─────────┤ │
Features
- 📱 Mobile Approvals — Approve from your pocket. Swipe, review the diff, tap approve.
- 🔒 FaceID Security — Biometric verification for high-risk actions. Production deploys require your face.
- ⚡ Granular Scopes — Allow Globally, Allow Once, or Allow in Workspace — per action.
- 🎯 Smart Policy Engine — Auto-approve safe commands (
npm test, git status). Only see the dangerous ones.
- 🛡️ Three Approval Modes — TURBO (speed), AUTO (balanced), ALWAYS (maximum security).
- 📊 Session Analytics — Token usage, cost tracking, and agent telemetry on your phone.
- 🔌 Universal — Works with Antigravity, VS Code, Codex, Cursor, Windsurf, Claude Code, and any MCP agent.
- 🔐 Zero Data Mode — Redacts diffs, diagnostics, logs, telemetry, and file contents before anything is sent to Orbiter.
Installation
- Open your IDE (VS Code, Antigravity, or compatible fork)
- Press
Ctrl+Shift+X (Extensions)
- Search for "Orbiter Dev"
- Click Install
- Follow the onboarding walkthrough to pair your phone
Quick Start
- Run
Ctrl+Shift+P → "Orbiter: Login with GitHub"
- Install the Orbiter Dev iOS app and sign in with the same account
- Run
Ctrl+Shift+P → "Orbiter: Connect Device" and enter the pairing code from the app
- Choose your approval mode:
Ctrl+Shift+P → "Orbiter: Set Approval Mode (V3)"
Commands
| Command |
Description |
Orbiter: Login with GitHub |
Sign in with your GitHub account |
Orbiter: Login with Google |
Sign in with your Google account |
Orbiter: Connect Device |
Pair your phone to this IDE |
Orbiter: Set Approval Mode (V3) |
Choose TURBO / AUTO / ALWAYS |
Orbiter: Show Status |
View connection status and settings |
Orbiter: Show Dashboard |
Open Mission Control dashboard |
Orbiter: Show Usage & Subscription |
View token usage and plan |
Orbiter: Request Approval |
Manually request approval |
Orbiter: Send Diagnostic Logs |
Submit diagnostics for troubleshooting |
Orbiter: Reconnect Device / Backend |
Force reconnect WebSocket |
Orbiter: Toggle Zero Data Mode |
Enable/disable Zero Data Mode |
Orbiter: Panic (Revoke All Sessions) |
Emergency: revoke all sessions |
Orbiter: Open Onboarding Guide |
Re-open the setup walkthrough |
Configuration
| Setting |
Default |
Description |
orbiterDev.approvalMode |
AUTO |
V3 Approval Mode: TURBO / AUTO / ALWAYS |
orbiterDev.autoConnect |
true |
Automatically connect on startup |
orbiterDev.showNotifications |
true |
Show approval notifications |
orbiterDev.zeroDataMode |
false |
Enable Zero Data Mode (no data stored on server) |
orbiterDev.secureMode |
false |
Enterprise: forces all interactions to require mobile approval |
orbiterDev.approvalTimeoutMinutes |
10 |
Minutes before an unresolved approval auto-rejects (1–60) |
orbiterDev.capture.runCommand |
true |
Route terminal commands to Orbiter |
orbiterDev.capture.filePermission |
true |
Route file permissions to Orbiter |
orbiterDev.capture.mcpTool |
true |
Route MCP tool calls to Orbiter |
orbiterDev.capture.browserAction |
true |
Route browser actions to Orbiter |
orbiterDev.telemetry.enabled |
false |
Enable optional telemetry collection |
orbiterDev.ruleSync.enabled |
false |
Allow Orbiter to write synced rule files into the workspace |
orbiterDev.remoteControl.enabled |
false |
Allow authenticated remote process and terminal-control actions |
orbiterDev.mcpAutoInjector.enabled |
false |
Enable experimental MCP auto-injection in manual Antigravity builds |
See the full settings reference in VS Code Settings → search "Orbiter".
Supported IDEs
| IDE / Agent |
Integration |
| Antigravity |
✅ Native gRPC sidecar |
| VS Code |
✅ This extension |
| Codex |
✅ MCP Server |
| Claude Code |
✅ MCP Server |
| Cursor |
✅ MCP Server |
| Windsurf |
✅ MCP Server |
| Any MCP Agent |
✅ MCP Server |
Privacy & Permissions
By using this extension, you agree to grant Orbiter functional access to your IDE, including:
- Terminal Output — Reading logs to visualize agent activity.
- Process Control — Listing and terminating development processes only when remote control is explicitly enabled.
- Diagnostics — Monitoring compiler errors and agent state; diagnostic uploads are user-initiated and redacted.
- File Permissions — Intercepting file read/write requests for approval routing.
Local Security Architecture
Orbiter Dev uses a local sidecar architecture for executing agentic actions. To secure loopback traffic (localhost), the sidecar dynamically generates self-signed SSL certificates. The extension configures its internal gRPC/HTTP2 transport with rejectUnauthorized: false. This poses no external risk because the traffic never leaves the host machine.
Data Handling
- Zero Data Mode: When enabled, diffs, source code, file contents, logs, diagnostics, command payloads, and telemetry are blocked or redacted before upload. Manual approval requests send metadata with the diff omitted.
- Standard Mode: Action summaries and user-requested diffs may be transmitted over TLS to enable mobile review. Optional telemetry remains off unless
orbiterDev.telemetry.enabled is turned on.
See the Privacy Policy for full details.
Website • Documentation • Support
© 2026 Orbiter Dev. MIT License.
| |