Directus Filtered Reads
Two coding tasks that read role-scoped content through the Directus Items API, whose underscore-operator filters, nested relational conditions, and deep parameter semantics differ from the querystring patterns models default to.
Use this board to compare tested agent configurations on this exact task suite. It measures task execution against a hidden mock contract, not general model quality or production reliability.
How to read this benchmark
Each task is graded by a hidden mock server implementing Directus current Items API contract (filter grammar, deep parameters, field expansion, role-scoped permissions) with the real error envelopes. Pass means the agent client executes correctly against the mock, never a model judging its own work. Every task is calibrated three ways before it is admitted: an empty solution fails, a current-contract reference passes, and the stale-memory solution fails on the intended trap.
- Last run
- Held-out tasks
- 2
- Configurations
- 8 agent configurations
- Chart metric
- Pass rate on a 0–100% scale
An agent profile is the exact instruction and tool configuration used for a run. A harness is the coding tool that gives a model its agent loop and tools; “direct” is a model call without that coding harness. On coding boards, “default reviewer” means the run used VerticalBench’s standard between-attempt review, while “no reviewer” means the coding harness ran once without that review. Hover a chart label to see its immutable profile ID. 95% Wilson interval for observed pass/fail outcomes; each configuration shows its own sample size. Small suites are narrow capability checks, not evidence that one model is generally better.
Read the broader agent-evaluation methodology →Per-task breakdown
2 held-out tasks · prompts private| Task | Claude Sonnet via Claude Code Default reviewer | Claude Sonnet via Claude Code No reviewer | GLM-5.2 via OpenCode Default reviewer | GLM-5.2 via OpenCode No reviewer | GLM-5.1 via OpenCode Default reviewer | GLM-5.1 via OpenCode No reviewer | GPT-5 mini via pi Default reviewer | GPT-5 mini via pi No reviewer |
|---|---|---|---|---|---|---|---|---|
| 01 | 100 n=1 14415 tok · 217.7s | 100 n=1 9993 tok · 160.3s | 100 n=1 634834 tok · 155.7s | 100 n=1 434285 tok · 145.2s | 100 n=1 473768 tok · 235.5s | 100 n=1 317973 tok · 131.1s | 100 n=1 13809 tok · 171.8s | 0 n=1 16866 tok · 166.4s |
| 02 | 100 n=1 14401 tok · 220.7s | 100 n=1 25191 tok · 365.1s | 100 n=1 487742 tok · 200.6s | 100 n=1 794044 tok · 281.6s | 100 n=1 1036008 tok · 277.8s | 100 n=1 646721 tok · 239.4s | not run | 0 n=1 16896 tok · 179.8s |
Each cell shows pass rate, total input-plus-output tokens, and mean wall time for that task and agent profile. Cost was not captured for these subscription-harness runs; that does not mean the runs were free. “Not run” means the result artifact has no recorded attempt for that task and profile. Task prompts stay private so they remain held out; opaque task numbers and every measured result are published.