# Run Terminal-Bench and other Harbor evals on Vercel Sandbox

Source: [Vercel](https://vercel.com/changelog/run-terminal-bench-and-other-harbor-evals-on-vercel-sandbox)  
Feed7 permalink: https://feed7.dev/p/run-terminal-bench-and-other-harbor-evals-on-vercel-sand-82b0afd7a5  
Published: 2026-09-17T00:00:00.000Z  
Trust: Official Source (official_source)

## Why Included

Harbor can run repeatable agent benchmarks in isolated microVMs, parallelizing model comparisons while keeping secrets outside each sandbox.

## Source Summary

Harbor can run Terminal-Bench and related evals in isolated Vercel microVMs, enabling parallel model comparisons without putting injected credentials inside each sandbox.

## Practical Implication

Move repeatable agent evaluations off a constrained local machine, parallelize trials, and swap the gateway `--model` value to compare providers while keeping the benchmark command stable.

## Agent-Ready Context

**Harbor 0.22.0 or later** can run Terminal-Bench, SWE-bench, tau3-bench, OSWorld, and other registry evals on Vercel Sandbox with `--env vercel`. Each trial gets an isolated **Firecracker microVM**.

Move repeatable agent evaluations off a constrained local machine, parallelize trials, and swap the gateway `--model` value to compare providers while keeping the benchmark command stable.

Network policy is enforced outside the VM, and optional secrets are attached only to matching outbound requests. The material does not quantify cost, startup overhead, concurrency limits, or result reproducibility.

## Context Map

- Layer: benchmark
- Domains: coding, security
- Topics: agent-evals, sandboxing, gateways

## Uncertainty

- None recorded.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.