Harbor Task Folders

A task folder holds everything one task needs: the instruction, the container the agent works in, the tests that score it and, optionally, a reference solution. Because each task brings its own environment and tests, there’s no server to write.

Tasks that share one verifier and toolset, such as math, instruction following or tool calling, fit JSONL Datasets better.

Guides

Page	Read it when
Author Task Folders	You are writing your first task: scaffold a dataset, write a task, check it and run an agent on it. Already use Harbor? Start at Coming from Harbor.
Task Folder Format	You need a file or a setting: the folder layout, `task.toml`, `dataset.toml` and Dockerfile modes.
Task Folder Verifiers	You are writing `tests/`: reward files, Python verifiers, and shared or separate verification.
Multi-Step Task Folders	A task runs several steps in one sandbox.
Multi-Container Tasks	A task needs sidecar services from a Compose file.
Task Folder Patterns	You want parameterized tasks, typed task fields, task MCP tools or shared verifier code.

You pick the harness that runs the tasks with --agent; Integrate Existing Agents lists which harnesses run task folders. Harbor Environment Server explains how an episode runs.