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

It applied the retrieved work-style memory to the internal update, but the report says the reply was slightly more structured and polished than the user's strict short, direct preference.

◐ Mixed🧾 artifact-verifiedinput + output shownTest date not recordedHindsight →
What was measured
Correct Application

Checks whether the agent actually uses the retrieved memory correctly.

decisive for this rankingtransformation

For agent memory, it is not enough to retrieve facts; the system must help the agent use them correctly in task execution. (2 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
237256dc-81fd-4381-89e5-63302db008cf
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/237256dc-81fd-4381-89e5-63302db008cf
Free with attribution.
Same input, same check — 4 other tools
measured on Correct Application
Cognee✓ WorkedApplies the stored working style to a new internal update by keeping the reply short and proof-oriented while blending in the current memory-testing project context.Mem0◐ MixedUses the retrieved style memory only partially: the internal update still reads a bit generic and polished instead of fully short, direct, and copy-paste ready.Supermemory◐ MixedThe tool applied the memory selectively: the internal update was useful but a bit more structured and polished than the requested short, direct style, while the formal partner email stayed professional and did not leak the internal terse style into a different writing task.Zep✓ WorkedApplied the remembered style selectively across two writing tasks: the internal update stayed short and practical, while the later partner email stayed professional instead of turning into an internal-note style response.
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