Incognito Mode
Toggle incognito mode for the current Antigravity CLI session. When enabled:
- Local JSONL capture continues
- Trace and log outputs to non-exempt Datadog destinations are suppressed
- Aggregate metrics continue and cannot be disabled by incognito
- Mode resets automatically when the session ends
Org-managed security destinations configured with incognito_exempt: true may still receive events. Do not describe incognito as a security or compliance bypass.
Toggle
For a durable user opt-out or opt-in, call trajectory_incognito with persistent: true and the requested enable value. Do not pass session_id.
- Decide the requested state.
- For
/incognito, "go incognito", "pause capture", "stop recording", or "private mode", enable incognito unless it is already enabled.
- For "turn off incognito", "resume capture", or "resume publish", disable incognito.
- If the user explicitly asks to toggle, call the
trajectory_incognito MCP tool with enable: true unless you have already confirmed the active session is incognito, then call it with enable: false.
- If the
trajectory_incognito MCP tool is available, call it with enable, client: agy, and project_dir set to the current workspace; omit session_id so the tool resolves the active session from Trajectory's active-session registry.
- If the tool reports multiple matching active sessions, call
list_active_sessions, choose the active Antigravity session matching the current workspace, and retry with that session_id.
- Worst-case fast lookup: check
TRAJECTORY_SESSION_ID, AGY_SESSION_ID, ANTIGRAVITY_SESSION_ID, CODEX_SESSION_ID, GEMINI_SESSION_ID, CLAUDE_SESSION_ID, OPENCODE_SESSION_ID, PI_SESSION_ID, DROID_SESSION_ID, or COPILOT_SESSION_ID; otherwise call list_active_sessions or run trajectory mcp sessions --active --json from the workspace, select the row matching the current client/workspace with the newest last_event, and retry with session_id.
- If MCP is not available, resolve the current session ID with
TRAJECTORY_SESSION_ID or trajectory mcp sessions --active --json, then call the HTTP endpoint directly:
curl -fsS -X POST "http://localhost:19222/session/incognito?session_id=${session_id}&enable=${enable}"
- Tell the user whether incognito is now enabled or disabled.
1---2name: incognito-63description: Toggle Trajectory incognito mode for the current Antigravity CLI session. Use when the user says "/incognito", "go incognito", "pause capture", "stop recording", "private mode", or asks to temporarily suppress Datadog publish for sensitive work.4---56# Incognito Mode78Toggle incognito mode for the current Antigravity CLI session. When enabled:9- Local JSONL capture continues10- Trace and log outputs to non-exempt Datadog destinations are suppressed11- Aggregate metrics continue and cannot be disabled by incognito12- Mode resets automatically when the session ends1314Org-managed security destinations configured with `incognito_exempt: true` may still receive events. Do not describe incognito as a security or compliance bypass.1516## Toggle1718For a durable user opt-out or opt-in, call `trajectory_incognito` with `persistent: true` and the requested `enable` value. Do not pass `session_id`.19201. Decide the requested state.21 - For `/incognito`, "go incognito", "pause capture", "stop recording", or "private mode", enable incognito unless it is already enabled.22 - For "turn off incognito", "resume capture", or "resume publish", disable incognito.23 - If the user explicitly asks to toggle, call the `trajectory_incognito` MCP tool with `enable: true` unless you have already confirmed the active session is incognito, then call it with `enable: false`.242. If the `trajectory_incognito` MCP tool is available, call it with `enable`, `client: agy`, and `project_dir` set to the current workspace; omit `session_id` so the tool resolves the active session from Trajectory's active-session registry.253. If the tool reports multiple matching active sessions, call `list_active_sessions`, choose the active Antigravity session matching the current workspace, and retry with that `session_id`.264. Worst-case fast lookup: check `TRAJECTORY_SESSION_ID`, `AGY_SESSION_ID`, `ANTIGRAVITY_SESSION_ID`, `CODEX_SESSION_ID`, `GEMINI_SESSION_ID`, `CLAUDE_SESSION_ID`, `OPENCODE_SESSION_ID`, `PI_SESSION_ID`, `DROID_SESSION_ID`, or `COPILOT_SESSION_ID`; otherwise call `list_active_sessions` or run `trajectory mcp sessions --active --json` from the workspace, select the row matching the current client/workspace with the newest `last_event`, and retry with `session_id`.275. If MCP is not available, resolve the current session ID with `TRAJECTORY_SESSION_ID` or `trajectory mcp sessions --active --json`, then call the HTTP endpoint directly:28 `curl -fsS -X POST "http://localhost:19222/session/incognito?session_id=${session_id}&enable=${enable}"`296. Tell the user whether incognito is now enabled or disabled.