The Anatomy of a Harbor Task

└── example-task/
    ├── task.toml        ◄
    ├── instruction.md
    ├── environment/
    │   ├── Dockerfile
    │   └── main.go
    ├── solution/
    │   └── solve.sh
    └── tests/
        └── test.sh

Task metadata

[metadata]
author_name = "Przemyslaw Hejman"
difficulty = "easy"
tags = ["trivial", "golang"]

[agent]
timeout_sec = 900.0

[environment]
cpus = 1
memory_mb = 4096

└── example-task/
    ├── task.toml
    ├── instruction.md   ◄
    ├── environment/
    │   ├── Dockerfile
    │   └── main.go
    ├── solution/
    │   └── solve.sh
    └── tests/
        └── test.sh

The prompt for LLM agent containing the actual assignment.

• Define role and goal clearly.
• Specify constraints (e.g., "DO NOT MODIFY main.go").
• Mention expected output location.

You are expert Go programmer.
Your task is to compile Go program from source
code located in `/app/src` and produce a working binary at `/app/bin/main`.
Do not modify any Go files.

└── example-task/
    ├── task.toml
    ├── instruction.md
    ├── environment/     ◄
    │   ├── Dockerfile   ◄
    │   └── main.go      ◄
    ├── solution/
    │   └── solve.sh
    └── tests/
        └── test.sh

The world your task lives in

• Dockerfile — environment in which the tasks runs.
• Input files: code and data (need to be explicitly copied).
• docker-compose.yaml (optional) for complex setups or network isolation.

└── example-task/
    ├── task.toml
    ├── instruction.md
    ├── environment/
    │   ├── Dockerfile
    │   └── main.go
    ├── solution/
    │   └── solve.sh
    └── tests/           ◄
        └── test.sh      ◄

How we know the agent succeeded

• test.sh — main verification script.
• It executes tests (e.g. pytest, diff) inside the environment.
• Writes score 1 (success) or 0 (failure) to /logs/verifier/reward.txt.
• Support of multidimensional metrics with reward.json.

└── example-task/
    ├── task.toml
    ├── instruction.md
    ├── environment/
    │   ├── Dockerfile
    │   └── main.go
    ├── solution/        ◄
    │   └── solve.sh     ◄
    └── tests/
        └── test.sh

Reference (oracle) solution

• Running solve.sh should make all tests pass.
• Optional, but useful for checking tests.
• Required for public benchmarks. e.g. TerminalBench.

harbor run -p "tasks/example-task" --agent oracle