Project Window
Orbit Map
Section titled “Orbit Map”All Projects drawer → Orbit tab. A visual overview of all projects arranged around a Mission Control hub by urgency — waiting projects closest in, working projects in the middle ring, idle and stale on the outside. Selecting a node shows status, queue count, activity, and Review/Open actions in the right rail.
Bold surfaces (CLI, Preview, Code Graph, Mobile Builds, Git/Deploy)
Section titled “Bold surfaces (CLI, Preview, Code Graph, Mobile Builds, Git/Deploy)”The per-project window tabs:
- CLI — split session plus live diagnostics.
- Preview — local or web preview.
- Code Graph — Memtrace code intelligence.
- Mobile Builds — Android APK/AAB.
- Git/Deploy — Git status, GitHub Issues, and Vercel/Railway deploy health. See Git Tab & Recovery for pull requests, stash inventory, and recovery surfaces.
Dependency-slot capacity strip
Section titled “Dependency-slot capacity strip”Project window header, and the Slot Inspector; also surfaced on Pipeline cards. Shows every configured dependency-pool slot with its real lifecycle state and opens a read-only inspector for it. Pipeline cards identify which slot owns a given run and what launch stage it’s at, so a run’s dependency footprint is visible without leaving the Pipeline view.
Servers tab + tool suggestions
Section titled “Servers tab + tool suggestions”Project window → Servers tab. Configure, start, and stop per-project dev servers; Orbit scans package.json for known dev tools and offers one-click “Detected project tools” suggestions (a server entry plus an MCP stdio entry).
MCP tools: orbit_server_start, orbit_server_stop, orbit_server_status, orbit_server_logs.
Docs tab
Section titled “Docs tab”Project window → Docs tab. An in-app viewer and editor for project context files, global context files, and the read-only audits/ subfolder; create, edit, and save inline.
MCP tools: orbit_get_context, orbit_list_context, orbit_get_context_file, orbit_write_context, orbit_append_context.
Project Database tab
Section titled “Project Database tab”Project window → Database tab. Connect a live database to the project and run SQL queries without leaving Orbit. A provider button bar lets you switch between configured database connections (Neon, Supabase, Firestore); the active connection is shown in the header. Queries run in a built-in SQL editor — press Ctrl+Enter to execute. A history dropdown surfaces the last 10 queries run in this project for quick re-use. Results show row count and execution time in the footer.
The tab defaults to read-only. Queries that modify or destroy data are blocked unless Write mode is explicitly enabled via the write-mode toggle — see SQL write gate below.
MCP tools: orbit_neon_query, orbit_neon_schema, orbit_supabase_query, orbit_supabase_schema, orbit_firestore_query, orbit_firestore_collections, orbit_firestore_schema.
SQL write gate
Section titled “SQL write gate”The write gate enforces read-only as the default for all database sessions. Queries classified as read operations (SELECT, EXPLAIN) run freely. Queries that modify or destroy data — INSERT, UPDATE, DELETE, DROP, TRUNCATE, ALTER — are blocked at execution time when write mode is off, and the editor shows a warning instead of running them.
To run modifying queries, enable Write mode via the toggle in the Database tab. A status badge updates to show the session is now in write mode. The gate inspects the raw SQL text before every execution, so the classification applies to queries run from history as well as queries typed directly.
Project file browser
Section titled “Project file browser”Project window → Files tab (also accessible from the right rail). Browse the project’s directory tree, open any file for reading, create new files, rename existing ones, and delete items — the same operations available to MCP clients. All writes go directly to the filesystem inside the registered project directory.
MCP tools: orbit_read_file, orbit_list_files, orbit_write_file, orbit_delete_file.
Roadmap tab
Section titled “Roadmap tab”Project window → Roadmap tab. A planning surface for the project, shown alongside the other project tabs (queue, docs, servers, preview, code graph, files, deployment, database). App Store Connect and Play Store status (TestFlight build state, Play Console production/internal track) surface under the Mobile Builds tab.
Mobile Builds tab
Section titled “Mobile Builds tab”Project window → Mobile Builds tab. Android APK/AAB builds run locally on Windows, Mac, or Linux like any other project build. iOS builds require a Mac: pick an online, macOS-platform peer from Connected Machines (multi-node — a Windows-only setup has no iOS build target available). Orbit checks that machine’s build capability (toolchain readiness, Fastlane/App Store Connect configuration) before offering Build (a debug .ipa via Fastlane) or Ship (a release build uploaded toward App Store Connect); either is blocked with a reason if the Mac isn’t ready. App Store Connect and Play Store status — TestFlight build state, Play Console production/internal track — surface in the same tab.
MCP tools: orbit_appstore_status, orbit_appstore_builds, orbit_playstore_status cover store-side status only; triggering a build or ship is a UI action, not currently exposed over MCP.
Deployment health
Section titled “Deployment health”On project rows and cards (the health dot), and Git → Deploy. Vercel and Railway projects show a live deploy-health dot (live, failed, building, unknown) opening a Deploy Health panel with logs, failure snippets, and an Apollo draft-fix action (never auto-queues).
MCP tools: orbit_vercel_status, orbit_railway_deployments, orbit_vercel_logs, orbit_railway_logs.