Memory toggle
At the top of the tab, Enable memory turns the whole system on or off. When it’s off, the memory layers are skipped in the prompt and the memory tools are hidden from the model.Memory health
A rolling health score (last 14 days) summarises how well memory is serving your users, based on the feedback signals it collects:- Happy — a 👍 confirmed the recalled memory helped.
- Missing — the user indicated something should have been remembered but wasn’t.
- Too much — the user indicated Logic AI recalled too much or the wrong thing.
Rebuild from history
Rebuild from history scans every user’s past chat sessions and messages and seeds structured memory from them. Any legacy (Version 1) memory is migrated in, then cleared once it’s been folded into the new items. The rebuild is additive and de-duplicated, runs in the background, and uses credits for the analysis.Memory scopes
Memory items are grouped on the tab by scope:- Org context — org-wide facts that apply to everyone (e.g. pipeline stages, what “Enterprise” means). You review and curate these here — see Org memory review below.
- User context — per-user facts, grouped by user and expandable. Read-only here (each user’s items are private to that user; they curate their own from the chat via the Your Memory panel).
- Agent context — items the agent has learned that help it operate. Read-only; the agent self-curates.
Org memory review
Org-wide facts captured automatically don’t go live immediately. Each one lands as Pending review and is held out of everyone’s prompts until an admin acts on it, so shared memory stays deliberate. For each item you can:- 👍 Approve — start injecting it as a positive org fact.
- 👎 Approve as negative — keep it injected, but framed as something Logic AI must not do or treat as true (useful for “we don’t carry X”).
- ✏️ Edit — fix the wording; editing also approves it.
- 🗑 Delete — remove it entirely.
- ↗ Move to… — re-home the fact to a coworker (or your own memory) instead of keeping it org-wide — handy when an auto-captured fact really belongs to one coworker’s area of work.
Org schema knowledge (Deep Dive)
The Run org deep dive scan button scans every queryable object in your org — schema, relationships, record counts, and last activity — and asks the model to summarise what data your org holds and the workflows it supports. It produces two read-only blocks:- Data Structure — a summary of your org’s objects and relationships.
- Workflow — the workflows your data supports (this is what the
get_workflowtool returns to the chat).

