Qwen Code

Hansard treats Qwen Code as a historical import source. It recognizes five source-audited layouts across the legacy runtime tmp/ tree and the later projects/ tree, while excluding transient runtime sidecars.

Source IDs

Source	Use it for
qwen-code	Historical prompt logs, manual checkpoints, monolithic chats, active-chain JSONL, archives, and linked subagent runs.

How the import works

Hansard scans the official Qwen runtime layouts: project prompt logs and manual checkpoints, legacy monolithic automatic JSON, and current or archived tree JSONL. Tree replay starts from the last physical non-artifact record and follows its parentUuid chain. Compatible fragments sharing one UUID are aggregated; abandoned rows remain preserved only in raw evidence.

Subagent records become linked child conversations, and scheduled-prompt metadata remains provider context rather than a fabricated human turn. An automatic transcript supersedes a duplicate prompt-only session without joining their source files. Manual checkpoints remain independent sessions. Legacy monolithic history has no recorded cwd, so Hansard leaves it uncategorized instead of reverse-mapping the project hash.

When a matching row exists in the global usage_record.jsonl, Hansard adds its duration, tool-outcome, and edited-line summary. The exact stable-read ledger bytes are content-addressed as a shared raw auxiliary, so a raw replay cannot silently consume a newer ledger.

Import and keep current

Import saved history

hansard import --source qwen-code --since all
hansard index rebuild

Historical source boundary

Rerun the saved-history import when the provider records change. Hansard does not install, launch, or configure Qwen Code as a live agent workflow.

Review the import in the app

After the import finishes, open Conversations and selectFilter & sort. Set Source toQwen Code, 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

• Chat messages, reasoning, tool calls and results, diffs, and per-message usage from structurally matched historical formats.
• Prompt-only sessions and path-scoped manual checkpoint context.
• Archived chats and each delegated agent journal as a linked run.
• Scheduled-run and runtime-notification prompts as provider context rather than human activity.
• Exact raw source bytes, including the optional shared usage auxiliary.

Known limitations

• Lock files, temporary streams, and other live runtime sidecars are excluded from the session boundary.
• Unknown tree record types or broken parent chains fail closed instead of selecting the nearest known converter.
• Historical executable release probes remain pending; the current boundary is based on official tagged source through v0.21.8.

Clean reimport required

Parser suffix 2 changes discovery, timestamps, branch replay, and usage raw evidence. Reimport from the original Qwen records instead of retaining older normalized metadata.

Refresh an existing archive

hansard import --source qwen-code --since all
hansard index rebuild