Tasks overview

Work Henry does on a schedule: reminders, digests, check-ins, and recurring jobs.

A task is anything you want Henry to do on a schedule rather than when asked. A Monday pipeline summary. A daily check for blocked tickets. A weekly reconciliation of subscriptions against a spreadsheet. A one-time reminder next Thursday.

Tasks run unattended and report back into the conversation they belong to. They are approved once, at activation, so nobody has to be online to click Confirm.

What a task is made of

Part	What it is
Instructions	What Henry should do, written as a runbook. Henry writes this for you from a plain-language description, or you write it yourself.
Schedule	Once, every few minutes, hourly, daily, weekdays, or weekly, at a time in your timezone.
Model and reasoning	Which model runs it and how deeply it thinks. Defaults to the workspace setting.
Trigger (optional)	A cheap pre-check so the task only really runs when there is work to do.
Authorizations	The write tools the task may use without asking. Granted once at activation.
Learnings	Notes Henry keeps from past runs, which you can edit or clear.
Runs	The history: what each run did, what it cost, and whether anything was blocked.

Where tasks live

Open Tasks in the web app to see every task in the workspace. Filter by All tasks, My tasks, or System tasks, by Active or Paused, by author, or by model. Click a task for its detail page.

You can also manage tasks in chat: “what tasks do I have?”, “pause the standup digest”, “run the renewal check now”.

System tasks

Henry ships with a few of its own recurring jobs, marked System. Any member can run them. You can change when they run and which model they use, but not their instructions.

Creating tasks

From chat or the web app, with every schedule option.

Activating and running

Previews, activation, run now, and authorizing tools.

Triggers

Skip runs when there is nothing to do.

Reports and delivery

Where results go and how budgets show up.