You work across projects, across tools, across weeks. memnant carries what you decided from one session to the next, from one project to every project.
Context windows die. Conversations end. Three weeks later you're re-explaining the same decisions to the same agent. memnant is the remnant that survives.
The agent logs silently as you work. Decisions, framework fixes, rejections, product calls. Every record gets a vector embedding for semantic search. You don't do anything — it just remembers.
Next session starts with what matters. Last session's summary, open TODOs, relevant decisions, staleness warnings. Not a raw dump — the relevant subset, with what's changed since you were last here.
It knows when knowledge goes stale. When a file changes, memnant scores whether the change actually affects related decisions. Semantic confidence, not a binary flag. A renamed variable doesn't invalidate an architecture decision.
Knowledge crosses projects automatically. Framework fixes and rejected approaches promote themselves to a machine-local colony. The gotcha you solved in one codebase is already waiting in the next.
Multiple builders, one shared understanding. Knowledge logged by one builder is available to all. Contradictions detected automatically. New team members get an onboarding brief — key decisions, patterns, gotchas — in minutes, not days.
Remembering is the start. What makes knowledge useful is how it connects, what fades, what stays, and what gets enforced.
~/.memnant/colony.db. Framework fixes and rejected approaches auto-promote across all your projects. Deduplicated by embedding similarity..memnant/ledger.db — copy it to another machine and everything comes with you.memnant — one command. Auto-detects: first run → setup, after that → session start.memnant.yaml at your project root. Version-controlled. No dashboard. No account. No login.One command. Full context. The agent already knows the rest.
how to install · no dependencies · works offline