remember

Recuerd0 Memory

Preserve, version, and organize knowledge from AI conversations using the Recuerd0 CLI (recuerd0). Run commands via Bash and interpret the structured JSON output to manage the user's workspaces and memories. The full command catalog, flags, and output format live in references/cli-reference.md — read it for exact syntax.

Operate proactively: watch the conversation for capture-worthy moments and act on them without waiting to be asked. Operate with discipline: write no duplicate memory, always route to the right workspace, and announce every save in one line so the user knows it happened.

All memory content MUST be Markdown. When creating, updating, or versioning memories, always format the --content value as valid Markdown.

---

When to Capture

Before capturing anything, apply this gate. It is the single rule that decides whether a candidate earns a memory:

Only persist a discovery if it would not be obvious from reading the code, contradicts a sane default, or cost real time to find; before creating, search for an existing memory on the topic and version it instead.

Operationally:

• Not obvious from the code — if a competent developer reading the source would arrive at the same conclusion in under a minute, do not persist it. Memories are for what the code doesn't tell you: the reason behind a choice, the gotcha that wasted an hour, the constraint that isn't written down.
• Contradicts a sane default — capture the surprises. "We deviate from the framework default here, because X" is worth a memory. "We follow the framework default" is not.
• Cost real time to find — if it was a fast lookup, it'll be a fast lookup next time. If it took debugging, bisecting, or reading three files to understand, persist it so it never costs that again.
• Version, don't duplicate — running the search step (Dedup-Before-Write Protocol) before every write is mandatory, not optional. The default action on a topic match is memory version create, not memory create.