Skip to main content
HLE evaluates hard human-level questions and usually relies on a judge model for normalized scoring.

Runtime Status

FieldValue
Benchmark idhle
TagsDeep Research, Reasoning, Judge-Scored
Execution typelocal with judge
Typical harnessresearchharness or naive_search_agent
Typical environmenthost_process
Current statusregistered in the direct runtime

When to Use

Use HLE when you need to measure deep research behavior with the task assumptions described by this benchmark. For large or remote benchmarks, prefer benchmark recipes so images, workspaces, and provider-specific defaults come from task metadata instead of manual CLI flags.

Parameters

Common parameters for this benchmark include:
  • category
  • judge_model
  • sample_ids
  • max_concurrency
Shared runtime controls such as k, avgk, sample_ids, resume, and category follow the conventions in Benchmark Parameters.

Run Example

agentcompass run \
  hle \
  researchharness \
  your-model \
  --env <env-provider> \
  --benchmark-params '{"sample_ids":["<task-id>"]}' \
  --model-base-url "$MODEL_BASE_URL" \
  --model-api-key "$MODEL_API_KEY" \
  --model-api-protocol openai-chat
Adjust the harness and environment to the supported combination for your branch and deployment.

Outputs

Per-task details are written to results/hle/<model>/<run>/details/. Aggregate metrics are written to summary.md in the same run directory.

Notes

Use hle_verified when you need the verified subset.