Creating an experiment
-c flag is required and points to the experiment config file. The experiment name is specified inside the YAML via the experiment_name field. Adding a - suffix to experiment_name appends a random unique ID — we recommend this to avoid name clashes.
You can override config values without editing the file by passing key=value arguments:
Listing experiments
| Column | Meaning |
|---|---|
| NAME | Experiment identifier |
| AGENTS | ready/total — e.g. 8/10 means 8 of 10 agents are ready |
| STATUS | Current experiment phase (see below) |
| AGE | Time since creation |
| Status | Description |
|---|---|
Pending | Experiment submitted, waiting to start |
ImageBuilding | Building container images |
InProgress | Agents are being initialized |
Running | Agents are executing experiments |
Completed | All agents finished successfully |
Viewing experiment details
name: Experiment identifierspec: Experiment specificationrepo: Source code repository configurationruntime: Execution settings (agents shows ready/total, e.g., 10/10)sandbox: Container environment and resources
status: Current statecreated: Creation timestamp and agephase: Current lifecycle phasemessage: Condition message (if available)
Streaming logs
Stream logs for a running experiment withhive logs. The --source flag selects where the logs come from:
--source sandbox together with --worker (0-based):
--no-follow to print the existing logs and exit:
Stopping experiments
--yes (or -y) to skip the confirmation prompt:
Viewing the dashboard
The experiment dashboard, which contains detailed information about all Hive experiments launched by your team, can be accessed by using:--no-browser to print the URL without opening a browser.