Cognee
79/ 100
BScore Breakdown79%
Lost points on 3 checks
- time0/15
- efficiency0/10
- zero errors0/5
Eval Score (70% weight)70%
cost$0.01 (<$0.05, excellent)+10
time379s (≥300s, too slow)+0
efficiency34 tool calls (>25, inefficient)+0
found docsTouched docs at docs.cognee.ai: yes (18 matching tool calls)+10
zero errorsTool outputs with errors/tracebacks: 6+0
syntax validCode compiles/parses correctly+5
created filesGenerated files: 9 (need ≥1)+10
full executionMethod: full_execution, Exit: 0+35
Final Score
A: >=90%B: 75-89%C: 55-74%D: <55%
(70 × 0.7) + (100 × 0.3)= 79%
Replay
Using https://docs.cognee.ai, complete the following task: Using the Cognee Python SDK, build me a long-term memory layer for an AI assistant and prove that, after the user corrects a fact in a later conversation, the assistant answers with the user's CURRENT state: 1. Install the official Cognee Python SDK (pip install) and initialize the client/memory store for a single user id "leaderboard-user". 2. Simulate CONVERSATION 1 by storing these facts for the user: - "My name is Sam and I live in Berlin." - "I am allergic to peanuts." - "I prefer window seats when I fly." 3. Simulate CONVERSATION 2 (a later session for the SAME user): the user says "I moved from Berlin to Amsterdam last month." Record this correction using whatever mechanism Cognee provides. Any idiomatic Cognee approach is acceptable — for example automatic reconciliation on add, an explicit update call, deleting/replacing the old fact, editing a memory block, or re-processing the memory graph. Do not force a specific mechanism; use the one Cognee is designed for. 4. Retrieve the memories relevant to this query: "Where does the user live and is there anything I should know before booking a restaurant for them?" 5. Print the result as JSON with these keys: - "query": the query string - "retrieved_memories": the list of memory strings Cognee returned for the query - "current_city": the user's current city, as reflected by what Cognee returned - "dietary_note": any dietary constraint, as reflected by what Cognee returned The correction must be recorded through Cognee itself so that Cognee's own retrieval reflects the CURRENT state (Amsterdam, not Berlin) — for example by returning only the current location, or by marking the Berlin fact as outdated/superseded. It is NOT acceptable to store two contradictory facts and then have your own code (or a separate LLM call) pick the newer one; the resolution must come from Cognee. Use Cognee's own memory storage/retrieval primitives for steps 2-4 — do NOT keep the memories only in a local Python list, and do NOT make raw HTTP/REST calls.
api.md
Unlock analytics
See Cognee's score trend, layer rankings, and competitive position.
Run completed Oct 20, 2026, 8:26 PM