Agents don’t do the same thing twice. Run one task five times and it may pass three. CheckAgain shows which tasks you can count on, and whether a change really changed anything.
CheckAgain reads the dots. The paths are here to show why they differ. Click an agent to watch it again.
Start from what you already do after a change. Nothing to install, no account.
Already have automated tests? Run them five times and drop the reports in the box.
Too many to run by hand? Let your coding assistant do it
I want to check whether my AI agent’s results hold up when run again, using CheckAgain (checkagain.cruciblescience.com). Please: 1. Find the cases I already test (an eval set or tests in this project), or ask me for the 10 to 20 cases I try by hand after a change. 2. Write a small script in this project that runs each case 5 times through my agent, the way my code already calls it, and decides pass or fail with the check I already use. If there isn’t one, agree a plain rule with me first; don’t use a model as the judge unless I ask. 3. Take a setup label from a flag (--setup before / --setup after) and append one row per run to results.csv with the columns task, setup, run, passed, ended, cost_usd (ended: completed, timeout or error; cost only if my client records it). 4. Before running anything, tell me how many agent calls it will make and roughly what that costs, and wait for my yes. Put only task names and outcomes in the file: never prompts, outputs, conversation text, customer data or keys. Don’t upload anything; I’ll drop the file into CheckAgain myself.
Turn my existing agent results into a CSV for CheckAgain (checkagain.cruciblescience.com). The results are in: [where your results are]. Write one row per run with the columns task, setup, run, passed (pass or fail), and, if the data has them, ended (completed if the run stopped by itself, otherwise what stopped it) and cost_usd (as recorded, never estimated). Keep each task’s name the same across runs, number repeats 1, 2, 3…, and use the model or version as the setup. Copy results exactly as recorded: don’t invent, fix or drop runs. Put only labels and outcomes in the file: never prompts, outputs, conversation text, customer data or keys. Save it as results.csv and tell me where it is.
Or install the CheckAgain skill, with the same rules and a checker that confirms the file is ready: download it (4 KB). For Claude Code, unzip into ~/.claude/skills/.
Paste your results here, or drop files on this box
Reads spreadsheets, CSV and JSON files, test reports from your CI, and exports from common eval tools. To compare a change, add the results from before and after.
● Your files stay in your browser. Nothing is uploaded.
Choosing a folder? Your browser may call it an “upload”: that’s its standard wording. The files are read here and nothing is sent. Dragging the folder onto the box skips the question.
A real readingReading the example…Back to the example
Data: Terminal-Bench 2.0 public runs, Apache 2.0.
Free for the first five agents. We read your agent’s runs before and after a change, and tell you what moved, what it costs and what to check next.