Monet
About
Local-first, state-centric memory for coding agents — remembers your project's conventions and how you like to work. 100% local, over MCP
Details
- Author
- Unknown
- Categories
- AI, Developer Tools
Jump to
Monet · local-first memory for coding agents
Memory should change what your agent does.
The outcome should be the one you meant.
The correction you made once should never need making twice.
The longer you work together, the better it should get at what you want.
Paste this into Claude Code — more agents coming soon:
Set up Monet for all my projects: read https://raw.githubusercontent.com/team-monet/monet/main/harness/bootstrap/install.md and follow it, checking with me at each step.
Everyone asks for an apple. Everyone means a different one.
A capable model gives youanoutcome.
Yours needs the agent to know what you mean — and no first prompt says it all.
What you want has to reach the agentwhile it works.Not before. Not after.
Principles for always. Stages for the moment.
The few judgments that govern everything. Always in front of the agent. Almost nothing earns this place.
Everything else binds to a moment. When it arrives, the agent reads the rules that apply. Until then, they cost nothing.
Everything else simply isn't delivered.
The fewer things the agent carries, the more seriously it takes each one.
The perfect memory is a unicorn. We chase it anyway.
A memory thatalwaysturns intent into action doesn't exist.
Models change with every release; no promise survives that.
So Monet keeps score: which rule fired, at which moment, what the agent did.
One number should fall:how often you repeat a correction.
Nine months of building and breaking led here. Read the retrospective
The moment arrives. The rules are already there.
Mid-work, the agent recognizes a moment your store has rules for.
It reads them, and keeps going — in the direction you set.
you the release branch is green — can you cut 1.4.0?
agent Cutting a release is a moment this store has rules for. Reading them before I touch anything.
- Publish the client package only — the engine ships inside it.
- Bump the version field first; tag only after it's committed.
- Before publishing, verify the tarball actually carries the new engine.
from your store · read at the moment they apply
agent Version first, then the tag — the order the rules set.
agent Tarball check passes — the new engine is inside. Tagging; the release pipeline takes it from here.
agent Watching the pipeline: build green, publish green. 1.4.0 is live on npm.
1.4.0 is out: bumped, tagged, verified, published.
Drawn from a real session — condensed for the page.
with-monetinstalls Monet and runs the method:
restore at session start, read the rules when moments arrive, record what you correct.
This is what turns a generic coding agent into yours.
- One store at~/.monet— plain SQLite you can read, back up, export.
- Embeddings run on-device. No accounts, no API keys, no cloud.
- Works offline after the first model download.
Setup may download the local embedding model once. Nothing about your code is uploaded by Monet.
Memory should change what your agent does. Start here.
Paste this into Claude Code — more agents coming soon:
Set up Monet for all my projects: read https://raw.githubusercontent.com/team-monet/monet/main/harness/bootstrap/install.md and follow it, checking with me at each step.
Free for any project. All of it is open source.
Local code-knowledge graph + bi-temporal mistakes memory for AI coding agents. Serves a ranked structural packet instead of whole files on read/grep, and surfaces fixes your repo already reverted (mined from git history). Zero cloud, Apache-2.0.
OpenMemBrain is the intelligent membrane for AI coding memory. It autonomously reads and learns from your coding sessions — you never have to tell it what to save. It selectively absorbs project knowledge, blocks secrets, filters noise, resolves conflicts, and persists only what matters.
Governed memory for coding agents with trust lifecycle, conflict detection, staleness tracking, and health scoring. SQLite + FTS5, zero infrastructure. Works with Claude Code, Cursor, Codex, Windsurf.
Persistent project memory + architectural decisions + pre-execution safety hooks for Claude Code. Local-only storage, multi-repo workspace, automatic knowledge extraction via background auditor.
Add persistent project memory and smart task routing to Claude Code. Stop repeating context every session - Claude finally remembers your architecture, decisions, and patterns forever. 100% local, 17 MCP tools.
Provides perfect memory for AI-assisted development by capturing project context snapshots, enabling natural language search, evolution tracking, and code intelligence.
Dalexor MI is an advanced project memory system designed to provide AI coding assistants with Contextual Persistence. Unlike standard RAG (Retrieval-Augmented Generation) systems that perform surface-level keyword searches, Dalexor MI maps the logical evolution of a codebase, tracking how symbols, dependencies, and architectural decisions shift over time.
Graph-based long-term memory skill for AI (LLM) coding agents — faster context, fewer tokens, safer refactors
Engineering discipline and persistent memory for AI coding assistants
Your AI development companion. An MCP server that gives your AI persistent memory, structured specifications, and adaptive change management — so it builds what you actually want.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
