GitHub Copilot

Copilot terminal, editor, and cloud coding-agent histories come from different stores. Import local CLI and editor sources together; retrieve coding-agent work explicitly through GitHub.

Source IDs

Source	Use it for
`copilot-cli`	GitHub Copilot CLI session events and workspace metadata.
`copilot-ide`	Copilot Chat sessions from VS Code-family editors.
`copilot-agent-cloud`	Explicit cloud coding-agent import through GitHub.

How the import works

For Copilot CLI, Hansard reads the session event stream and its saved workspace state. For editor chat, it reads the Copilot records stored in VS Code-family workspace storage. Each path reconstructs messages and available tool, edit, model, and usage records in the order written by that surface, while joining only metadata that belongs to the same bounded session or workspace.

The explicit cloud importer retrieves coding-agent sessions through GitHub and joins the prompt, transcript, premium-request charge, repository, and pull request context by the provider’s session identifier. Cloud billing is reported as premium requests rather than fabricated token totals. Sessions belonging to other participants remain separate, and missing tool arguments or usage fields stay visibly absent. Reimporting refreshes the same provider records.

hansard import --sources copilot-cli,copilot-ide --since all
hansard import copilot-agent-cloud --since all
hansard index rebuild

The cloud import uses GH_TOKEN, GITHUB_TOKEN, Hansard config, or the GitHub CLI’s stored login.

hansard config sources add copilot-cli
hansard config sources add copilot-ide
hansard watcher restart

Coding-agent imports remain explicit and are not part of all.

Review the import in the app

After the import finishes, open Conversations and selectFilter & sort. Set Source tothe matching GitHub Copilot CLI, VS Code, or coding-agent 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

CLI messages, tools, lifecycle events, routing telemetry, workspace data, bounded sidecars, tokens, premium-request multipliers, and AI credits.
VS Code-family chat messages, thinking, tool activity, terminal commands, file edits, titles, timing, and diff statistics when the editor recorded them.
Cloud coding-agent prompts, transcripts when available, model identity, premium-request charge, pull-request attribution, and distinct retry runs.

Known limitations

VS Code versions before 1.109 do not record per-request token usage.
Editor serialization drops most tool arguments; terminal commands, confirmation inputs, todo lists, and subagent calls retain more detail.
Cloud coding agents report premium requests or AI credits rather than tokens. Their transcript endpoint is not a stable public API, so an unavailable transcript degrades to metadata instead of failing the whole import.
Sessions answered by another registered editor participant are left to that provider.

Refresh an existing archive

hansard import --sources copilot-cli,copilot-ide --since all
hansard import copilot-agent-cloud --since all
hansard index rebuild