Ada keeps a short set of durable facts about your team: your website, your product, the tools you prefer, the conventions you work to. Those facts go into every conversation she has, so keeping them accurate is the quickest way to improve her answers. This guide covers reading that memory, correcting it, and knowing what belongs in it.
See what the AI remembers
- Select your team name at the top of the sidebar, then Settings.
- Select the Memory tab.
Everything Ada has learned about your team sits in one editable box. It starts empty and fills up as you work with her.
Add or change a fact from chat
The fastest route is to tell Ada in a chat:
/remember our website is newurl.comadds or updates a fact/remember forget that our website recently changedremoves one
She also picks facts up on her own when you mention something lasting in passing. Either way she shows you an approval card first, so she never saves anything you have not approved.
Edit it yourself
Team managers can edit the memory box directly. That is the quickest way to correct something out of date, or to paste in context Ada has never been told.
- Go to Settings, then the Memory tab.
- Edit the text.
- Select Save.
Clearing the box empties the memory. Team members see the same memory, but read-only. See roles and permissions.
Keep it short
Memory travels with every message Ada sends, so a long memory costs you on every turn and buys you little. The box holds up to 10,000 characters, but only the first and last 2,500 reach the AI. Go past 5,000 and the character count turns amber to tell you the middle is being skipped.
If you are near the limit, cut it back to the facts that change how Ada answers rather than everything true about your company.
What belongs in memory
Memory is for durable facts, not for the job in front of you:
- Good: your domain, your product and pricing model, your ideal customer, the analytics tool you trust, naming conventions, a preference for one channel over another.
- Leave out: today’s question, one-off requests, anything already in your campaigns or your goal.
Your positioning, audience and channel thinking belong in your team strategy instead, which Ada also reads. Memory is the correction layer on top: when the two disagree, memory wins. You update memory the moment something changes, while a strategy document is written once and revisited rarely. So if Ada keeps repeating something out of date, the fix is almost always in memory.