Skip to main content
task.toml describes what the task needs. Start with a small configuration and add settings when the task depends on them.
task.toml
artifacts is a top-level key. Place it before any [table] header, as above.
For every accepted field and default, use the task.toml reference.

Time and resources

A job’s --timeout-multiplier scales the task timeouts. Provider limits still apply. Use sandbox capabilities to check whether a provider can satisfy the task.

Network access

allowed_hosts is valid only alongside network_mode = "allowlist".
task.toml

Change access for the agent phase

The environment policy applies during setup and after the agent finishes. An [agent] policy can override it while the agent runs.
task.toml
A shared verifier uses the restored environment policy. A different [verifier].network_mode requires a separate verifier. Its policy resolves from [verifier.environment], or a copy of [environment] when that table is absent, then applies any [verifier] override. The legacy allow_internet = false means no-network; true means public. An explicit network_mode takes precedence.

Environment variables

task.toml
Templates must occupy the whole value. A missing required secret rejects job creation. Keep credentials out of literal values: dataset contents are not a secret store. The image’s startup process receives literals only. Secret templates are resolved for the agent and processes it launches. Healthchecks never receive secret templates; a single-container healthcheck also does not receive the task’s literal table.

Save outputs

For separate verification, artifacts names the files or directories to copy into the verifier sandbox. Retained files also appear in the job archive. A shared verifier reads the agent’s existing filesystem directly and does not export this artifact list; use the filesystem commands to inspect live or captured files.
task.toml
Sources are absolute paths. destination is relative to the stored artifacts/ directory. It does not change the source path used to restore a file in a separate verifier. See verification and artifacts for a complete example.

Start from a saved conversation

Put a valid ATIF trajectory.json beside the instruction. Evolve loads it as the agent’s conversation history before giving it the new instruction. This works with Claude Code and Codex.
Only the conversation is restored. Put any files it depends on in the task environment. An invalid trajectory is rejected during import; a harness that cannot load it is rejected before the agent runs.
trajectory.json
This authored example supplies conversation context; it does not create a report file. The next instruction can ask the agent to use the earlier title.Imports accept ATIF-v1.0 through ATIF-v1.7. Steps are numbered from 1 in order. Evolve converts the document into the selected harness’s session format. Multimodal content is reduced to text; image parts become placeholders.
There is no trajectory setting in task.toml or run-level load flag in Evolve. For multi-step tasks, place the trajectory beside the first step’s instruction; later steps start fresh.

Other task inputs

Validate before publishing

This checks task configuration without uploading the corpus or building images. A successful check does not prove that an image builds or that the verifier is correct. Use task checks for the latter.