Schedules
Some AI tasks are better on autopilot. A daily journal prompt at 8 AM. A weekly code summary on Friday afternoon. A monthly goals review on the first. Schedules let you set those up once and let Osaurus run them — you just review the results.
Where Watchers react to file changes, schedules run on a clock.
Quick start
- Open the Management window (
⌘ ⇧ M) → Schedules - Click Create Schedule
- Fill in:
- Name — what this schedule is for
- Frequency — once, daily, weekly, monthly, or yearly
- Time — when it runs (for recurring schedules)
- Agent — which agent handles the task
- Instructions — the prompt to send when it fires
- Click Save
The schedule is now active. Review past runs anytime via View Last Run.
Frequency options
| Frequency | What it does | Example |
|---|---|---|
| Once | Single run at a specific date | One-time reminder |
| Daily | Every day at a set time | Morning journaling |
| Weekly | Once a week on a chosen day | Weekly progress reports |
| Monthly | Once a month on a chosen date | Monthly goal reviews |
| Yearly | Once a year on a chosen date | Annual reflection |
For recurring schedules, configure the time (24-hour) and the day-of-week (weekly) or day-of-month (monthly).
Schedules run when Osaurus is active. If your Mac is asleep or Osaurus isn't running at the scheduled time, the task runs when you next launch the app.
Picking an agent
Each schedule runs through one of your agents. The agent's system prompt, default model, and theme apply to the run. Different schedules can use different agents.
Tools and skills are picked automatically at run time based on your instructions — pick the agent whose personality best fits the task; the right capabilities will load themselves. How auto-selection works →
Example pairings:
- Daily Journal — A reflective, conversational agent
- Code Summary — A technical agent (Git tools surface automatically when the prompt mentions a repo)
- Research Digest — A research-focused agent (Search and Fetch tools surface automatically)
Writing good instructions
Be specific. The instructions are the prompt sent to the agent — clear prompts produce useful runs.
Daily journaling:
Good morning! Let's start the day with a brief reflection.
Please ask me:
1. What are my top 3 priorities for today?
2. Is there anything from yesterday I need to follow up on?
3. What's one thing I'm looking forward to?
Keep the conversation warm and encouraging.
Weekly report:
Generate a weekly summary based on our conversations from the past week.
Include:
- Key topics discussed
- Decisions made
- Action items identified
- Questions that remain open
Format as a concise bullet-point summary.
Managing schedules
Viewing your schedules
The Schedules tab shows all your configured schedules with name, frequency, next run time, assigned agent, and active/paused status.
Editing
- Click on the schedule
- Modify the settings
- Click Save
Pausing and resuming
Toggle a schedule on or off without deleting it. Paused schedules don't run until you resume them.
Running manually
Trigger any schedule immediately:
- Click on the schedule
- Click Run Now
Useful for testing new schedules, running outside the normal time, or catching up on missed runs.
Deleting
- Click on the schedule
- Click Delete
- Confirm
Reviewing past runs
After a schedule fires, you can see exactly what happened:
- Click on the schedule
- Click View Last Run
The full conversation opens — your instructions, the agent's response, any tool calls or actions taken.
Each run is also saved as a chat session tagged schedule (visible as a badge in the chat sidebar). Filter the sidebar by source to browse all your scheduled runs in one place.
Example schedules
Daily journaling
| Setting | Value |
|---|---|
| Name | Morning Journal |
| Frequency | Daily at 8:00 AM |
| Agent | Personal Coach |
| Instructions | "Start my day with 3 reflection questions about priorities, energy, and gratitude." |
Weekly code summary
| Setting | Value |
|---|---|
| Name | Weekly Dev Summary |
| Frequency | Weekly on Friday at 5:00 PM |
| Agent | Code Assistant |
| Instructions | "Review git activity this week and summarize commits, branches, and open items." |
Monthly goals
| Setting | Value |
|---|---|
| Name | Monthly Goals Review |
| Frequency | Monthly on the 1st at 9:00 AM |
| Agent | Personal Coach |
| Instructions | "Let's review my goals for last month and set intentions for the new month." |
Daily news digest
| Setting | Value |
|---|---|
| Name | Tech News Digest |
| Frequency | Daily at 7:00 AM |
| Agent | Research Helper |
| Instructions | "Search for the latest AI and developer tools news and give me a 5-item digest." |
Tips
- Start simple — Begin with one or two schedules and add more as needed
- Use descriptive names — Make it easy to identify schedules at a glance
- Match agent to task — Choose an agent with appropriate tools and style
- Be specific in instructions — Clear prompts yield better results
- Review results regularly — Check that schedules are producing useful output
- Adjust timing — Find times that work with your routine
- Use "Run Now" to test — Verify new schedules work before waiting for the timer
Troubleshooting
Schedule didn't run
- Was Osaurus running? Schedules require the app to be active
- Is the schedule enabled? Paused schedules don't run
- Has the time passed yet? Check the next-run time on the card
Unexpected results
- Review the instructions — Ambiguous prompts lead to inconsistent results
- Check the agent — Make sure the right agent is assigned
- Inspect what tools fired — Open Insights (
⌘ ⇧ M→ Insights) to see exactly which capabilities were loaded and which tool calls ran. If the wrong tools loaded, make the schedule's instructions more specific.
Missed schedules
If Osaurus wasn't running at the scheduled time:
- The schedule runs on next app launch (if configured for catch-up)
- Or waits until the next scheduled time
- Use "Run Now" to trigger manually
Related: