openltm

---

📣 Now open source

OpenLTM was born as a private memory layer for Claude Code. Today it's fully open source under MIT.

Same engine — automatic capture, semantic recall, importance-weighted decay, a queryable memory graph — now yours to read, fork, and extend. What started as one developer's "stop re-explaining my codebase" plugin is now an open foundation for agent memory across Claude Code, OpenCode, and Pi.

• 🔓 MIT licensed — no cloud, no account, no telemetry. Your memory lives in a local SQLite DB you own.
• 🧩 Provider-agnostic — one core (@rohirik/openltm-core), thin adapters per host.
• 🛠 Hackable — hooks, skills, janitor providers, and the graph visualizer are all in the open.

Migrating from an earlier install? The marketplace is now RohiRIK/OpenLtm and the plugin is openltm. Your existing memory database carries over.

---

The philosophy

Four ideas. No exceptions.

• Memory should be automatic. Hooks do the work. The session end hook extracts patterns, the session start hook injects them back. You shouldn't have to remember to remember.
• Decay is a feature, not a bug. A gotcha from six months ago that you never revisited probably no longer applies. Set importance: 5 to make something permanent — everything else ages out naturally.
• Semantic over keyword. FTS5 full-text search runs first; if it returns nothing, vector embeddings kick in. You search by meaning, not exact words — "how we handle async errors" finds the right memory even if you never wrote those exact words.
• Zero config, zero lock-in. Install once, works everywhere. Every setting has a sane default. The DB lives outside the plugin directory so it survives every update. No cloud, no telemetry, no account.

---

What you get

🔍 Recall	Past decisions, patterns, and gotchas — before you start work
🧠 Learn	Every session, automatically — no manual note-taking
💉 Inject	Top context at session start so Claude picks up where it left off
⏳ Decay	Stale memories fade while critical knowledge lives forever
🕸 Graph	Traverse relationships between memories for reasoning chains
🗺 Visualize	See your entire memory network in a browser-based explorer
⚡ Vec Recall	Semantic vector (KNN) recall via sqlite-vec; degrades to JS-cosine when unavailable
🔌 Extensions	sqlite-vec + Honker (queue/cron/pub-sub) loaded dynamically; graceful fallback without system libsqlite3

---

Install

Marketplace (recommended)

claude plugin marketplace add https://github.com/RohiRIK/OpenLtm
claude plugin install openltm

Restart Claude Code. That's it. Four Claude Code hooks + one git post-commit hook auto-wire, four commands load, five skills activate, and your openltm.db migrates or creates itself.

bunx (no clone)

bunx @rohirik/openltm-core          # auto-detect Claude Code, OpenCode
bunx @rohirik/openltm-core --pi     # experimental Pi adapter
bunx @rohirik/openltm-core --dry-run --claude  # preview without writing

Dev / git clone

git clone https://github.com/RohiRIK/OpenLtm ~/Projects/OpenLtm
cd ~/Projects/OpenLtm && bash install.sh

---

Quick Start

Start a new session. Context is injected at the top automatically.

Then try:

/openltm:memory recall auth       — what do we know about auth in this project?
/openltm:memory learn <insight>   — save something worth keeping
/openltm:health                   — memory health + decay summary
/openltm:project init             — set a goal for the current project

That's it. The rest is hooks doing the work.

CLI access for headless agents