TIMPS — Persistent Memory for AI Coding Agents

Claude Code, Cursor, and Windsurf forget everything the moment you close the session.
TIMPS is an MCP server that gives them memory that survives restarts — architecture decisions, past bugs, your conventions.
Free and fully local with Ollama. No API key required to try it.

Read in: English • 日本語 • Deutsch • Español • Français • हिन्दी • Português

Status: solo project, early. The MCP server and CLI are the parts I actually use daily and trust. Everything else in this repo (desktop app, mobile, JetBrains, plugin marketplace) is younger and less tested — flagged below. I'd genuinely rather you try the core and tell me it's broken than read marketing copy.

Try it in 30 seconds

npx timps-code "what does this codebase do?"

No install, no config, no API key. Point it at any repo. If you have Ollama running locally, this is 100% free and nothing leaves your machine. If not, it'll walk you through picking a provider.

To actually get persistent memory in Claude Code, Cursor, or any MCP client, add the MCP server:

npm install -g @timps-ai/timps-mcp

then point your MCP client at it (config instructions in MCP Setup).

What it actually does

Ask Claude Code to fix a bug today. Close the session. Ask it something related tomorrow — it has no idea what you decided yesterday, what you already tried, or why you structured something the way you did. You end up re-explaining the same context every single session.

TIMPS sits between you and your agent as an MCP server and keeps a memory store per project:

• What it remembers — architectural decisions you've made, patterns and conventions specific to your codebase, bugs you've already hit and how they were fixed, and a plain audit log of what it wrote and why.
• Where it lives — local JSON/SQLite files by default, keyed per-project so different repos don't bleed into each other. Optional Postgres/Qdrant if you want it shared across a team.
• What it costs — free if you run Ollama locally. Optional paid providers (Claude, GPT, Gemini) if you want their reasoning quality instead.

That's the whole pitch. It's a memory layer, not a new agent — it works alongside whatever coding agent you already use.

How it works (short version)

Under the hood, memory is organized in a few real tiers:

1. Working memory — current session: active files, recent errors, live goals. Cleared on exit.
2. Episodic memory — a log of past sessions and their outcomes.
3. Semantic memory — the durable stuff: patterns, conventions, decisi

... View full README on GitHub