Antigravity
Antigravity writes several local stores. Import all three source IDs to cover terminal, current application, and IDE activity without interpreting opaque legacy records as readable transcript data.
Source IDs
Section titled “Source IDs”| Source | Use it for |
|---|---|
antigravity-cli |
CLI transcript logs and task artifacts. |
antigravity |
Antigravity 2.0 readable logs, structured database steps, artifacts, and usage data. |
antigravity-ide |
IDE transcript logs, structured database steps, task artifacts, and usage data. |
How the import works
Section titled “How the import works”Hansard scans three independent Antigravity stores. The CLI source reads terminal transcript logs and task artifacts, the current application source reads Antigravity 2.0’s readable records, and the IDE source reads editor logs plus conversation databases. Each importer uses the session identifiers recorded by its own store to reconstruct messages, tool calls, results, lifecycle events, working directory, and available model or usage data.
Readable transcript logs remain the authority when present. Without one, Hansard can reconstruct a conversation from the verified database step types, including user and planner messages, tool calls and results, errors, notifications, and subagent launches. Database records also add per-generation model and token data. Unsupported step types remain counted and raw-preserved; opaque legacy protobuf bodies are preserved rather than decoded speculatively. Importing all three sources gives broad coverage while keeping genuinely separate terminal, application, and IDE sessions separate.
Import and keep current
Section titled “Import and keep current”hansard import --sources antigravity-cli,antigravity,antigravity-ide --since allhansard index rebuildhansard config sources add antigravity-clihansard config sources add antigravityhansard config sources add antigravity-idehansard watcher restartReview the import in the app
Section titled “Review the import in the app”After the import finishes, open Conversations and selectFilter & sort. Set Source tothe matching Antigravity CLI, 2.0, or IDE source, choose the backfill window underTime, and use Folder when the same harness appears in several projects. Select a result to inspect its messages, tool calls and results, files, commits, model and usage fields, and source provenance in one conversation view.
For a local source that should stay current, open Settings → Indexing & Imports. Automatic follows detected local harnesses; Custom lets Sources scannedselect an explicit set. Explicit cloud and account-export sources do not turn into background network jobs here. If the expected result is absent after resetting the conversation filters, return to the terminal import in this guide and add --explain-skips where supported.
What Hansard preserves
Section titled “What Hansard preserves”- Readable transcript turns, tool calls and results, lifecycle notices, task artifacts, and provider status or numeric exit codes.
- Structured system, checkpoint, history, generated-message, and error notices.
- Verified conversation-database steps, including tool activity, when a readable transcript log is unavailable.
- Per-generation model and token usage decoded from supported conversation databases.
- Conversation databases with their WAL and SHM sidecars in raw preservation, plus matching last-view annotations when available.
Known limitations
Section titled “Known limitations”- Legacy
conversations/*.pbbodies are preserved but not decoded. - Unknown conversation-database step types remain counted and raw-preserved until their schemas can be verified.
- A tool call without a durable result remains unresolved. A nonzero exit code is treated as failure even if a generic provider status says otherwise.
Refresh an existing archive
Section titled “Refresh an existing archive”hansard import --sources antigravity-cli,antigravity,antigravity-ide --since allhansard index rebuild