FOR PEOPLE WHO WRITE EVALSWrite the task.
Write the task.
Judge the evidence.
A prompt, a rubric, and a real agent run.
Measure the behavior you care about. See why it passed.
bun add --exact @hona/openevalprompt.md taskjudge.md criteria0 | 1 | null decisionsask-dialectinteractive exampleNo model calls
CANDIDATE RESPONSE
“Which database are you using—PostgreSQL, MySQL, SQLite, or SQL Server?”
SELECT id, created_at, total
FROM orders
WHERE customer_id = $1
ORDER BY created_at DESC, id DESC
LIMIT 10;
Bind $1 to the customer ID with your database driver.
Judge decisions2 / 2 passed
Click a metric to locate its response evidence.
Your evals are files
| File | What you write |
|---|---|
| prompt.md | A natural, focused task |
| judge.md | Named metrics and clear criteria |
| eval.ts | Optional workspace and early stop |
Every score has a trail
- Task
- Recording
- Judgment
- Score
- Inspect tool calls and workspace artifacts
- Follow each decision to its evidence
- Rejudge without rerunning the candidate
THE RESULTS WORKSPACE
How scores work Compare. Drill down. Inspect.
Run a small batch first.
Keep the full aggregate. Execute only the evals, models, and repetitions you select.
Plan and resume workterminal
bunx --bun @hona/openeval plan --only-eval ask-dialect
bunx --bun @hona/openeval run --only-repetition 1
bunx --bun @hona/openeval view


