Skip to main content
A Hive Agent run starts from a blueprint and adds the work for one execution: the objective, optional sources, status, trace, costs, nodes, and final result.

​
How do I start a run?

Open a Hive Agent in the editor. Click Start Run. Enter a Run objective. This field is required and should describe what this run should accomplish. Choose a Search country. This defaults to United States and localizes web search tools for this run (GPT Search, Anthropic Web Search, Sonar Web Search, and Perplexity Search). It overrides the Location Country saved on those tools for this execution only. Review the warning in the dialog. Hive Agents can take minutes or days, and complex runs can become expensive. Optionally attach Sources, then set Notify me when this run finishes if you want a completion alert. Click Start Run. Fetch Hive starts the run, closes the dialog, and opens Run Console in the editor so you can watch progress without leaving the page.

​
Can I get notified when this run finishes?

In Start Run, turn on Notify me when this run finishes to override the blueprint default for one execution. The switch starts from the value saved in Notifications. Delivery uses the same Send via, Email address, and Telegram account settings as budget alerts. See Notifications.

​
How do I attach sources?

In Start Run, open Sources and click Add Source. Choose one source type: Sources are per-run. They do not become blueprint defaults. Website and file sources go through source preparation before planning. Fetch Hive processes them into searchable context, records their source-preparation cost, and fails the run before planning if a required source cannot be prepared.

​
What does source preparation do?

Source preparation makes run sources available to the planner, executor, and verifier. For website and file sources, Fetch Hive creates or reuses run-source Knowledge Base records, processes the content, and waits until searchable chunks are ready. For existing Knowledge Bases or Knowledge Base items, Fetch Hive references the selected content without copying the whole source. The planner receives a compact source manifest. Executor and verifier stages retrieve focused source chunks as they work. Full source bodies are not dumped into the planner prompt.

​
What setup is required?

Your workspace must have an active Default API key before dashboard Hive Agent runs can start. Fetch Hive uses that key for run attribution and tracing. It does not create a Default key as a side effect of starting a run. If run start fails with a Default API key error, open API Keys and create or activate a Default key.

​
How do I track a running task?

Hive Agent status updates are live. As the run moves through source preparation, planning, execution, verification, retrying, composition, budget checks, and finalization, Fetch Hive updates the run and logs views. After you start a dashboard run, Fetch Hive opens Run Console in the editor so you can follow progress without leaving the page. You can also open Hive Agents > Logs to inspect the historical run table; selecting a run opens the same console. In the Run Console, Pass means the current execute-and-verify round. Attempts are the recorded execute or verify tries for a specific node inside those passes. Compose attempts are tracked separately after node work has been verified. Use View technical trace from the Run Console when you need the detailed request sheet with trace spans, child requests, timings, cost, tokens, inputs, outputs, and metadata. Use the request ID from logs if you need to open the same run from global search.

​
Can I rerun the same Hive Agent?

Yes. A Hive Agent is reusable. Start another run from the same blueprint and enter a new Run objective, a different Search country, or different sources. Blueprint settings apply to future runs. Existing runs keep the objective, search country, sources, and runtime records they started with. See also: Logs, Notifications, and Troubleshooting.