It feels like preparing a library
AIppocampus scans local source, builds clean source, and prepares searchable indexes. It is not a hosted chat memory switch.
First useful path
Try AIppocampus locally before you configure anything ambitious: probe the CLI, check provider status, onboard only with consent, then search one old phrase from source.
Start with read-only checks:
uvx aippocampus --help
uvx aippocampus onboard --provider codex --status --format json
After you decide this machine may create local memory artifacts:
uvx aippocampus onboard --provider codex --all --format json
uvx aippocampus search "a distinctive old phrase"
AIppocampus scans local source, builds clean source, and prepares searchable indexes. It is not a hosted chat memory switch.
A useful recall result points back to earlier source. The agent can continue from evidence instead of acting as if it magically remembers.
Manual search proves the substrate. Prompt and lifecycle hooks make future continuity quieter after you trust the local setup.
Pause before onboarding if the workspace contains material you do not want in local memory artifacts.
Read the architecture page for the mental model, then the agent page if you are wiring AIppocampus into an agent host.
Adapted from the public wiki pages Getting Started and First Recall and Onboarding.