Browse conversations
The Hansard viewer reads the normalized local archive. It provides conversation, project, memory, activity, and research views without requiring a hosted account.
Open the viewer
Section titled “Open the viewer”hansard appOn macOS, Hansard activates the separately installed native app when it is available. Otherwise the command opens the local browser viewer.
hansard webThis starts the local viewer and opens it in the default browser.
hansard web --no-openThis prints the local address and leaves the viewer running without opening a browser window.
Move through the archive
Section titled “Move through the archive”The primary navigation separates different ways of reading the same archive:
- Conversations lists archived sessions by project or scope, ordered by recent activity.
- Projects summarizes work by repository and exposes linked subagent runs.
- Memories shows provider memory files and their snapshot history.
- Stats, Usage, and Behavior provide activity and resource views.
- Deep Recall researches questions across multiple complete sessions.
- Settings controls viewer, import, privacy, notification, and sync options.
Select a folder or project in the rail, then select a session. Long lists use a load-more control rather than loading the complete archive at once.
Read a session
Section titled “Read a session”The session header shows the title and available provider, model, token, and archive metadata. The View menu switches between:
- Readable, which renders user and assistant messages, context, tool calls, results, and diffs as structured cards.
- Source, which shows the generated conversation Markdown.
Tool cards load their full arguments and results when opened. When a parent session has linked subagent transcripts, expand the child list or use the Original, previous, and next controls in the session header.
Use the transcript finder to search within the currently open session. Use archive search when the target session is not yet known.
Continue or hand off
Section titled “Continue or hand off”Supported local provider sessions include a composer for continuing the native conversation. The Continue in… menu can instead start a handoff in another installed harness, and project rows expose a new-conversation action.
Autocomplete follows each harness’s own syntax:
| Harness | Command or skill syntax |
|---|---|
| Codex | $ for effective skills, apps, and plugins; @ for files and plugin mentions |
| Claude Code | / for commands and user-invocable skills; @ for files |
| OpenCode | / for custom commands; @ for files |
| Grok | / for commands and user-invocable skills; @ for files |
| Devin CLI | @skills: for user-triggered skills; @ for files |
OpenCode skills are tool-activated resources rather than direct /skill-name
entries. Configured MCP servers stay available inside each harness but are not
shown as a synthetic @server prompt token. Desktop notifications configured
under Settings → Notifications fire when an orchestrated task completes,
fails, needs approval, or needs typed input, including while another pane is
open.
Inspect a session from the terminal
Section titled “Inspect a session from the terminal”Print the human-readable conversation:
hansard show <session-id>Print its Markdown path:
hansard show <session-id> --pathReturn a bounded latest-message window for an agent or script:
hansard show <session-id> --json --msg-limit 20Export the normalized session bundle to a chosen directory:
hansard export <session-id> --out ./session-export