Agent integrations

Agent integrations let a coding agent search the Hansard archive without requiring direct access to archive files. The recommended setup installs an MCP configuration when the client exposes a compatible configuration surface, plus the best native command or skill surface available to that agent.

Install an integration

1. Initialize Hansard and import at least one source.

2. Add Hansard to the target agent.

   hansard integrations add-to codex

   Replace codex with claude, antigravity, devin, opencode, or grok.

3. Restart or reload the target agent so it reads the updated configuration.

4. Ask the agent to recall a focused topic or continue from a prior session.

Rerun the same add-to command after upgrading Hansard when generated recall instructions need to be refreshed.

Opt in to unified-memory retrieval

Provider memory can contain sensitive project conventions, paths, account context, and durable instructions. It is therefore excluded from agent integrations by default. Enable it explicitly for a trusted agent:

hansard integrations add-to codex --memories

The flag installs targeted memory-retrieval instructions and configures the MCP server to expose the read-only search_memories and get_memory tools. It does not let the agent create, edit, merge, or delete memories.

Memory access is a separate opt-in

An integration installed without --memories can search conversations only. Ordinary recall and continue-from workflows remain conversation-only even after memory retrieval is enabled; the agent or user must select the memory workflow separately.

Configure live session messaging

Local Codex and Claude Code sessions can discover and message each other through the same-project mode selected by default during new setup. Repair or change the managed integration with:

hansard peers setup

This enables the recommended same-project mode and adds messaging tools to Hansard’s existing Codex and Claude MCP entries. Existing sessions must restart once. No skill or manual link command is required. See Message live agent sessions for the drawer, CLI, scope, delivery, and safety behavior.

Configure cross-harness helper launches

Codex and Claude Code can launch bounded same-project helpers through the other default-on collaboration setting:

hansard agents setup

This also enables same-project messaging, then adds helper tools to Hansard’s existing Codex and Claude MCP entries. Existing sessions must restart once. The init picker can uncheck both collaboration options, and unattended setup can use --no-agent-collaboration. See Delegate to helper agents for supported harnesses, nested ownership, queueing, safety limits, and the end-to-end transcript.

What gets installed

Native surfaces vary because agent clients expose different extension points.

Target	Installed surface
Codex	MCP configuration plus recall, continue-from, and Deep Recall skills.
Claude	MCP configuration plus slash commands and matching skills.
Antigravity	MCP configuration plus recall and continue-from skills.
Devin	MCP configuration plus recall and continue-from skills.
OpenCode	MCP configuration plus recall and continue-from commands.
Grok Build	MCP configuration plus recall and continue-from surfaces compatible with Grok Build.

Each target also receives its native memory-retrieval surface when --memories is present.

Historical import sources

The legacy Cursor CLI and Gemini CLI remain supported as historical transcript and memory import sources. They are not live integration targets. Use Grok Build for current Cursor-successor coverage and Antigravity for current Google agent coverage.

Deep Recall availability varies

integrations recall installs recall, continue-from, and Deep Recall surfaces where the target supports them. The standalone Deep Recall CLI and viewer are available independently of an agent’s native command system.

Install only the native recall files

Use integrations recall when the MCP configuration is managed separately:

hansard integrations recall codex

The current live targets are codex, claude, antigravity, devin, opencode, and grok.

Run the MCP server directly

Clients with a manually managed MCP configuration can launch the recall server over standard input and output:

hansard mcp serve

The server exposes search_past_sessions by default. To opt a manually managed client into memory retrieval, launch hansard mcp serve --memories instead. The memory-enabled server also exposes the read-only search_memories and get_memory tools. A manually managed Codex or Claude client can use hansard mcp serve --delegation; delegation implies the peer messaging tools. Generated integrations call the installed hansard executable, so a global installation must be available on PATH unless the client configuration supplies another executable path.

Recall workflows

Recall

Finds conversations relevant to a focused topic, then reads a bounded latest-message window before reporting the result.

Continue from

Reads both the opening and latest windows of the selected conversation so the original objective, current state, tests, and next action are available.

Deep Recall

Decomposes broad questions into multiple searches and synthesizes evidence from selected complete sessions with session citations.

Memories

Searches current-project and global memories together, then retrieves only bounded content from the selected records. This workflow is installed only with --memories and does not write to provider memory stores.

Generated instructions tell the agent to infer a focused query rather than passing an entire user request directly to archive search. Archive-dependent claims should remain tied to the selected session IDs.

Memory-enabled instructions tell the agent to search proactively when work depends on a prior preference, provider capability, durable project convention, or earlier decision. They do not inject the full unified memory archive into every prompt.