Aether Evals
Aether Evals is a Rust library that makes writing agent evals easier to express as ordinary cargo-nextest tests.
Table of Contents
- Quick Start
- Test organization
- Core API
- Dockerized evals
- Assertions
- Failure output and debugging
- Git-backed evals
- Development
Quick Start
use ;
async
Run evals with nextest:
The CI profile writes JUnit XML to target/nextest/ci/junit.xml.
Test organization
Aether Evals' fake-agent coverage should use normal test names. Reserve _eval suffixes for real provider-backed evals selected by the repository evals nextest group.
Core API
Task::new(prompt, workspace)describes the problem to solve and the starting workspace.Task::run(&agent)runs an agent on one task and returns aTaskRun.DockerAgent::new(image, command)runs an in-container command whose stdout is newline-delimitedAgentMessageJSON.default_eval_env_vars()forwards provider credentials and Aether-related environment into Docker while settingAETHER_HOME=/root/.aether.Workspace::empty()creates an isolated temp directory.Workspace::from_dir(path)copies fixture directory contents into a temp directory.Workspace::from_git_repo(GitRepoSpec { url, start_commit, gold_commit, subdir })clones and checks out a git repository.TaskRunexposes the prompt, final workspace, transcript, and failure context.Transcriptexposes agent messages and tool-call helpers.
Dockerized evals
Aether Evals mounts the workspace root at /workspace and runs the command from the effective eval cwd. The command receives:
AETHER_EVAL_WRAPPED_TASK_PROMPT— the prompt to send to the agent.AETHER_EVAL_WORKSPACE_ROOT=/workspace— the mounted workspace root.AETHER_EVAL_CWD— the command's effective cwd inside the workspace.
Stdout is reserved for AgentMessage JSON lines and must end with a terminal message such as {"type":"done"}. Diagnostic logging should go to stderr.
use ;
let agent = new
.with_env_vars
.with_ephemeral_mount;
let run = new
.run
.await?;
A wrapper script for evaluating Aether itself can delegate to headless JSON output:
#!/bin/sh
A declarative eval:
Assertions
Use normal Rust assertions over the returned TaskRun, its Transcript, and files on disk:
let run = new.run.await?;
assert!;
assert_eq!;
assert_eq!;
Aether Evals also exports small #[track_caller] helpers for common tool assertions:
assert_tool_called;
assert_tool_call_count;
assert_tool_call_with_args;
LLM judging runs through declarative eval files: add a rubric judge block to expect in a *.eval.json file. Each criterion is scored 0.0–1.0 by the judge model, weighted into an overall score, and blocking criteria below their threshold fail the eval. See the evals documentation for the file format.
Judge faults — transient LLM stream failures, unparseable responses, criterion sets that don't match the rubric — are recorded as failures on the eval's outcome rather than conflated with a "the agent didn't do it" verdict.
Failure output and debugging
TaskRun::failure_context() returns deterministic plain text suitable for assertion messages, nextest output, and JUnit failure bodies. It includes prompt, workspace path, agent messages, and git diff stats when available.
Temp directories are deleted when the task run is dropped.
Git-backed evals
use GitRepoSpec;
let run = new
.run
.await?;
assert!;
Development