What org memory covers
remember_fact saves a durable memory of one of three types, a fact, a preference, or a lesson, and is meant for standing things worth knowing long-term, not a note about one specific candidate, which belongs on that candidate's own pipeline record instead.
The distinction between the three types is mostly about framing: a fact is neutral information about the company, a preference is how you like something done, and a lesson usually comes from something that didn't go well the first time.
search_org_memory looks up what's already been saved by a query, and an empty query returns the most recently saved memories instead, so it works as both a search and a quick review of everything on file. forget_org_memory retires a memory you name specifically as outdated or wrong, and it's the only way a saved memory ever goes away.
A walkthrough: a policy that changes mid-year
An employer says: "remember that we never hire without a work sample." The agent shows an approval card, "Save fact to org memory: 'we never hire without a work sample'?", and once approved, that preference is on file.
Two months later, in a completely different conversation, the employer asks the agent to help draft a screening rule for a new role, and the agent checks org memory first, surfaces the work-sample preference, and suggests folding it into the rule without being reminded. Later still, the policy changes.
The employer says: "forget that note about requiring a work sample, we don't do that anymore," and the agent confirms: "Forget org memory [id]? This cannot be undone," before retiring it for good. The next time a screening rule comes up in conversation, the agent no longer brings up a preference that no longer applies.
Boundaries
What memory does and doesn't hold onto
Saving a new memory always requires your approval, with the exact content shown on the card before it's stored. Searching or listing what's already saved never requires approval, since it changes nothing, so checking what's on file is always a safe, free action.
Forgetting a memory requires approval too, and it's permanent, once retired, a memory is gone rather than archived, so there's no way to bring back a memory you forgot by mistake short of stating it again.
This tool group is for standing, company-level knowledge; a note about a single candidate belongs on that candidate's own record instead, through add_candidate_note, and the agent is expected to route it there rather than into org memory, keeping the two kinds of information from blurring together.
Frequently asked questions
Does the agent remember things about my company automatically, without me asking?
No, saving a new memory through remember_fact requires your approval, with the exact content shown before it's stored. It doesn't save standing preferences on its own without you stating one.
Can I see everything the agent has remembered about how we hire?
Yes, search_org_memory with an empty query lists the most recently saved memories, and a specific query searches within them, with no approval needed for either.
What happens if a saved policy changes?
You can ask the agent to forget a specific memory you name as outdated, using forget_org_memory. It requires approval and is permanent once confirmed.
Should I use org memory for notes about a specific candidate?
No, that belongs on the candidate's own pipeline record through the note tool covered on the pipeline automation page. Org memory is for standing, company-level facts and preferences, not one-off candidate details.
What's the difference between a fact, a preference, and a lesson in org memory?
A fact is neutral company information, a preference is how you like something handled, and a lesson usually reflects something learned from a specific situation that didn't go as planned. All three are saved and searched the same way.
Related pages
Save a preference worth remembering
Tell the agent a standing hiring rule once, and let it check that memory automatically in later conversations.