Repeated context
Architecture, edge cases, and decisions get re-explained across assistant sessions.
Promemo
Promemo saves decisions, architecture notes, TODOs, and handoff context as durable Markdown inside your repository.
npm install -g promemo@latestWorkflow preview
promemo load authentication --related --token-budget 1200
# Example output:
# authentication
# Current state, decisions, and nearby feature hints.promemo save product-direction --stdin
# Example output:
# Saved feature memory: product-direction
# Updated summary, decisions, and TODOs.promemo search "why did we choose passkeys" --hybrid --limit 5
# Example output:
# authentication/decisions.md
# Related feature: identityProblem
Every assistant session starts colder than it should. You re-explain architecture, data models, edge cases, and what not to change. Promemo keeps that reasoning beside the code, so future sessions can load durable context instead of guessing from chat history.
Architecture, edge cases, and decisions get re-explained across assistant sessions.
Important project knowledge stays trapped in chat history instead of living with code.
Local memory
Promemo is project memory for developers who want AI assistants to remember architecture, decisions, TODOs, APIs, and handoff context without moving that memory into another hosted workspace.
Promemo writes durable Markdown under .promemo/ so local memory can be reviewed, diffed, merged, and committed with the code it explains.
Use Promemo to load project memory into Claude, Codex, Cursor, and other MCP-capable tools before the next AI-assisted development session starts.
If your search starts with Supermemory or Minimi, Promemo is the Git-native option for teams that want memory owned by the repository.
Promemo keeps local project memory searchable through CLI commands, MCP tools, and a generated retrieval index.
Product
Promemo stores project, shared, and feature memory under .promemo/. Generated summaries, decisions, APIs, data model notes, TODOs, and prompts stay human-readable, reviewable in pull requests, and committed like any other project artifact.
.promemo/
project.md
config.toml
index.json
features/
authentication/
memory.md
notes.md
shared/
architecture.md
coding-guidelines.md
notes.mdFeatures
Turn assistant or human handoffs into durable feature memory.
Give the next AI session current state, decisions, TODOs, and prompts.
Review, diff, merge, and commit human-readable .promemo/ Markdown.
Generated regions can be rewritten while notes outside them stay intact.
Snapshot branch, changed files, commits, TODO/FIXME comments, and memory.
Build a local index for keyword, semantic, and hybrid memory search.
Use CLI, JSON contracts, and expanded MCP tools without changing the memory format.
Download / Install
Install Promemo globally with npm, run it with npx, install it through Homebrew, use the direct release installer, install a tagged Cargo release, or build from the source repository.
npm install -g promemo@latest
promemo --versionnpx -y promemo@latest --versionbrew tap seguelabs/tap
brew install promemo
promemo --versioncurl -fsSL https://raw.githubusercontent.com/seguelabs/promemo/main/scripts/install.sh | shcargo install --git https://github.com/seguelabs/promemo.git --tag v0.4.0 --forcegit clone https://github.com/seguelabs/promemo.git
cd promemo
cargo install --path .Quick Start
Get started with Promemo and begin building durable project memory.
Initialize Promemo from the root of a Git repository.
Save a short handoff into feature memory.
Inspect, load, search, and open memory as you resume work.
promemo initcat <<'EOF' | promemo save authentication --stdin
# Authentication
- Refresh tokens rotate on every use.
EOFpromemo tree
promemo tree --jsonpromemo load authenticationpromemo search "refresh token"promemo open authenticationWorkflow
Promemo does not require a hosted backend, does not store raw transcripts, and does not lock memory inside one AI provider. The durable source of truth is Markdown in your repo; the CLI and MCP integrations read and write through the same core engine.
No hosted backend is required. The durable source of truth is Markdown in the repository.
CLI commands, JSON contracts, and MCP integrations read and write through the same core engine.
If Promemo disappeared tomorrow, your project memory would still be readable, reviewable, and portable.