Deep Recall

Deep Recall is Hansard’s archive-research workflow. It is intended for questions that require several searches, full-session reading, timelines, or comparison across providers and projects.

Use normal search and recall when one query or one known session is likely to answer the question.

Run from the viewer

Open hansard app or hansard web, choose Deep Recall, select an available Codex or Claude model, and submit a question. The viewer shows planning, search, reading, synthesis, and citation-checking stages as the run progresses.

Research threads are stored separately from normal conversation sessions. They do not appear in Conversations, history search, Stats, Projects, or notifications.

Run from the terminal

hansard deep-recall "Compare the migration approaches and explain why each was abandoned"

The default backend is the authenticated Codex CLI. Select Claude or a specific model when needed:

hansard deep-recall "Build a decision log for the authentication rewrite" \
  --repo github.com/acme/widgets \
  --backend claude \
  --model opus

Constrain archive coverage with the same structured dimensions used by history search:

hansard deep-recall "How did the cache strategy change?" \
  --provider codex-cli \
  --since 90d \
  --limit 8

Use --json when an agent or script needs the plan, ranked candidates, reader reports, citations, and coverage information:

hansard deep-recall "Did the recovery plan change later?" --json

How a run works

A planner turns the question into keyword, project, provider, tool, command, and time-window searches.
Hansard runs those searches against the canonical history index and combines repeated hits.
The strongest candidates are opened as complete normalized session dossiers.
Isolated reader calls evaluate individual sessions against the original question.
A final synthesis combines the reader reports and places [session:<session-id>] citations beside archive-dependent claims.
Hansard validates cited session IDs and records coverage limitations.

CLI options

Option	Purpose
`--backend codex\|claude`	Select the authenticated CLI runner.
`--model <id>`	Select a model; omit it to use the CLI default.
`--repo <repo-or-path>`	Constrain planned searches to a project or path.
`--provider <provider-or-alias>`	Constrain archive results to a provider.
`--tool <name>`	Require a normalized tool name.
`--command <head>`	Require a parsed shell command head.
`--since 90d\|all`	Constrain the archive time window.
`--limit <count>`	Set the maximum number of complete sessions to read; the default is 12.
`--json`	Return the complete research payload.

A claim with a valid session citation can be traced to a selected archived conversation.

Research threads remain local-only in the current sync contract because one answer can combine evidence from several otherwise unrelated projects.