Reports and delivery

​

Where results go

Tasks report into the conversation they belong to:

• A task created in a Slack channel posts to that channel. Long reports post a short summary with the full details in a thread.
• A task created in a DM or in the web app posts to your Slack DM with Henry (or your Teams chat).
• A task created in Teams posts to that Teams conversation.

The task dialog’s preview shows the destination as Delivers to before you save. If your workspace has no chat platform connected yet, results have nowhere to go until you link one. If both Slack and Teams are connected, admins choose the Default surface in Settings → Team settings for reports not tied to a conversation.

​

Quiet when there is nothing to say

A run that finds nothing worth reporting ends as No update and posts nothing. Combined with triggers, this keeps recurring tasks from becoming noise.

​

The budget note

Every run has a credit budget so a single task cannot drain your balance. When a run reaches it, Henry finishes the highest-value work, posts what it did, and adds a scope note listing anything not done. Reply “finish the rest” in the thread and Henry runs it again right away, or raise the task’s per-run budget from its settings.

​

Cost per run

Each run’s credit cost appears in Recent runs on the task page, and the Usage page shows cost per task over time under Where your credits go. To bring a line down, open the task and change its model tier, add a trigger, or lower its per-run budget. See Usage.