Check the CLI.
Make sure the package surface is reachable before touching memory.
Source-backed continuity
A local-first memory layer for agents that need a way back to the source, not a story about having remembered.
Fastest useful path
Probe without writing, ask before onboarding private history, then search for one source-backed snippet.
Make sure the package surface is reachable before touching memory.
Use read-only status first; choose a provider-specific onboarding path only when allowed.
Use a distinctive old phrase and reopen source before strong claims.
uvx aippocampus --help
uvx aippocampus onboard --provider auto --status --format json
uvx aippocampus onboard --provider codex --all --format json
uvx aippocampus search "a distinctive old phrase"
Clean source and explicit references outrank generated summaries.
Memory should surface when it helps, not turn every prompt into a personal profile.
Conversation source, registry rows, indexes, and sync bundles are private by default.
Why it exists
A bright new session can still feel strangely newborn. AIppocampus gives a future agent a way to return to the thread honestly, with the path, the source, and the limits still visible.
Explore
No. AIppocampus gives agents a reliable local path back to source. The model itself still has no inner autobiography of you.
No. Coding agents are the cleanest pressure test, but the project is about life-wide continuity: corrections, reading notes, recurring questions, unfinished work.
No. Public code and docs are different from private conversation source, indexes, and sync bundles, which stay on your machine unless you opt in.
Use a narrower tool if you only need a vector store, stateless RAG, or a hosted team profile. AIppocampus is heavier than a thin memory layer.