Retrieves the right ACME troubleshooting history for the follow-up reply and avoids restarting from basic password, cache, or browser troubleshooting.
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: Client Relationship Memory · text · group: memory-for-ai-agents
Input — what we sent
The exact prompt
Session 1: Use this under account_id: client_acme_001 ACME is a client using our AI support assistant. They prefer clear next steps and do not like repeated troubleshooting. Their team already tried password reset, clearing browser cache, and switching browsers. The issue is still happening only for users with SSO enabled. Session 2: Use this under account_id: client_acme_001 ACME came back today and said: "Our users still cannot log in with SSO. What should we try next?" Draft a support reply that respects what they already tried and moves to the next useful step. Session 3: Use this under account_id: client_acme_001 Update the client memory: ACME is no longer using SSO for this rollout. They moved to email-password login for the first launch. Do not keep treating SSO as the active issue unless they mention it again. Session 4: Use this under account_id: client_acme_001 ACME says: "Some users are still unable to log in during launch testing." Draft the next support reply. Session 5: Use this under account_id: client_beta_002 BetaCorp is a new client. They say: "Our users cannot log in for the first time." Draft the first support reply for BetaCorp.
A client-support memory test that checks whether the assistant remembers prior troubleshooting, handles a changed rollout context, keeps client scope isolated, and avoids leaking one client’s history into another client’s support reply.
Why this input is hard
- · client history recall
- · avoid repeating troubleshooting
- · update handling
- · scope isolation between clients
- · support response continuity
Output — unretouched
Also checked on this input — same tool, 4 other criteria
Correct Application✗ FailedKeeps applying old ACME SSO context after the rollout changed, so the later reply still falls back to SSO troubleshooting instead of the new email-password path.Memory Capture Quality✓ WorkedStores detailed client-support history as memory cards, including the ACME issue state and the already-tried troubleshooting steps.Scope Control✓ WorkedKeeps client scope separated so BetaCorp does not inherit ACME's prior troubleshooting history or SSO context.Update and Correction Handling◐ MixedAccepts the ACME correction and stores the rollout change, but does not retire the older SSO memory strongly enough to stop later reuse.
Provenance
- Observation
- 4d5d448d-d24f-4dc0-be2e-d4ee053643db
- 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: "mem0",
scenario: "memory-for-ai-agents"
})MCP · mcp.aidemos.com/api/mcp
Free with attribution.
Same input, same check — 2 other tools
measured on Relevant Retrieval
Supermemory✗ FailedIn the next support turn, the reply panel showed 'No memories retrieved yet,' so the assistant did not surface ACME's prior troubleshooting history and instead repeated a cache-clearing step that had already been tried.Zep✓ WorkedOn the follow-up, it retrieved the right ACME history and skipped the three already-tried basics, moving straight to higher-value SSO/IdP troubleshooting.
This evidence is published in
Real inputs and real outputs, no retouching · every cell queryable via API & MCP · aidemos.com