What is rememd
What it keeps, what it deliberately does not, and why that distinction is the whole product.
rememd keeps the reasoning around your work and hands it to whichever coding agent you are using. Not facts about the code - the code is the source of truth for those, and it moves. What was decided, what was ruled out and why, and what actually happened in a session: the part that ends when the session ends, and that no amount of reading the repository recovers.
Why it exists
Agent sessions are stateless. When you start a new session, the agent has no memory of what you decided last time, what failed, what's still pending, or why you chose one approach over another. You end up re-explaining context, making the same mistakes, or missing follow-ups.
rememd captures that context into structured markdown on disk, organized by workspace, product, focus area, and feature. The MCP tools let the agent read and write this context automatically - no copy-pasting, no manual handoff.
Which agents
rememd speaks MCP, so it is not tied to any one tool. Anything that speaks MCP can use it - point the client at rememd mcp-server and it works.
rememd never launches your agent. You start it however you already do, run rememd connect in that terminal, and the agent picks up context by calling get_feature_context - not from a file injected at startup. That is why there is nothing to configure per project and no "supported editors" list to be on.
Core value
- Every session ends with a structured log: what was done, what was decided, what to do next
- Every feature has a PRD + tasks + issues: the "why" and "what's left"
- Every focus area has a backlog: ideas captured as they emerge
- Every product has accumulated learnings: wisdom that outlives individual features
What you actually do
Most of the time you just talk to your agent. It calls the right rememd tools silently. You rarely think about "MCP" - you say things like "what did we do last time?" or "add this to the backlog" and the system handles it.
See Daily Use for how natural-language interactions map to actions.
What it isn't
- Not an issue tracker (though it captures issues)
- Not a task manager for humans (though it has tasks)
- Not a wiki (though it has markdown)
It is a continuity layer for AI-driven development.