Set up routines
A routine is a prompt the agent runs on a schedule. Each run starts a new thread in the group with the agent's answer, under the subject you chose. Members can reply to it like any other thread, and the agent picks up the follow-ups.
Good routines are standing jobs nobody wants to compile by hand:
- "Every Monday at 9, summarize last week's threads: decisions made, open questions, and who owes what."
- "Each weekday morning, list threads from the last day that asked a question nobody answered."
- "On the 1st, check the vendor contracts in the group files and flag any that renew this month."
Set one up
Group admins manage routines on the group's Routines page. A routine has:
| Field | What it is |
|---|---|
| Name | How it's listed, e.g. "Monday digest" |
| Email subject | The subject of the thread each run starts |
| Schedule | A cron expression, e.g. 0 9 * * 1 for Mondays at 09:00 |
| Time zone | An IANA zone like America/New_York. UTC if left as is |
| Prompt | What the agent should do each run |
Routines can run at most once an hour.
Run, pause and delete
On the Routines page, admins can Run now, Pause or Resume, and Delete each routine. The page shows each routine's next and last run.
From the group, anyone can send @cloud !routines to list them.
When a routine fails
A routine that fails three times in a row turns itself off. The group's activity log records that it turned off, and Recent turns on the Usage & activity page shows each failed run's error. Resume it on the Routines page once the cause is fixed.
After a lost response, Cloud Tag looks for the exact accepted request in session history. If it cannot identify it safely, the request may already have run: an admin must inspect the session named in the error before running it again.
An uncertain dispatched request is not automatically resent, even if history looks empty. Its thread pauses for input review. Check the earlier run before using Run now to request another run.
Routines don't run while the group is muted, and they're stopped by the same spend limits as any other reply.
Not built yet
Claude Tag can also watch a channel for matching messages and subscribe to pull requests. In Cloud Tag, Respond automatically is the nearest thing to watching: the agent reads every new thread and replies when it can help. See Control when it responds.