Skip to content
Hansardhansard

Grok Build

Grok Build is the current Cursor-successor integration target. Hansard uses its durable ACP updates as the conversation chronology and joins only matching sidecars that add usage or tool detail.

Source IDs

Section titled “Source IDs”
Source Use it for
grok-build Local Grok Build sessions, events, prompt ledgers, and chat sidecars.

How the import works

Section titled “How the import works”

Hansard treats each session’s durable ACP update stream as the authoritative chronology. It replays those updates in order to build user and assistant turns, tool calls and results, edits, status changes, and other lifecycle events. This means a chat sidecar cannot reorder or replace events that Grok Build recorded in the session stream.

Matching prompt-ledger and chat sidecars can enrich those same events with tool arguments, model names, tokens, cost, and project metadata. Hansard joins them only when the stored session identity matches. Forked sessions remain separate conversations with their lineage preserved, and high-volume telemetry is summarized rather than expanded into noisy transcript messages. Reimporting follows the stable session identifiers and refreshes existing archive entries.

Import and keep current

Section titled “Import and keep current”
Terminal window
hansard import --source grok-build --since all
hansard index rebuild

Review the import in the app

Section titled “Review the import in the app”

After the import finishes, open Conversations and selectFilter & sort. Set Source toGrok Build, 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”
  • Durable turn order, user and assistant messages, tools, plan and mode changes, hooks, subagent activity, permission changes, and MCP lifecycle.
  • Complete prompt ledgers with directional tokens, cache reads, reasoning tokens, model calls, API duration, and provider-reported cost.
  • Matching chat-history detail such as tool arguments, model, reasoning effort, and user-interjection provenance.
  • Fork parent, fork time, and session kind without classifying every fork as a subagent.

Known limitations

Section titled “Known limitations”
  • High-volume phase and timing ticks are summarized instead of becoming visible transcript rows.
  • The cross-session per-working-directory prompt history is not attached to an individual archive.
  • Peak _meta.totalTokens is context telemetry, not billed usage.
  • Nonterminal tool previews do not create results until a durable terminal update exists.

Refresh an existing archive

Section titled “Refresh an existing archive”
Terminal window
hansard import --source grok-build --since all
hansard index rebuild