DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to find which items a new assistant version fixed or broke with Keystone Bench

Compare two saved runs item by item to see exactly what changed between versions.

  • Research
  • Intermediate
  • 1 hour
  • From the README
  • Any agent

Credentials. Each run calls a model endpoint, so the API key must be set in the environment before the runs start.

Who it is forA team shipping updates to a medical chat assistant that needs to know whether a new version got worse on specific decisive-fact cases.

The problemA single aggregate score can hide that a new version fixed some missing-evidence cases while breaking others.

The outcomeA list of items that changed verdict between the two runs, so the team can review the regressions directly.

What you need first

  • Python with pip to install keystone-bench from PyPI
  • An API key for an OpenAI-compatible endpoint, such as OpenRouter, to run models and a judge from a different vendor
  • Network access so that keystone build can fetch HealthBench from OpenAI's public copy and the label files
  • Enough disk space and time for the local rebuild of the twins, since the release ships span references rather than benchmark prose

Steps

  1. pip install keystone-bench
  2. keystone build
  3. keystone run --family all --layer quick --model openrouter/openai/gpt-5.6-terra --judge openrouter/anthropic/claude-sonnet-5
  4. Rerun the same command for the new version with a different output folder, so you have two run folders to compare (inferred, check the README)
  5. keystone regress runs/v1 runs/v2

Prompt for your agent

In the keystone-bench repo, compare two saved runs with keystone regress runs/<old> runs/<new>. Report the items that regressed and the items that were fixed, and confirm both runs used the same quick layer.

Caveat. Both runs must use the same release and layer for the comparison to be meaningful, and the regression check only covers the twins in those runs.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page