/dashboard), as the Memory review tab beside Brain above the memory frame. Once the review has loaded, the tab shows how many conflicts and gaps are waiting.
Links to /memory-review still work: they redirect to /dashboard?view=review. Add &tab= with conflicts, gaps, timeEvents, sharing or solved to open a specific tab; any other value opens Memory conflicts.
Memory Review is a Cognee Cloud feature. In the local UI,
/memory-review redirects to the plain dashboard.The overview
Inside the frame, the review starts with a short summary:- Brain health: a percentage that starts at 100% and drops by 4 points for every conflict or gap still waiting, down to 0%.
- Memory conflicts and Memory gaps: the count of each. With none left, each line shows All conflicts solved or All gaps filled.
- Copy prompt to resolve all with the number waiting: copies one prompt that lists every open conflict and gap. Paste it into a connected agent and the agent checks the sources, keeps the value that holds, adds what answers each gap, and tells you what it changed. To work through them yourself, use See them in detail ↓, which scrolls to the tabs.
- Upcoming events: dated memories for the next 14 days, in UTC. Open calendar (or See all N events when there are more than three) opens the Upcoming events tab.
- Session learning: marked Coming soon.
Tabs
Below the frame, five tabs hold the details, in priority order: what needs a decision first, then what to read.Memory conflicts
A conflict means two sources state different values for the same fact, for example two documents giving different support log retention periods. Cognee finds conflicts when it reviews facts against the documents they came from, as part of improving memory. See Review Conflicting Facts. The tab, headed Memory that disagrees, lists every unresolved conflict across your datasets, nine per page. Use Find memory to filter by topic or dataset, and Refresh to reload. Open a card to see the competing facts. Each fact lists its sources (document name and effective date, when known).1
Optionally say why
Type a Reason (optional) of up to 2,000 characters under the facts. It is saved with your decision and shown in Solved.
2
Pick the fact memory should use
Click Keep next to the fact that is right. It reads Saving… while the decision is written.
- The fact you kept becomes the current one, and recall answers with it. The other facts are marked superseded. They stay in the graph as evidence but are left out of search context.
- Later automatic reviews keep your choice as long as the chosen fact exists. The choice is withdrawn if that fact disappears, for example when its source document is deleted, forgotten, or removed by a connector sync. Choosing a different fact later replaces the earlier decision.
- You need write access to the dataset to resolve a conflict.
A conflict can’t be deleted or dismissed: Keep is the only way to close it, and the facts you didn’t keep stay as superseded evidence. To remove a wrong value from memory entirely, delete the document it came from on Datasets.
Memory gaps
A gap is a topic that memory answers badly: its questions scored below 4 out of 5 in the latest completed Memory Coverage analysis of a dataset. Questions that match no topic count as the Other topic. The tab has two parts:- Memory gaps (left): one card per gap, with its dataset and a Gap (below 2.0) or Partial (2.0 to 3.9) badge. An open card shows the score and how many questions were measured, for example Coverage 2.4/5 · 6 of 8 questions measured. Use Find a gap to filter by topic or dataset.
- Coverage by dataset (right): the coverage analysis the gaps come from, with Add memory and Run analysis. It loads four datasets at a time. Use Load more datasets to see the rest; gap counts cover only the datasets loaded so far.
1
See which questions failed
Click Inspect questions on the gap card. The coverage panel switches to that dataset and topic.
2
Add the missing knowledge
Click Add memory to upload documents on Datasets, or Add integration to connect a tool that has the answer on Integrations.
3
Measure again
Click Run analysis. The gap disappears once the topic scores 4 or more.
Upcoming events
Upcoming events shows memories that carry a date or a period, taken from your datasets, on a two-week calendar that starts on a Monday. Dates are in UTC, and a period appears on every day it covers. Use Previous two weeks and Next two weeks to move, Find dated memory to filter by topic, dataset or status, and Refresh to reload. Each day shows two events, with the rest behind See N more. Each event has a status: Past, Today, Ongoing or Upcoming. Hover over or click an event to see its dates, how far away they are, and its dataset. This tab is read-only.Session learning
The overview marks session learning (lessons your agents learn in their sessions, ready to share with your team) as Coming soon. For now, the tab holds Document sharing. It lets you share a whole document you own with another dataset in the workspace. You need authority on both datasets, and another manager has to approve:- Choose the Source memory, the Destination memory, and the Document to copy.
- Click Request document sharing.
- Another workspace manager enters a Decision reason and clicks Approve copy or Deny. You can’t decide your own request, and neither can the owner of the agent that made it.
Session learning suggestions are rolling out. Until then, nothing in this tab counts toward the review’s waiting items or brain health.
Solved
Solved, headed What is settled, lists every saved conflict decision, newest first, including those settled by automatic review. Its columns are Accepted fact (with your reason, if you gave one), Dataset, Decision (User choice or Automatic review), and Solved (the date). Use Find a solved item to filter by topic or dataset.Resolve conflicts from an agent or the API
Agents can work through the same review:- Copy prompt to resolve all gives an agent with Cognee access the full list of conflicts and gaps in one paste.
- The conflicts API is the same one the UI uses. Call
GET /api/v1/conflicts?dataset_id=<id>(optionally withstatus=resolvedorstatus=unresolved) to list a dataset’s conflicts with their fact ids, sources and earlier decisions. Then callPOST /api/v1/conflicts/{conflict_id}/resolvewithdataset_id,selected_fact_idand an optionalreason(camelCase keys also work). Authenticate with your API key as described in HTTP API. - In the Python SDK,
cognee.list_conflicts()andcognee.resolve_conflict()do the same, and run against your Cloud workspace aftercognee.serve(). See Resolve Conflicting Facts and the conflicts reference.