Give an agent memory

An agent’s context resets every session; a project does not. Save something worth keeping once, and find it again weeks later by meaning rather than by filename or timestamp. Over MCP, an agent reaches the store directly, with no glue code to maintain on your side.

What you need

• Remember & recall: embed and store a piece of text, then recall the closest ones back by meaning.
• MCP: the tools an agent calls directly, no SDK and no server code of your own.
• Automatic memory: the session-start/stop hook pattern that recalls and writes back without the model having to ask.

Doing it

nidus remember notes "Users authenticate with a bearer token issued at login." \
  --dir ./store

nidus recall notes "how do users sign in?" --dir ./store

The same two operations are remember/recall over MCP, so an agent calls them directly instead of shelling out.

What to tune

• Reinforcement: a recall can stamp nidus.access_count and nidus.last_accessed on what it returned, which a ranking expression can then read so an entry nobody asks for again sinks.
• Filters & metadata: scope memories to a project or a user, and combine that with recency-decay ranking so old notes fade rather than pile up.

Where it stops

One writer holds the store at a time. nidus stores what you tell it to remember and ranks it on recall; it does not decide on its own what is worth keeping.