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

How to test whether an agent change helps, task by task with Crux

Compare two agent versions on the same tasks with a paired sign test instead of one total score.

Who it is forAn engineer changing the agent layer of a pi-based coding agent who needs to know whether an edit is a real improvement or noise.

The problemA single pass rate can move by chance, so an edit can look like a gain or a loss without being one.

The outcomeA task-by-task comparison of two agent versions with a paired sign test that shows which changes are meaningful.

What you need first

  • uv installed, since the benchmark is set up with `uv sync`
  • harbor installed, since the benchmark runs through `harbor run`
  • Access to the terminal-bench/terminal-bench-2-1 dataset
  • A model endpoint you can reach through the `openai/` model prefix used in the README command

Steps

  1. Clone the repository and open the benchmark folder with cd benchmark.
  2. Install the harness dependencies with uv sync.
  3. Run the baseline version and the changed version with harbor run --dataset terminal-bench/terminal-bench-2-1 --agent crux.pi_agent:CruxPiAgent --model openai/<your-model>, keeping the model and dataset the same. (inferred, check the README)
  4. Use the harness comparison step in the benchmark folder to compare the two runs task by task with the paired sign test. (inferred, check the README)

Prompt for your agent

Use the alanhuangyoo/crux repository benchmark folder. Run the same Terminal-Bench 2.1 dataset and model for two agent versions, <baseline> and <changed>, then compare them task by task with the paired sign test. Output the per-task outcome counts and the test result, and verify that both runs used the same model and task set.

Caveat. The README describes the paired sign test but does not show the exact command for it, so check the benchmark folder for how to invoke the comparison.

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