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

How to benchmark a self-hosted model on Terminal-Bench 2.1 with Crux

Run the Crux agent on 89 Terminal-Bench 2.1 tasks to get a pass@1 score for your own model.

Who it is forAn ML engineer who serves an open-weight coding model locally and needs a repeatable score before deciding whether to use it for agent work.

The problemAgent scores vary with the harness, so a model's raw ability is hard to compare without the same tasks and the same agent setup.

The outcomeA pass@1 score for your model running inside the Crux agent on the Terminal-Bench 2.1 task set, comparable to the README results.

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. Finish the --model argument after openai/ with the name of your served model, since the README command is cut off there. (inferred, check the README)
  4. Run harbor run --dataset terminal-bench/terminal-bench-2-1 --agent crux.pi_agent:CruxPiAgent --model openai/<your-model>. (inferred, check the README)

Prompt for your agent

Use the alanhuangyoo/crux repository. Go to its benchmark folder, run `uv sync`, then run harbor against the terminal-bench/terminal-bench-2-1 dataset with agent crux.pi_agent:CruxPiAgent and model openai/<your-model>. Report the pass@1 score over the full run and the number of tasks evaluated, and confirm the run covered 89 tasks.

Caveat. The README gives the model argument only as far as openai/, so you must supply the rest yourself and the full run covers 89 tasks, which takes a long time.

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