> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fetchhive.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Running Tasks

> Start Hive Agent runs with objectives, optional sources, live status updates, and reusable blueprints

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? <a href="#start-run" id="start-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.

Review the warning in the dialog. Hive Agents can take minutes or days, and complex runs can become expensive.

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? <a href="#run-finished-notification" id="run-finished-notification" />

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](./notifications).

## How do I attach sources? <a href="#sources" id="sources" />

In **Start Run**, open **Sources** and click **Add Source**.

Choose one source type:

| Source type             | What it does                                                    |
| ----------------------- | --------------------------------------------------------------- |
| **Website**             | Scrapes content from one URL and attaches it to the run         |
| **File Upload**         | Uploads one PDF, Word, text, markdown, CSV, or spreadsheet file |
| **Knowledge Base**      | Uses all searchable content from one active Knowledge Base      |
| **Knowledge Base Item** | Uses one existing item from a Knowledge Base                    |

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? <a href="#source-preparation" id="source-preparation" />

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? <a href="#setup-required" id="setup-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](../workspace/api-keys) and create or activate a Default key.

## How do I track a running task? <a href="#track-running-task" id="track-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? <a href="#rerun" id="rerun" />

Yes. A Hive Agent is reusable.

Start another run from the same blueprint and enter a new **Run objective** or different sources. Blueprint settings apply to future runs. Existing runs keep the objective, sources, and runtime records they started with.

See also: [Logs](./logs), [Notifications](./notifications), and [Troubleshooting](./troubleshooting).