opencode-scheduler

opencode-scheduler

Run AI agents on a schedule. Set up recurring tasks that execute autonomously—even when you're away.

Schedule a daily job at 9am to search Facebook Marketplace for posters under $100 and send the top 5 deals to my Telegram

This is an OpenCode plugin that uses your OS's native scheduler (launchd on Mac, systemd on Linux) to run prompts reliably—survives reboots, catches up on missed runs.

Install

Add to your opencode.json:

{
  "plugin": ["opencode-scheduler"]
}

Examples

Daily deal hunting:

Schedule a daily job at 9am to search for standing desks under $300

Weekly reports:

Schedule a job every Monday at 8am to summarize my GitHub notifications

Recurring reminders:

Schedule a job every 6 hours to check if my website is up and alert me on Slack if it's down

Commands

Command	Example
Schedule a job	Schedule a daily job at 9am to...
List jobs	Show my scheduled jobs
Get version	Show scheduler version
Get skill template	Get the scheduled job best practices skill
Get job	Show details for standing-desk
Update job	Update standing-desk to run at 10am
Run immediately	Run the standing-desk job now
View logs	Show logs for standing-desk
Delete	Delete the standing-desk job

How It Works

• You describe what you want scheduled in natural language
• The plugin creates a cron job and installs it in your OS scheduler
• At the scheduled time, OpenCode runs your prompt autonomously
• Output is logged to ~/.config/opencode/logs/

You can also trigger a job immediately via run_job—it runs fire-and-forget and appends to the same log file.

Jobs run from the working directory where you created them, picking up your opencode.json and MCP configurations.

Reference

Cron Syntax

Jobs use standard 5-field cron expressions:

┌───────────── minute (0-59)
│ ┌───────────── hour (0-23)
│ │ ┌───────────── day of month (1-31)
│ │ │ ┌───────────── month (1-12)
│ │ │ │ ┌───────────── day of week (0-6, Sunday=0)
│ │ │ │ │
* * * * *

Expression	Meaning
0 9 * * *	Daily at 9:00 AM
0 */6 * * *	Every 6 hours
30 8 * * 1	Mondays at 8:30 AM
0 9,17 * * *	At 9 AM and 5 PM daily

Tools

Tool	Description
schedule_job	Create a new scheduled job
list_jobs	List all scheduled jobs
get_version	Show scheduler and opencode versions
get_skill	Get built-in skill templates (best practices)
get_job	Fetch job details and metadata
update_job	Update an existing job
delete_job	Remove a scheduled job
run_job	Execute a job immediately (fire-and-forget)
job_logs	View logs from a job

Tools accept an optional format: "json" argument to return structured output with success, output, shouldContinue, and data.

Storage

What	Where
Job configs	~/.config/opencode/jobs/*.json
Logs	~/.config/opencode/logs/*.log
launchd plists (Mac)	~/Library/LaunchAgents/com.opencode.job.*.plist
systemd units (Linux)	~/.config/systemd/user/opencode-job-*.{service,timer}

Working Directory

Jobs run from a specific directory to pick up MCP configs:

Schedule a daily job at 9am from /path/to/project to run my-task

By default, jobs use the directory where you created them.

Attach URL (optional)

If you have an OpenCode backend running via opencode serve or opencode web, you can set attachUrl on a job so runs use that backend:

Update the standing-desk job to use attachUrl http://localhost:4096

Project Philosophy

• This plugin is intentionally a thin wrapper: it schedules opencode run via launchd (Mac) or systemd (Linux).
• We avoid prompt “injection” as a feature. If a job needs dynamic values (dates, paths, etc.), the prompt should compute them at runtime using tools.
• Prefer non-interactive dependencies for scheduled runs (e.g., Telegram Bot API over web.telegram.org).
• Logs are the source of truth for scheduled runs: ~/.config/opencode/logs/*.log.
• Resiliency/reporting roadmap (not implemented): PRD-resilient-execution.md.

Built-in Skill Templates

Use get_skill to fetch scheduled-job-best-practices, copy it into your repo, then add @scheduled-job-best-practices at the top of scheduled job prompts.

Troubleshooting

Jobs not running?

• Check if installed:

  • Mac: launchctl list | grep opencode
  • Linux: systemctl --user list-timers | grep opencode

• Check logs: Show logs for my-job

• Verify the working directory has the right opencode.json with MCP configs

MCP tools not available?

Make sure the job's working directory contains an opencode.json with your MCP server configurations.

License

MIT