Automations
Work that happens whether or not anyone opens the tab.
A schedule or a trigger, and the finding comes to your team.
Read the automations docs- Cron
- In a timezone you choose
- Events
- Fire on product activity
- 4 channels
- Slack, email, SMS, WhatsApp
- Threaded
- Every run stays readable
Clado
Olive
Codebuff
Attensira
Assemble
Opennote
Stratify
Gatekeep- Clado
- Olive
- Codebuff
- Attensira
- Assemble
- Opennote
- Stratify
- Gatekeep
- Clado
- Olive
- Codebuff
- Attensira
- Assemble
- Opennote
- Stratify
- Gatekeep
Triggers and delivery
When it runs, and where the answer lands.
Configured per agent. The one you chat with is the one that runs at 6am — there is no second configuration to keep in sync.
Cron schedules
Recurring runs in a timezone you choose, pausable without deleting the schedule you spent time getting right.
Event triggers
Fire an agent off something that happened in your product rather than off the clock.
Slack
A first-class channel: the agent listens for mentions and replies in-thread, so the conversation stays where the team is.
Email, SMS, WhatsApp
For the results that should interrupt someone. Channels are configured on the agent, not bolted on as a generic webhook.
Runs are readable
Every automated run becomes a thread in Recent chats, tagged with the channel it was delivered through.
Failures are visible
A failed run carries a red-dot Failed marker rather than silently producing nothing.
Setting one up
Three decisions, then leave it alone.
- 01
What it should do
Instructions and toolboxes — the same agent configuration you would build for interactive use.
- 02
When it should do it
Open Automations on the agent and add a cron row or an event trigger. Saving persists immediately.
- 03
Who should hear about it
Attach the channels. From then on the next scheduled run is pinned to the agent page so you know it is alive.
Details
What running unattended actually means.
- Upcoming run row
- An unpaused cron schedule with a next occurrence pins a non-clickable Upcoming run row to the agent page. Event triggers do not produce one.
- Paused is explicit
- The top bar reads Automations (paused) when nothing is scheduled to fire, so a quiet agent is never ambiguous.
- Tools stay scoped
- An automated run can only reach the toolboxes enabled on that agent, whatever else the project has connected.
Keep going
The rest of the platform.
Everything here reads from the same recorded session — there is nothing to stitch together between surfaces.
Stop guessing what happened.
One SDK, one afternoon. We will walk your team through it on a call and leave you with the recording of your own product.