Practical overview
When it fits
Use Hippo when coding-agent context needs to persist locally across sessions or tools, and when you want memory files that can be inspected or tracked with project work.
Who it is for
- Developers using coding agents who want project context to persist between sessions.
- People working across supported agent tools who want a shared local memory store.
- Developers who want to inspect or commit agent-memory notes as Markdown.
Documented uses
- Create a local project memory store and connect documented coding-agent integrations.
- Save a project lesson and search for relevant stored context.
- Lower the ranking of a memory marked wrong or remove a superseded fact from recall.
- Import supported existing notes and histories into a shared memory store.
Requirements & limits
The documented CLI requires Node.js 22.16 or later. The repository identifies the project as MIT-licensed.
- The core store is local SQLite with readable Markdown mirrors.
- Default search is BM25 and does not require a model or network call.
- Automatic capture depends on completing setup and on the particular agent integration.
- Codex hooks require explicit trust through
/hooks; session capture also has a documented wrapper option. - Optional embeddings require an additional install or an opt-in API embedder.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install Hippo and initialize one project
Create a project memory store and let Hippo configure the agent integrations it finds.
Before you start
- Node.js 22.16 or later
- A project directory in which to run initialization
Steps
Install the CLI with the command below.
npm install -g hippo-memoryChange to the project directory and run
hippo init.
Expected outcome
Hippo creates a `.hippo/` store with SQLite and Markdown mirrors, and configures documented project or machine-level integration files for agents it finds.
Guide limitations
- Initialization adds instructions to an existing
CLAUDE.mdorAGENTS.md; it does not create those files. - Codex hooks run only after you trust them once in
/hooks. - Package installation alone does not enable automatic memory preservation for every agent.
Save and retrieve a project memory from the CLI
Add a note to Hippo and search the memory store.
Before you start
- Hippo installed and initialized in the project
Steps
Run
hippo rememberwith the note and an optional tag.Run
hippo recallwith a search query.
Expected outcome
The note is stored and can be retrieved through Hippo's documented BM25 search.
Guide limitations
- The README examples document the commands but do not specify a guaranteed search result.
- Default BM25 search uses no model or network call; embeddings are an optional separately installed feature.
Compare options for AI coding assistance
These projects document a common task and share a project role. This is a source-based comparison, not an execution benchmark or a guarantee of interchangeability.
| Project | Documented purpose | Platform | Access and requirements |
|---|---|---|---|
| Hippo | Create a local project memory store and connect documented coding-agent integrations. | CLI, Self-hosted | The documented CLI requires Node.js 22.16 or later. The repository identifies the project as MIT-licensed. |
| Continuum — pouyahasanamreji | Store project lessons so coding agents can retrieve them across conversations. | CLI, Self-hosted, Server | The repository documents local Docker Compose and bare-metal development setups. Bare-metal startup requires Node 22.12.0 or later and pnpm 10.33 or later; the Compose path skips these host prerequisites. |
| Haft | Record the problem a project is solving and the options considered. | CLI, Self-hosted |
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 12 October 2026
- Original website title
- kitfunso/hippo-memory · Official homepage title · retained in its source language

