An agent that forgets everything between sessions is a junior that never learns. NIBWP’s Memory abilities give your agents a persistent, on-site memory — facts, preferences and context they can store and recall — so they get more useful over time instead of starting from zero every conversation. This guide explains how Memory works and how to use it well.
The nibwp/memory-store and nibwp/memory-recall abilities let an agent save and retrieve facts on your site — your brand voice, your conventions, project context. Memory lives on your WordPress install, under your control, and makes every future session smarter.
What Memory is for
Memory turns one-off instructions into lasting context. Tell an agent your brand voice once, have it store that, and every future draft follows it — without you repeating yourself. The same goes for naming conventions, project facts, or preferences about how you like things done.
The two abilities
| Ability | What it does |
|---|---|
nibwp/memory-store | Save a fact or preference to the site’s memory |
nibwp/memory-recall | Retrieve relevant memories to inform the current task |
Using it in practice
You rarely call these directly — you tell the agent something worth remembering, and it stores it; later, it recalls what is relevant:
You: Remember that our blog voice is plain, concrete, no hype —\n and we always link to a related post.\nnibwp/memory-store { fact: voice + linking convention }\nStored. I will apply this to future drafts.
Why it matters
- Consistency — every draft follows the same voice and conventions, automatically.
- Less repetition — you stop re-explaining the same context each session.
- On your site, under your control — memory lives on your WordPress install, not a third party.
- Compounding usefulness — the more an agent learns about your site, the better it works.
FAQ
Where is memory stored?
Do I have to manage it manually?
Should I store sensitive data?
Give your agents a memory
Store your conventions once and have every future session apply them.
Get NIBWP