		{
		"name": "opencode-scheduler",
		"version": "1.0.1",
		"version": "1.0.2",
		"description": "OpenCode plugin for scheduling recurring jobs using launchd (Mac) or systemd (Linux)",
		@@ -5,0 +5,0 @@ "main": "dist/index.js",

+14

-0

README.md

		@@ -45,2 +45,3 @@ # opencode-scheduler
		\| Get version \| `Show scheduler version` \|
		\| Get skill template \| `Get the scheduled job best practices skill` \|
		\| Get job \| `Show details for standing-desk` \|
		@@ -95,2 +96,3 @@ \| Update job \| `Update standing-desk to run at 10am` \|
		\| `get_version` \| Show scheduler and opencode versions \|
		\| `get_skill` \| Get built-in skill templates (best practices) \|
		\| `get_job` \| Fetch job details and metadata \|
		@@ -131,2 +133,14 @@ \| `update_job` \| Update an existing job \|

		## 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
		@@ -133,0 +147,0 @@

dist/index.js

Sorry, the diff of this file is too big to display

opencode-scheduler - npm Package Compare versions

New alerts