leetcrypt
df45303f5c
Add bench/ — a 4-category × easy/medium/hard task matrix (shell, code, git, multi) and a runner that drives the live TUI over tmux and grades each task by a `podman exec` verify snippet (exit 0 == PASS), never by the model's self-reported summary (which the weak CPU model fabricates). Tasks run in the agent's real cwd with bare filenames so the suite measures task completion, not the model's absolute-path discipline. Completion is detected off the viewport- independent `is thinking…` footer (the TUI is full-screen, so capture-pane scrollback is not chat history). First baseline (qwen2.5:3b): 2/12 PASS, high variance. Surfaces the next harness-addressable improvements — `<native>` tag leakage and bare tool-call-as-text — now measurable against this suite. Findings doc updated. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
69 lines
2.9 KiB
Markdown
69 lines
2.9 KiB
Markdown
# Native-harness benchmark
|
||
|
||
A small, ground-truth-graded benchmark for the `/ai <model> !<task>` native
|
||
tool-calling loop (`cmd_chat/agent/bridge.py:_run_native`). Use it to compare
|
||
harness changes (and models) **systematically** instead of eyeballing one-off
|
||
runs.
|
||
|
||
## Why ground truth
|
||
|
||
The weak CPU model routinely *claims* success it didn't achieve ("written, made
|
||
executable, and run successfully" after a 126; "created notes.txt" while the
|
||
file actually contains `echo 'hello'`). So every task is graded by a POSIX-sh
|
||
`verify` snippet run **inside the sandbox** via `podman exec`, exit 0 == PASS —
|
||
never by the model's own summary. See
|
||
`docs/findings-native-harness-2026-06-10.md`.
|
||
|
||
Tasks run in the agent's real cwd (the container HOME, `/root`) with **bare
|
||
filenames** — pinning an absolute `/root/bench/...` path instead just measures
|
||
whether the weak model honours absolute paths (it ~never does for `run_shell`
|
||
redirects) and drowns out every other signal. Only the suite's known artifacts
|
||
are wiped between tasks; the home dir itself is never `rm -rf`d.
|
||
|
||
## The matrix
|
||
|
||
Four categories × easy / medium / hard (`bench/tasks.py`):
|
||
|
||
| category | tools exercised | easy → hard |
|
||
|---|---|---|
|
||
| `shell` | run_shell | whoami→file · nested mkdir · count `/etc/*.conf` |
|
||
| `code` | write_file + run_shell | py `2+3` · **chmod +x script** · 10× Fibonacci |
|
||
| `git` | run_shell + network | clone · clone+read README · clone+report branch |
|
||
| `multi` | chained steps / recovery | mkdir→write→list · reverse-sort · word-count script |
|
||
|
||
`code-medium` (write → `chmod +x` → `./run`) and `multi-easy` are the
|
||
historically hardest cases — they're the nudge loop's main targets, so they
|
||
double as regression canaries.
|
||
|
||
## Prerequisites
|
||
|
||
Same setup as a manual live test:
|
||
|
||
1. Server + Rust client running in a tmux window (default `hh-house:2`).
|
||
2. An agent online with drive: `/ai start <model>` then `/grant ai`.
|
||
3. The sandbox container running (default `hack-house`) with `python3`, `git`,
|
||
and outbound network (the `git` tier needs it).
|
||
|
||
The runner only *sends* tasks and *reads* state — it never starts/stops the
|
||
agent, so a failure leaves your session intact.
|
||
|
||
## Running
|
||
|
||
```bash
|
||
.venv/bin/python bench/run.py --model qwen2.5:3b # full suite
|
||
.venv/bin/python bench/run.py --tier easy # one tier
|
||
.venv/bin/python bench/run.py --no-net # skip git/network tasks
|
||
.venv/bin/python bench/run.py --only code-medium,multi-easy
|
||
.venv/bin/python bench/run.py --dry-run # print the matrix, run nothing
|
||
```
|
||
|
||
Useful flags: `--container`, `--target` (tmux window), `--user` (for @mention
|
||
detection), `--timeout` (per-task wallclock cap, default 300 s).
|
||
|
||
## Output
|
||
|
||
A PASS/FAIL table with per-task latency, plus a JSON record under
|
||
`bench/results/` (gitignored — these are runtime artifacts). Commit a curated
|
||
baseline explicitly (e.g. `--out bench/results/baseline-<model>.json` then
|
||
`git add -f`) when you want one tracked for comparison.
|