Skip to content

Add Benchmarks & evals use case (Terminal-Bench via Harbor on E2B) - #321

Open
tomasvarga wants to merge 2 commits into
e2b-dev:mainfrom
tomasvarga:use-case-benchmarks
Open

Add Benchmarks & evals use case (Terminal-Bench via Harbor on E2B)#321
tomasvarga wants to merge 2 commits into
e2b-dev:mainfrom
tomasvarga:use-case-benchmarks

Conversation

@tomasvarga

Copy link
Copy Markdown
Contributor

What

Adds a new Use cases → Benchmarks & evals page (docs/use-cases/benchmarks.mdx) plus its nav entry in docs.json.

The page covers running coding-agent benchmarks on E2B via Harbor (the Terminal-Bench harness, which ships an E2B environment backend): why per-task sandbox isolation matters for eval integrity, a verified quickstart running the Terminal-Bench 2 sample set with Claude Code, and pointers to scaling up (full TB2, other registry datasets, --skill for with/without-skill comparisons, and e2b-dev/swe-bench).

Verified

All commands were run end-to-end on 2026-07-29 with harbor 0.20.0:

  • pip install 'harbor[e2b]'harbor run -d terminal-bench-sample@2.0 -a claude-code -m claude-sonnet-5 -e e2b -n 3
  • 3 trials, 0 exceptions, mean 0.667, 3m30s total — the output block in the page is verbatim from that run
  • Trajectories, verifier output, and rewards all collected back to the host by the harness

Known limitation (documented in a Note callout)

Harbor currently hardcodes a 24h sandbox timeout at creation (harbor/environments/e2b.py), which fails with 400: Timeout cannot be greater than 1 hours on plans with a 1h sandbox lifetime cap. The page documents this; a Harbor upstream fix to make it configurable is a sensible follow-up.

@cla-bot cla-bot Bot added the cla-signed label Jul 29, 2026
- Quickstart is now tabbed: Terminal-Bench (registry dataset) and ReactBench
  (local task dirs from a cloned repo), both verified end-to-end on E2B
- ReactBench tab explains --allow-agent-host (offline tasks + per-phase
  network policy) and --override-memory-mb (build-time resource limits),
  with a Warning documenting the two temporary Dockerfile edits
- New 'Bring your own eval' section: harbor init scaffold, task layout,
  SWE-bench-style fail-to-pass/pass-to-pass testing, and eval validation
  with oracle/nop control runs before spending on agents
- All commands and output blocks are verbatim from verified runs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant