Benchmark · October 2026

Ruune memory on DolphinBench

DolphinBench feeds three simulated people’s histories, 13,500 messages over three years, into a memory system, then asks an assistant to complete 600 tasks that depend on remembering them. We ran it on Ruune with the benchmark’s public runner.

77.5%

465 of 600 tests passed. The best official configuration, Mem0 on Hermes, scores 70.7%.

0%25%50%75%100%Ruune (Custom (tools loop)): 77.5%Ruune77.5%Mem0 (Hermes): 70.7%Mem070.7%Hindsight (Hermes): 69.5%Hindsight69.5%Honcho (Hermes): 68.5%Honcho68.5%Built-in (Hermes): 65.7%Built-in65.7%Supermemory (Hermes): 59.2%Supermemory59.2%
Tests passed, out of 600. Official rows: the Hermes harness with gpt-5.6-luna, the paper’s strongest family.
Memory build
$230
13,539 messages compiled
600 test runs
$2.06
agent calls and query embeddings
Median task
36 s
p95 86 s
Alex
152/200
5,011 messages in history
Morgan
152/200
3,400 messages in history
Riley
161/200
5,128 messages in history

What passing looks like

Six of the 465, chosen for how far back the fact sits and how little the question gives away. Quotes are from the evidence files; the people are DolphinBench’s simulated personas.

  1. Morgan, startup founder · asked September 14, 2026

    “Text Jamie with the booking rule we agreed on during the flight home from Tokyo, applied to the refundable cabin for December 27 through January 2.”

    Ruune remembered

    “On the flight home we said the obvious thing out loud: protected dates only work if we name them and then treat them as actual commitments.”

    March 12, 2024. 2½ years earlier, in a notes-app entry titled “Tokyo flight home notes”. The words “booking rule” never appear.

    The assistant did

    Texted Jamie: “For Dec 27–Jan 2, let’s apply our flight-home rule to the refundable cabin: treat those dates as real, protected commitments and route work/coverage around them—not as soft placeholders. If we can’t genuinely protect the dates, we shouldn’t book it.”

    Judged against

    Supports protecting the named dates and arranging ordinary work or coverage around them. Making the dates contingent on normal workload fails.

    4 searches, then read the full note · test morgan/075

  2. Riley, growth lead · asked January 1, 2028

    “Create a private note that says which Marcus “Friday Marcus call” means and distinguishes him from the Marcus in my work context.”

    Ruune remembered

    “Friday Marcus call in a sec -- brother Marcus Tanaka, not Marcus Vail lol.”

    February 17, 2023. Nearly five years earlier, one offhand remark. Later entries only ever say “Marcus”.

    The assistant did

    Wrote the note: “‘Friday Marcus call’ means Marcus Tanaka, my brother—not Marcus Vail, my work colleague.”

    Judged against

    Names both identities and their relationship to the user, and nothing else.

    1 search, then the person page for Marcus Tanaka · test riley/069

  3. Morgan, startup founder · asked September 14, 2026

    “Email Devon why we passed on Drift Capital after evaluating its terms.”

    Ruune remembered

    “wrote the Drift Capital thing down so i stop re-litigating it. four discovery calls was enough. passed. board observer language was too grabby, the IP carve-out stuff got weird, and i really don’t want a tranche tied to MAU.”

    March 1, 2023. 3½ years earlier. Drift Capital is mentioned nowhere else.

    The assistant did

    Emailed Devon: after four discovery calls and a review of the terms, the board observer language felt too intrusive, the IP carve-out terms raised concerns, and a tranche tied to MAU wasn’t acceptable.

    Judged against

    Describes an evaluated-and-passed decision based on overreaching board-observer language, problematic IP carve-outs, and an MAU-linked tranche.

    6 searches across mail, recordings and documents · test morgan/118

  4. Morgan, startup founder · asked September 14, 2026

    “Elena Volkov’s CRM record was recreated with only her name. Restore my last recorded follow-up status and the reason for it.”

    Ruune remembered

    “Elena Volkov sent the no from the VC firm. passed on the round, but not boilerplate at all … her main push was the retention funnel.”

    February 20, 2023. Her original pass.

    “Elena Volkov is first because she is warm context and gave the useful retention feedback earlier.”

    September 28, 2023. A voice memo seven months later.

    “I’ll reconnect in January if the package is cleaner.”

    December 12, 2023. The last recorded plan, in an email draft request.

    The assistant did

    Set the record to “warm later” with the reason: she passed over the retention funnel but her feedback was thoughtful; keep warm, reconnect when the package can address uneven expansion.

    Judged against

    Keeps a warm/later follow-up, not an active process. Explains that her pass questioned the retention-funnel shape. Does not invent a new investment commitment.

    12 calls: searches, the person page, a timeline of late 2023, and three full sources read end to end · test morgan/104

  5. Riley, growth lead · asked January 1, 2028

    “Privately thank the two teammates I credited in my old team note about the pricing-page rollback. Send each a separate, concise Slack DM acknowledging their specific contribution.”

    Ruune remembered

    “put the team note in Slack … gave Owen the nod for the cut and Ines for catching the email QA stuff before it turned into a mess.”

    March 22, 2023. Nearly five years earlier. The ask names neither person.

    The assistant did

    Two DMs. Owen: thanks for pulling the cohort cut for the pricing-page rollback. Ines: thank you for catching the email QA issues early and keeping them from turning into a bigger mess.

    Judged against

    Six checks: both DMs sent, to the right two people, each crediting that person’s specific contribution, without a broad experiment recap.

    6 searches and two full reads of the rollback thread · test riley/157

  6. Morgan, startup founder · asked September 14, 2026

    “Create a short historical timeline document recording the date, time, and timezone when the lead firm formally passed on the 2023 B-round pitch.”

    Ruune remembered

    “Just got the lead firm’s formal pass email. 12:45pm on Feb 16. So yeah. B-round pitch fell through.”

    February 16, 2023. The note itself never states a timezone; the agent took it from the entry’s recorded offset.

    The assistant did

    Saved a timeline document: “February 16, 2023 — 12:45 p.m. PST (UTC−08:00): received the lead firm’s formal pass by email.”

    Judged against

    Identifies the formal pass as February 16, 2023 at 12:45 PM Pacific, or the equivalent instant, and attributes it to no other event.

    4 searches, then read the full entry · test morgan/137

Every official configuration

MemoryHarnessModelPass rateTotal costMedian latency
RuuneCustom (tools loop)GPT Luna77.5%$23236 s
Mem0Hermesgpt-5.6-luna70.7%$9638 s
HindsightHermesgpt-5.6-luna69.5%$8555 s
HonchoHermesgpt-5.6-luna68.5%$14345 s
Built-inHermesgpt-5.6-luna65.7%$6144 s
SupermemoryHermesgpt-5.6-luna59.2%$34653 s
Mem0HermesMiniMax M347.8%$14847 s
HonchoHermesMiniMax M347.3%$21280 s
HindsightHermesMiniMax M341.0%$158144 s
HonchoClaude CodeClaude Sonnet 535.8%$1,56638 s
Mem0Claude CodeClaude Sonnet 532.3%$1,83142 s
Built-inHermesMiniMax M326.5%$10751 s
Built-inClaude CodeClaude Sonnet 526.3%$1,13332 s
SupermemoryHermesMiniMax M320.0%$498138 s

Total cost is memory build plus the 600 tests. Latency is the median time per task.

How the run was made

  1. Ingestion. Each dated message went into a fresh Ruune account through the public notes API, one account per persona. Ruune’s server-side compiler then did what it does for every user: extracted the people, places, topics, commitments and dates, classified and embedded them, and built entity pages.
  2. Freeze. Once compiling finished, each account’s compiler was switched off and a hash of the vault recorded. The runner re-checks that hash before and after the tests, so the memory the tests read is exactly the memory that was built.
  3. Tests. An assistant built on GPT Luna answered the 600 tasks with the benchmark’s mock apps plus Ruune’s read-only memory_* tools over MCP, the same tools any MCP client gets. No write tools were offered.
  4. Grading. gpt-5.6-sol on Azure, medium reasoning: the judge DolphinBench fixes for every submission.

Read this before comparing

  • Self-run. DolphinBench has not validated this result. The evidence archive their validator accepts is linked at the top.
  • Different agent, different harness. The official rows answer with gpt-5.6-luna inside the Hermes agent; ours answers with a different model inside a small tool loop we wrote. The memory is the variable we care about, but the agent is not held constant.
  • Cost is mostly memory build. $230 of the $232 total is Ruune compiling 13,539 messages. The entity page build runs as a background job whose tokens are not metered; it is on top of that figure.
  • One run. Both the agent and the judge sample. Re-running the same frozen memory moves the score by about three points either way; the official rows are single runs too.

The benchmark, dataset and paper are at dolphinbench.ai.