Automations Rebuilt

The automations system got a full rework: reliability fixes and a redesigned dashboard surface on top.

Reliability fixes

Three bugs in how scheduled runs fire are fixed:

• Double-fires are prevented. An automation could fire twice in the same minute. Each scheduled occurrence now fires exactly once.
• Pinned agents run where they're pinned. A Slack or Discord automation with a pinned agent was running on the channel's default agent instead. Pinned agents now receive the run when they're connected to the channel; the channel default is the fallback.
• Automations queued while no agent was free are now delivered. A Slack automation that fired while no agent was available could be silently dropped. Those runs are now delivered correctly when an agent becomes free.

Run now

Any automation can be triggered immediately from its task page. The run doesn't touch the next scheduled fire time, so it's safe to use for testing before enabling. It shows up in the runs history as a manual run.

Runs history

Each automation's task page shows every run: when it started, whether it was scheduled or manual, which agent handled it, and a link to the Slack or Discord message it replied to. The automation list rows show last run (with a status dot) and next run as a relative time.

Redesigned list and form

• List: each row shows what the automation does (name or the prompt's first line), where it runs (channel, agent, model), and when (cadence as readable prose, last run, next run).
• Form: rebuilt in sections — Task, Where, When, Options. The schedule field has preset buttons (Hourly, Daily, Weekdays, Weekly, custom cron) with a next-runs preview in the automation's timezone. Automations can now have an optional name; unnamed ones display the first line of their prompt.
• Task page: a dedicated page per automation with the full prompt, run history, and audit history.