Issue #144 — Antigravity CLI Transcript Parser
Add a parser for the Antigravity transcript format to extract session metadata.
Background
Antigravity CLI (agy) logs are saved in a JSONL format (transcript.jsonl)
under ~/.gemini/antigravity-cli/brain/<conversation-id>/.system_generated/logs/.
Unlike Claude Code, which registers events with properties like message,
cwd, and type, Antigravity structures logs as conversation steps.
Requirements
- Implement a pure codec submodule in
crates/claude or a new
crates/antigravity crate to parse transcript.jsonl.
- Extract the first
USER_INPUT step content as the summary (truncated to
120 UTF-16 units).
- Compute
message_count based on the number of USER_INPUT and
PLANNER_RESPONSE steps.
- Concatenate user/model step content for FTS indexing (
text_content),
capped at 8000 UTF-16 units.
- Extract the project workspace directory (CWD) from the log (e.g., from step
metadata or run_command tool call Cwd arguments) to determine the CWD.
Tests
- Parse simple transcripts and verify correct summaries/message counts.
- Gracefully handle corrupt or empty lines (skip them).
- Extract the correct CWD from tool calls or step metadata.
Issue #144 — Antigravity CLI Transcript Parser
Add a parser for the Antigravity transcript format to extract session metadata.
Background
Antigravity CLI (
agy) logs are saved in a JSONL format (transcript.jsonl)under
~/.gemini/antigravity-cli/brain/<conversation-id>/.system_generated/logs/.Unlike Claude Code, which registers events with properties like
message,cwd, andtype, Antigravity structures logs as conversation steps.Requirements
crates/claudeor a newcrates/antigravitycrate to parsetranscript.jsonl.USER_INPUTstepcontentas thesummary(truncated to120 UTF-16 units).
message_countbased on the number ofUSER_INPUTandPLANNER_RESPONSEsteps.text_content),capped at 8000 UTF-16 units.
metadata or
run_commandtool call Cwd arguments) to determine the CWD.Tests