Antigravity Integration

Binary detection, environment inheritance, and transport pipeline.

Binary Detection & Path Resolution

When Orbit launches, the AntigravityProvider executes an automatic resolution sequence to locate the agy executable:

Environment Override: Checks if ORBIT_AGY_PATH is set in the runtime environment.
PATH Traversal: Executes system discovery via which agy (Linux/macOS) or where agy (Windows).
Known Default Paths: Checks standard install locations:~/.local/bin/agy/usr/local/bin/agy~/.gemini/antigravity-cli/bin/agy

Orbit passes through the parent desktop process environment to child CLI executions. This ensures:

Zero credential storage: Orbit does not store or prompt for Google API keys.
Custom shell variables: Proxy configurations, HTTP_PROXY, and custom PATH entries are honored.
Tool execution context: Git configurations, SSH keys, and compiler environments operate exactly as in your native terminal.

Orbit provides dual transport mechanisms depending on the execution context:

Transport Mode	Invocation Syntax	Primary Use Case
StreamJsonTransport	agy --print --output-format stream-json --conversation <id>	Standard multi-turn runs, parsed JSON stream events, automated tool telemetry.
PtyTransport	node-pty fork(agy, [...args], { cols: 120, rows: 40 })	Direct interactive shell sessions requiring terminal control sequences or curses UI.