Docs
CommunityJev Benchmarks & Evaluations
Jev Evaluation Traces
Raw traces from retired, versioned native ToolEmu and AgentDojo runs, including failures and partial trajectories, preserved as original bytes with SHA256 manifests and upload revisions.
- Format
- Docs
- Reading time
- 2 min
- Published by
- Community
- Author
- Ayushnangia
- Last verified
- Oct 2026
- Capabilities
- Open source
Highlights
- AgentDojo runs for clef, gemma4-12b-it, jev-omni and kev-27b, each with native-report.json, predictions.jsonl, smoke.exit and status.json.
- Retired native-v1 ToolEmu and completion manifests are kept under archive-manifests/.
- Files retain their original bytes; archive manifests record SHA256, sizes, source paths and upload revisions.
- Local trace copies are removed only after remote byte verification, and active files are never archived or deleted.
Watch out
The card declares no licence and the repository metadata carries only the region:us tag. These are retired runs that include failures and partial trajectories, not a completed 23-model evaluation, and the card states AgentDojo environments are synthetic benchmark fixtures with unvalidated ToolEmu judge scores. Gated classification source text is excluded from the archive.
Questions about this entry
Short answers drawn from the linked project or page.
Full raw traces from retired, versioned native ToolEmu and AgentDojo runs, including failures and partial trajectories, published so the exact artifacts each run produced stay reviewable.
Under aurora/agentdojo-results-before-storage-link, with folders for clef, gemma4-12b-it, jev-omni and kev-27b, each holding native-report.json, predictions.jsonl, smoke.exit and status.json.
No. The card states they are not a completed 23-model evaluation and not validated ToolEmu judge scores; they are archived raw runs that include failures and partial trajectories.
The card declares no licence, and the repository metadata carries only the region:us tag, so check the underlying AgentDojo and ToolEmu terms before redistributing anything from the archive.
Files keep their original bytes and archive-manifests/ records SHA256 hashes, sizes, source paths and upload revisions; local trace copies are deleted only after remote byte verification succeeds.
The card calls them synthetic benchmark fixtures, so the traces reflect model behavior on constructed agent scenarios rather than production traffic.
Gated classification source text is excluded from this native archive by design, per the card's notes on the release.
From the Jev guides
Original write-ups on what this entry is for.
From the Jev AI model community
Posts from builders shipping with Jev right now.