Orbit Concepts
Projects, sessions, multi-turn runs, and discovered workspace artifacts.
The Project Model
In Orbit, a Project is not an abstract cloud container—it is bound directly to a real path on your local filesystem. Every file read, tool execution, and child process spawned by Antigravity is strictly anchored to this directory.
Orbit executes Antigravity with cwd set explicitly to the project root. When tools attempt to modify files outside this boundary, Orbit triggers an explicit boundary confirmation modal.
Sessions and Turns
A Project contains one or more Conversations. Each conversation represents an ongoing stream of multi-turn problem solving.
- Native Conversation ID: Orbit maps each conversation record directly to Antigravity's internal
conversation_id. - Turns: A turn begins when the user submits an instruction, progresses through tool invocations and interactive approvals, and terminates when the agent produces final output or is cancelled.
- State Tracking: Every turn records its start time, execution duration, tokens exchanged, and exit status in local SQLite.
Artifact Management
When an agent generates or updates files during a turn, Orbit automatically categorizes them in the Artifact Drawer. Orbit provides specialized inspectors:
Code & Diffs
Syntax-highlighted diffs showing additions and deletions per file turn.
Images & SVGs
Direct visual canvas rendering with pan, zoom, and aspect ratio metrics.
Web Prototypes
Isolated iframe sandbox allowing interaction with generated HTML/JS.