Mention something in passing. The next morning — when it actually matters — the right store hears about it. Memory turns into action without you having to ask twice.
A copilot that re-asks "which store is Glendale?" every conversation isn't useful. The point of memory is that the agent shows up to work already knowing the building.
Capo's memory is structured. It's not a vector blob — it's typed entries with provenance, editable at any time.
How you like answers formatted, units, level of detail, default time windows.
Store nicknames, abbreviations, internal jargon. The agent uses your words back.
What you check first thing in the morning. Surfaces unprompted on day-start chats.
Recipe names, vendor relationships, operational quirks unique to your business.
Who's on staff, their roles, who to cc. Nothing crosses owner accounts — fully isolated.
Memory is account-scoped. There is no cross-tenant leakage. Every entry is auditable and editable by the owner.
Your memory database is yours. It is not used to train base models. It is not visible to other Capo customers — ever.
View every memory entry. Edit. Delete. Pause learning. The owner has the final say on what the agent remembers.