Product benchmarks

Measure the effectof context.

LoCoMo measures factual recall across long conversations. LoCoMo Plus tests whether implicit constraints are remembered and applied. SWE-bench Pro measures whether project context helps Codex resolve more repository issues.

LoCoMo accuracy and search latency1,540 scored questions
SystemAccuracySearch p95
PowerContext90.78%1.38 s
PowerMem87.79%1.44 s
Full context52.9%17.12 s

LoCoMo: retrieve the right context

LoCoMo asks questions about long conversations split across sessions. PowerContext must find the relevant conversation evidence before producing an answer. This run covers 1,540 scored questions in categories 1 through 4.

Question mix1,540 total
Single-hop841
Temporal321
Multi-hop282
Open-domain96
PowerContext resultCategories 1 through 4

90.78% answer accuracy

PowerContext answered 1,398 of 1,540 questions correctly, 37.88 percentage points above full-context prompting. Search p95 was 1.38 seconds, with about 1.65k answer tokens per question.

LoCoMo Plus: apply implicit memory constraints

Even when a new question does not resemble an earlier cue, the system must retain and apply the user's state, goals, values, and causal background. These results compare native PowerContext with Jev candidate filtering across three models.

Each model is used for both Memory extraction and answer generation. Jev filters candidates after retrieval; it does not replace either model role.

Embedding model
qwen3.7-text-embedding
1024 dimensions

These six scores were supplied by the project owner. The corresponding run manifests, summaries, protocol and model/Judge configurations, run hashes and raw outputs are not publicly available for verification. Reproducibility documentation describes the harness, not verification of these scores.

Highest reported score

69.28%

GPT-4o · PowerContext + Jev

Largest score difference

+8.925

GPT-4o-mini · percentage points

Project-owner-supplied scores, with and without Jev
Extraction & answer modelNative PowerContextPowerContext + JevDifference
GPT-4o-mini40.855%49.78%+8.925percentage points
Qwen3.7-plus60.37%68.947%+8.577percentage points
GPT-4o65.082%69.28%+4.198percentage points

SWE-bench Pro: turn context into working patches

To measure the effect of PowerContext, we ran the same Codex configuration twice on all 731 public v2 tasks. The two arms differed only in whether PowerContext was enabled.

SWE-bench Pro paired runsPassing the benchmark tests counts as resolved
PowerContext OFF602 / 731 · 82.35%
PowerContext ON634 / 731 · 86.73%
+4.38 pp · 32 more tasks

This is a paired run on a pinned task set, not an official SWE-bench Pro submission. Agent runs are stochastic, so the scores describe these two runs only.

Comparison with published results

Explore published LoCoMo and LoCoMo Plus results alongside the official SWE-bench Pro Public leaderboard. Each entry links to its evaluation configuration and source.

LoCoMo / SWE-bench Pro checked August 31, 2026

15 systems · All 1,540 scored questions

  1. 1ZepVendor run94.70%
  2. 2EverMemOSThird-party run94.50%
  3. 3XMDBVendor run93.20%
  4. 4TrueMemory ProOpen harness93.00%
  5. 5Mem0Vendor run92.50%
  6. 6PowerContextProject run90.78%
  7. 7HonchoVendor run89.90%
  8. 8DakeraReproducible vendor run88.20%
  9. 9PowerMemProject run87.79%
  10. 10MemvidOpen harness85.65%
  11. 11GenesysCertified vendor run85.55%
  12. 12EngramThird-party run84.50%
  13. 13MemHQOpen harness83.20%
  14. 14Logica MindOpen harness72.50%
  15. 15SupermemoryThird-party run65.40%

Readers, judges, and answer-matching rules differ, so this is not an official ranking.

Evaluation methods and sources

Method references and evaluation tools for all three benchmarks. Read models, scoring rules, and data scope together.

LoCoMo

LoCoMo Plus

Pinned data and official evaluatorxjtuleeyf/Locomo-Plus · 059f4e3
PowerContext harness and scoring notesbenchmark/locomo_plus · 87fceeb7

SWE-bench Pro

Use PowerContext in your workflow

Start with a supported agent or connect an application through the HTTP API. The repository contains the runtime, integrations, and evaluation tools.

Open the GitHub repository