> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.nvidia.com/nemo/gym/main/data/task-folders/llms.txt. # Harbor Task Folders > Write, validate and run tasks as task folders in the Harbor format, on the harbor Environment Server. 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](/main/data/jsonl) better. ## Guides | Page | Read it when | | ---------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [Author Task Folders](/main/data/task-folders/harbor-tasks) | 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](/main/data/task-folders/harbor-tasks#coming-from-harbor). | | [Task Folder Format](/main/data/task-folders/task-folder-format) | You need a file or a setting: the folder layout, `task.toml`, `dataset.toml` and Dockerfile modes. | | [Task Folder Verifiers](/main/data/task-folders/task-folder-verifiers) | You are writing `tests/`: reward files, Python verifiers, and shared or separate verification. | | [Multi-Step Task Folders](/main/data/task-folders/multi-step-tasks) | A task runs several steps in one sandbox. | | [Multi-Container Tasks](/main/data/task-folders/compose-tasks) | A task needs sidecar services from a Compose file. | | [Task Folder Patterns](/main/data/task-folders/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](/main/agent-server/integrate-existing-agents#sandboxed-harnesses) lists which harnesses run task folders. [Harbor Environment Server](/main/agent-interactions/harbor) explains how an episode runs. > Write, validate and run tasks as task folders in the Harbor format, on the harbor Environment Server. ## Docs - [Author Task Folders](https://docs.nvidia.com/nemo/gym/main/data/task-folders/harbor-tasks.md): Write a task folder, check it with the oracle, run an agent on it, and pull or publish Harbor datasets. - [Task Folder Format](https://docs.nvidia.com/nemo/gym/main/data/task-folders/task-folder-format.md): The files of a task folder and a dataset of task folders, the task.toml and dataset.toml fields Gym reads, Dockerfile modes, Harbor compatibility and what the loader refuses. - [Task Folder Verifiers](https://docs.nvidia.com/nemo/gym/main/data/task-folders/task-folder-verifiers.md): The contract a task folder's tests/ must meet: reward files, Python verifiers, reference answers, sidecar inputs and shared or separate verification. - [Multi-Step Task Folders](https://docs.nvidia.com/nemo/gym/main/data/task-folders/multi-step-tasks.md): Write a task folder with [[steps]] that runs as several turns in one sandbox, each with its own instruction and verifier, rolled up into one reward. - [Multi-Container Tasks](https://docs.nvidia.com/nemo/gym/main/data/task-folders/compose-tasks.md): Author a task folder whose environment runs sidecar containers beside the agent's sandbox, described with Docker Compose. - [Task Folder Patterns](https://docs.nvidia.com/nemo/gym/main/data/task-folders/task-folder-patterns.md): Generate many tasks from one template, type each task's fields, give a task its own MCP tool, and share verifier code across tasks.