Agent-facing guide

For agents

Use AIppocampus to find the source trail first, then decide what kind of answer the evidence actually supports.

Default stance

If old context may change the answer, use the smallest useful route before broad search. Treat summaries, semantic labels, and ambient scents as navigation unless source is open or bounded evidence is declared.

  1. Notice when continuity might matter.
  2. Open the smallest useful route or recall handle.
  3. Reopen source before exact, sensitive, stale, or disputed claims.
  4. Say when a route is blocked, stale, private, or insufficient.

Public surfaces

NeedUse
Human or script checksaippocampus CLI
Agent host read toolsMCP
Opt-in foreground recallagent recall, agent deepen, and agent explain
Provider-neutral importGeneric JSONL import
CI or local automationCLI --json and documented return codes
Trusted in-process command dispatchrun_command(capture_output=True)

Ten-minute path

Read-only agent check
uvx aippocampus --help
uvx aippocampus onboard --provider auto --status --format json

For the current complete Codex path after explicit consent:

Consented agent path
uvx aippocampus onboard --provider codex --all --format json
uvx aippocampus search "a distinctive old phrase"
uvx aippocampus agent recall "a continuity-sensitive cue" --json
uvx aippocampus mcp list-tools

Agent-readable files

Start with llms.txt for a compact agent overview, then use the public API docs when wiring tools.

Adapted from the public API, coding-agent memory lane, and AIppocampus runtime entrypoint.