CodeBuddy
Hansard’s CodeBuddy reader is mapped from the published CodeBuddy package. It is deliberately conservative because verification against a real user store is still pending.
Source IDs
Section titled “Source IDs”| Source | Use it for |
|---|---|
codebuddy |
CodeBuddy project transcripts, metadata sidecars, and delegated runs. |
How the import works
Section titled “How the import works”Hansard scans CodeBuddy’s project transcript directories and reads the record types documented by the published CodeBuddy package. User messages, assistant messages, reasoning, tool calls, tool results, and compaction records are assembled in their stored order. The working directory recorded inside the session supplies project attribution because the directory name alone can be lossy.
Metadata sidecars can add model, usage, and delegated-run relationships to the conversation. If the importer encounters a record shape it does not recognize, it counts and preserves that record with the raw source instead of inventing a message for it. This keeps the archive usable now while allowing a later parser update and reimport to recover more detail from the original provider files.
Import and keep current
Section titled “Import and keep current”hansard import --source codebuddy --since allhansard index rebuildhansard config sources add codebuddyhansard 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 toCodeBuddy, 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”- User, assistant, reasoning, tool-call, tool-result, and compaction records when the published shape provides them.
- Per-message usage and linked subagent runs.
- Working directory from the record itself rather than reversing CodeBuddy’s lossy project-folder name.
- Counts of every record type Hansard does not recognize.
Known limitations
Section titled “Known limitations”- The format was mapped from the vendor bundle, not a real CodeBuddy archive. Every field is therefore optional and coverage may change after live-store verification.
- Unknown records are counted in session metadata but are not invented as visible turns.
Refresh an existing archive
Section titled “Refresh an existing archive”hansard import --source codebuddy --since allhansard index rebuild