The project
remembers.
0ctx captures sessions, checkpoints, and decisions at the repo level. Switch tools — the context follows.
1. Install dependencies:
bash npm install2. Configure environment: Copy
.env.example to .env.localEvery AI session starts from zero.
You switch tools. You close a tab. You come back tomorrow. The context is gone.
Sessions vanish
Close the tab, lose the thread. No tool remembers what the last one discussed.
Decisions evaporate
You made a call and moved on. The reasoning lives in a chat log you’ll never reopen.
Context silos
Each AI tool builds its own understanding. Nothing transfers between them.
SESSIONS
Conversations captured automatically, tied to branches and commits. Every turn preserved.
CHECKPOINTS
Decision snapshots at meaningful moments. The ‘why’ behind the ‘what’ — always recoverable.
WORKSTREAMS
Parallel work contexts within a repo. Feature branch memory stays cleanly isolated.
INSIGHTS
Reviewed learnings that persist across sessions. Cross-session knowledge that compounds.
Four steps from install to persistent project memory. Zero configuration, zero cloud dependencies.
Install
$ npm i -g @0ctx/cliInstall the CLI globally. One command, nothing else to configure. Works on macOS, Linux, and WSL.
Enable
$ 0ctx enableRun inside any repo. A local daemon starts, binds the workspace, and begins capturing automatically.
Work
Use any AI tool — Claude Code, Cursor, Copilot. 0ctx captures sessions, decisions, and context in the background.
Recall
Switch tools or come back tomorrow. New sessions inherit full project memory via MCP. Zero context loss.
Local SQLite graph
No cloud, no latency. Your data stays on your machine.
MCP protocol
Tool-agnostic capture and recall. Not locked to any vendor.
Repo-bound
Context lives with the code. Clone the repo, get the memory.
Zero config
Works with Claude Code, Cursor, and any MCP client.
0ctx uses the Model Context Protocol. Any tool that speaks MCP gets full project memory automatically.