Jules
Jules stores no usable local conversation history, so its API is the only import surface. Hansard reads both archived and active sessions on each explicit run.
Source IDs
Section titled “Source IDs”| Source | Use it for |
|---|---|
jules |
Explicit Jules cloud API import. |
How the import works
Section titled “How the import works”Jules does not expose a local transcript store, so hansard import jules makes
an explicit, read-only API request using the existing Jules authentication. It
lists active and archived sessions, then reads each session’s initiating prompt
and typed activity stream. Plans, approval requests, progress updates, status
changes, shell actions, and change sets become ordered messages, tool activity,
and edits in the archived conversation.
The source context on the Jules task supplies repository attribution, and media returned by the API is stored as attachments. Jules does not expose model names, token usage, or cost through this interface, so those fields remain unavailable. There is no background watcher for this cloud source; running the command again refreshes the stored session snapshots and adds sessions created since the last explicit import.
Import and keep current
Section titled “Import and keep current”hansard import jules --since allhansard index rebuildSet JULES_API_KEY or jules.apiKey in Hansard config. A missing key prints
setup guidance instead of failing the entire import run.
Jules is an explicit network source and is not part of all or the local
watcher set. Rerun the import when cloud history should be refreshed:
hansard import jules --since 30dReview the import in the app
Section titled “Review the import in the app”After the import finishes, open Conversations and selectFilter & sort. Set Source toJules, 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 and agent messages, plans, approvals, progress updates, and terminal states.
- Shell artifacts with exit codes and change sets as structured edit calls.
- Media artifacts in the attachment sidecar.
- Repository attribution from the session source context.
Known limitations
Section titled “Known limitations”- Jules exposes no model identity and no token or cost usage. Sessions remain
unmodelled and unpriced unless
jules.modelHintsupplies user-declared attribution. - A session without repository context remains uncategorized.
- The API import is a snapshot; there is no local watcher path.
Refresh an existing archive
Section titled “Refresh an existing archive”hansard import jules --since allhansard index rebuild