Evidence · first-party tested/Best AI Tools for Memory for AI Agents

On a later task, it retrieved the earlier work-style and memory-testing context for the internal update instead of falling back to unrelated conversation history.

✓ Worked🧾 artifact-verifiedinput + output shownTest date not recordedHindsight →
What was measured
Relevant Retrieval

Checks whether the tool retrieves the right memory for the current task.

decisive for this rankingtransformation

The main value of memory is surfacing the right context when needed, so retrieval quality directly determines usefulness. (3 of 3 judges)

What was given, what came back

Test input: Personal Work Brain Memory · text · group: memory-for-ai-agents
Input — what we sent
The exact prompt
Session 1:
Use this under user_id: founder_001

I run a small AI product/research team. When you help me, remember how I work:
- Keep outputs short, direct, and copy-paste ready.
- Do not make writing sound too polished or motivational.
- Always mention what proof or artifact is needed before making a strong claim.
- If a task is risky or unclear, tell me the safest next step instead of guessing.

Session 2:
Use this under user_id: founder_001

Today I am testing tools for an AI memory use case. I want to show users that memory is not just "remember my favorite color." It should help an assistant continue real work across days, remember my working style, and avoid repeating the same explanation again.

Create a short internal update for my team about what I worked on today and what we should test next.

Session 3:
Use this under user_id: founder_001

Now write a formal email to a potential enterprise partner asking if they are open to a product demo next week. Keep it professional.

A multi-session personal assistant memory test where the user first sets working-style preferences, then asks for an internal update, and finally requests a formal partner email to check whether the assistant applies memory selectively and appropriately across different writing tasks.

Why this input is hard
  • · work-style preference memory
  • · cross-session retrieval
  • · tone adaptation by task
  • · proof-first behavior
  • · avoiding overgeneralization of memory
Output — unretouched
image
Provenance
Observation
c42eea97-46ba-43ef-b287-93886b03407c
Evidence run
6e31afbb-34d7-459a-b688-68ef76fc615a
Study
Memory for AI Agents
Research task
86ba16xrp
Tested at
not recorded
Source
first-party
Evidence state
verified
Proof shown
input + output shown
Cost / latency
not captured
Repeat run
not captured
Tester
not captured

The last three rows are honest blanks, not placeholders — our capture has no field for them yet.

Query this
get_evidence({
  tool: "hindsight",
  scenario: "memory-for-ai-agents"
})
MCP · mcp.aidemos.com/api/mcp
JSON · ai.aidemos.com/v1/observations/c42eea97-46ba-43ef-b287-93886b03407c
Free with attribution.
Same input, same check — 4 other tools
measured on Relevant Retrieval
Cognee✓ WorkedRecalls prior working-style memory in later sessions through GRAPH_COMPLETION, exposing evidence chunks plus dataset and document/chunk IDs rather than a simple memory-hit flag.Mem0✓ WorkedRetrieves the previously stored work-style memory in a later session so the assistant can reuse it for a follow-up internal update.Supermemory✓ WorkedLater turns could draw on the stored working preferences without the user restating them, showing that prior context remained available across sessions and influenced follow-up responses.Zep✓ WorkedRetrieved the saved founder work style in a later task and produced a short internal update without requiring the user to restate the preference block.
This evidence is published in
Best AI Tools for Memory for AI Agents →
Real inputs and real outputs, no retouching · every cell queryable via API & MCP · aidemos.com