Use a scheduled trigger to fire an Expert on a recurring cron schedule — daily standups, hourly health checks, end-of-week reports. Add one from the Triggers section of the Expert editor.Documentation Index
Fetch the complete documentation index at: https://docs.augmentcode.com/llms.txt
Use this file to discover all available pages before exploring further.
Adding a Schedule
- Open Experts in the sidebar and click the Expert you want to schedule (or click + Create Expert to make a new one).
- Scroll to the Triggers section and click + Add Trigger.
- In the trigger row, set:
- Name — a human-readable label (e.g.
weekday-standup). - Type —
Scheduled. - Cron expression — a 5-field cron string (see below).
- Timezone — an IANA timezone name (e.g.
America/New_York); leave blank for UTC. - Auto-archive sessions created by this trigger — toggle off if you want sessions to remain after they go idle.
- Name — a human-readable label (e.g.
- Click Save.
Once a schedule trigger is created, its type and timezone are fixed. To change them, delete the trigger and add a new one.
Cron Syntax
Cosmos uses 5-field crontab (no seconds, no macros like@daily or @hourly):
| Position | Field | Values |
|---|---|---|
| 1 | minute | 0–59 |
| 2 | hour | 0–23 |
| 3 | day of month | 1–31 |
| 4 | month | 1–12 or JAN–DEC |
| 5 | day of week | 0–6 (Sunday=0) or SUN–SAT |
* (wildcard), , (list), - (range), / (step).
Common Cron Examples
| Expression | Meaning |
|---|---|
* * * * * | Every minute |
*/5 * * * * | Every 5 minutes |
0 * * * * | Top of every hour |
0 0 * * * | Daily at midnight |
0 9 * * MON-FRI | 09:00 every weekday |
0 9-17/2 * * MON-FRI | Weekdays at 09, 11, 13, 15, 17 |
0 0 * * 0 | Weekly, Sunday midnight |
0 0 1 * * | Monthly, 1st at midnight |
0 0,12 * * * | Twice daily, midnight and noon |
Concurrency and Reliability
- Each schedule runs in singleton mode: if the next fire arrives while the previous run is still executing, that fire is skipped — runs are not queued.
- Missed fires during pod transitions or leadership changes are not backfilled.
- The session executes with the permissions of the user who created the schedule.