What a schedule is
A schedule is a standing order: an agent, a prompt, one or more clients, and a cadence. Omega runs it for you and delivers the output — no reminders, no copy-pasting last week's request.
Find them under the Agents product: choose Schedules in the Automation group of the left rail.
Create a schedule
Click New schedule.
Give it a name and pick the agent that should run.
Write the prompt — exactly what you'd type if you were asking by hand.
Choose the clients. The client pinned in your top-bar client picker is added automatically; you can remove it or add several clients, and the schedule runs once per client each time it fires.
Set the cadence — Daily, Weekly, or Monthly, with a time and timezone. An Advanced tab is there if you need a custom pattern.
Pick where it delivers: in-app, to a Slack channel, or as a Slack direct message.
Save. The list shows the cadence and the next run time at a glance.
Tip: You rarely need to start from scratch. After a good chat output, choose the option to run it on a schedule — the form opens with the agent and the exact prompt already filled in, so all that's left is the cadence. The same shortcut lives on each agent's detail page.
Checking upcoming and past runs
Click any schedule to open its detail panel:
The header shows the cadence and when it runs next.
Recent runs lists each past run per client, with a status dot (delivered, failed, or delivery issue) and a note about where it was delivered.
Open on any run takes you to the full conversation and output for that run.
If a run produced its output but the delivery didn't land, a Re-deliver button sends it again.
Deliverables from scheduled runs are also filed into each client's folder in Files, so there's always a durable copy in the library.
Pausing, editing, and running on demand
Run now fires the schedule immediately — handy for testing a new prompt.
The Enabled toggle pauses a schedule without deleting it; paused schedules show a badge in the list.
Edit changes any part of it; Delete removes it for good.
Note: A schedule with several clients fans out — each client gets its own run, its own delivery, and its own row in Recent runs, so one flaky data source never hides the others.