Skip to main content
Hive Agents can send four kinds of dashboard alerts. All of them reuse the same Notifications delivery settings on the Hive Agent blueprint: Send via (Email or Telegram), optional Email address, and optional Telegram account. These alerts are separate from public API callbacks. Callbacks are HTTPS webhooks for code integrations. Dashboard notifications are email or Telegram messages for people working in Fetch Hive.

​
Comparison

​
Who receives alerts?

Clarification requests and budget approvals go to the Hive Agent creator when that person is still an account member. If not, Fetch Hive uses the account owner. Run finished alerts prefer the dashboard user who started the run. If the run was started without a user (for example from the public API), Fetch Hive falls back to the same creator → account owner rule. If Email address is set under Notifications, alerts go there. Otherwise Fetch Hive uses the resolved recipient’s account email.

​
Configure delivery

Open the Hive Agent editor and click the bell button in the editor control bar to open Notifications.
  • Notify when run finishes — task-level default for run-finished alerts (off by default)
  • Send via — Email or Telegram
  • Email address or Telegram account — optional override for where alerts are delivered
If Send via is Telegram but no active Telegram destination is available, Fetch Hive falls back to email. See Creating and Configuring for the Budget Settings and Notifications controls.

​
Clarification request

This alert fires when planning cannot continue until a person answers one clarifying question. The message includes the objective and a link to the clarification page. While waiting, the run status is blocked. See Clarification Requests for answer, expiry, and resend behavior.

​
Budget hint approval

This alert fires when a run crosses the Budget Hint (USD) and Fetch Hive pauses for human review. Typical causes:
  • Budget Strictness is Conservative — Fetch Hive pauses soon after the hint is crossed
  • Budget Strictness is Balanced — the run may continue with lower concurrency first, then pause if spending keeps rising
The message summarizes spend against the hint. Additional budget (USD) is optional on the approval page. While waiting, the run status is blocked. See Budget Approval for approve, decline, expiry, and resend behavior.

​
Hard cap approval

This alert fires when cumulative spend plus projected next gated work reaches the Budget Cap (USD) and either When hard cap is reached is Ask for approval, or the pause is at Compose (Compose always asks for approval at the hard cap, even under Stop run). The message includes:
  • Spend so far against the hard cap
  • Estimated cost for the next gated work
  • A suggested additional budget amount
Additional budget (USD) is required on the approval page for hard-cap pauses. Approval raises the cap by the amount you enter, then budget is checked again before work continues. If the amount is too low, the run can pause again.

​
Run finished

This alert fires when a run reaches a terminal status:
  • completed
  • failed
  • cancelled
It does not fire when a run is blocked waiting for budget approval or clarification — those alerts already went out.

​
Task default

In Notifications, turn on Notify when run finishes to make this the default for future dashboard runs.

​
Per-run override

In Start Run, use Notify me when this run finishes to override the task default for one execution. See Running Tasks. The message matches the budget-approval email layout: heading, short status summary (including the Hive Agent name), objective, total spend, and a View run log link to open the run in Logs. See also: Clarification Requests, Budget Approval, Running Tasks, and Logs.