Cloud The core runtime is open source and free. TekMemo Cloud (hosted sync, managed MCP, team features) is in early access. Join the waitlist →
Skip to content

TekMemoYour AI agents forget. TekMemo doesn’t.

Local-first memory for AI agents — versioned, portable, and always there when the next session starts.

Core MemoryArchival MemoryRecall MemorySync State

Works with Claude Code·Cursor·Codex·OpenCode·any MCP client

The problem

Every new session starts from zero.

You walk your agent through the auth system. It gets it. Next session — a blank stare. You paste the architecture doc again, and it ships code that contradicts last week's decision. It has no memory of what you chose, because there was nowhere to put it.

How it works

Three commands. Your agent remembers.

1

Install

$ npm install -D @tekbreed/tekmemo-cli
2

Initialize

$ npx tekmemo init
✓ Created .tekmemo/ with core memory, notes, recall indexes, and graph files.
3

Record

$ npx tekmemo remember "Auth uses JWT with refresh rotation" --tag auth
✓ Saved to core memory.

Next session, your agent already knows. No repeating yourself. No contradictions. No "what were we working on again?"

File-first

Open it. Diff it. Commit it.

Every decision, convention, and note sits in plain text under .tekmemo/. Open it in your editor. Diff it in review. Commit it with your code. Memory stops being a black box.

Learn about file-first memory →
.tekmemo/
manifest.json
memory/
core.md
notes.md
events/
memory-events.jsonl
conversations.jsonl
indexes/
chunks.jsonl
graph/
nodes.jsonl
edges.jsonl
snapshots/
snapshots.jsonl
Recall

The right memory, fetched for you

Stop scrolling through old prompts. TekMemo indexes your memory and returns the fragment that fits the task — semantically, not by keyword. Hybrid recall merges lexical and vector search, then reranks.

See how recall works →
Query"How does auth work?"
0.94
core.md · Auth decisionsJWT with refresh rotation. Access tokens expire in 15min…
0.87
notes.md · Auth flow notesToken validation middleware checks expiry and signature…
0.71
conversations.jsonl · Session 42User decided to switch from session-based to JWT auth…
Runtimes

One engine, three ways to run it

Local mode works offline. Hybrid adds a cloud replica so your memory follows you across machines. Managed runtime is on the roadmap. The engine and the API stay the same — you only change how memory is stored and synced.

Explore the cloud client →
Zero cloud. Works offline.
import { Tekmemo } from "@tekbreed/tekmemo";

// Default. Memory lives in .tekmemo/ as markdown + JSON.
// No API keys, no network. Read it, diff it, commit it.
const memo = new Tekmemo({
  mode: "local",
  rootDir: "./.tekmemo",
  projectId: "my-app",
});
Built for how you work

Two ways in

🧩

Building AI apps

Give your app durable memory. Import @tekbreed/tekmemo — the same API whether memory lives in local files, the cloud, or both. The AI SDK runtime ships recall, context-building, and a tool definition ready to wire into any agent.

See the API reference →
🤖

Using a coding agent

Your coding agent finally remembers your project. Install the MCP server, drop one config block into Claude Code, Cursor, or Codex, and your agent gets project context every session — automatically.

Connect your agent →
Why file-first

TekMemo vs. hosted memory tools

Most memory tools hide your data in a dashboard you can't inspect. TekMemo stores everything as plain text and JSON in your project's .tekmemo/ directory — alongside the code it describes.

FeatureTekMemoHosted Memory Tools
Where memory lives Plain files in your repoLocked in a remote dashboard
Inspect & edit Any editor, any diff toolVendor UI only
Version control Git-tracked with your codeSeparate system (if at all)
Ownership You own every byteVendor-dependent
Offline support Full offline by defaultRequires internet

MIT Licensed · 100% open source

One command. Your agent never forgets.

npx tekmemo init
View on GitHub

Released under the MIT License.