The blank-slate problem

Every coding agent — Claude Code, Codex, Cursor, Gemini — opens each session with no memory of the last one. It re-reads your codebase, re-asks the same questions, and re-makes the same mistakes. You spend the first ten minutes of every session explaining things the agent already knew yesterday.

The answer isn't a bigger context window. It's a memory that survives.

What a memory layer does

Termyte sits between you and your agent and quietly records what happens:

npm install -g termyte
termyte install claude-code

From then on, every tool call, file read, shell command, and final answer becomes a trace in a local SQLite database. In the background, Termyte synthesizes those traces into searchable memories. The next time you (or the agent) open the project, the relevant memories are right there.

Why local matters

There are cloud memory services. They send your code, your conversations, and your agent's actions to someone else's servers. Termyte doesn't. Everything stays in a single SQLite file on your machine. The embeddings model runs locally. The only optional network call reuses the LLM plan you already pay for — not a separate service.

Your memory belongs to you. It should stay on your computer.