Renor is memory for coding agents: it keeps what you tell Claude Code, Codex or Cursor in a folder of Markdown files on your machine, and serves it back to any of them over MCP. Every new agent session starts from zero, so with Renor one agent saves a decision and the next one finds it. The memory is plain files you own, runs locally, and needs no account or API key.
Be the first to rate Renor. Your feedback helps other users decide.
One agent saves what it learned and the next session recalls it.
Notes live in a folder of Markdown files on your own machine.
Renor serves the same memory back to whichever agent you are using.
Similar tools in the same category — compare side-by-side
catnap is a Claude Code mod that lets Claude compact its own conversation and carry on by itself. Cl...
Pando deploys and shares apps. It turns the apps your team builds with AI into tools everyone can us...
code-mode is a Claude Code plugin that stops flooding Claude's context with MCP results. Claude writ...
Guides and comparisons about code tools
Ten Show HN launches that answer the same question differently: where does what an agent learned live, who owns it, and who can read it back?
Nine Show HN launches beneath the model: filesystems, snapshots, gateways and deploy tools that decide what an agent sees and what survives.
Nine launches that check agent work: per-call access policy, MCP server vetting, runtime verification, readable diffs and a hard stop at 95%.
Nine Show HN launches sitting under the agent: a model gateway, vectorless retrieval, on-device inference, an MCP browser layer and connectors for real systems.
Eight Show HN projects for trusting long agent runs: work context capture, distilled memory, folder fences, dollar budgets, plan review and tool governance.
