You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Minor Changes
#1720f3860 Thanks @G4brym! - Add trigger_schedule MCP tool to manually trigger a schedule run
Adds a new MCP tool that allows agents and users to trigger a schedule to run immediately without waiting for the cron interval. The run is started asynchronously and returns the run ID so callers can check status via list_runs. Disabled schedules are rejected, and the concurrent run limit is enforced.
Patch Changes
#2053c5d4d Thanks @G4brym! - Fix schedules with identical cron patterns — all matching schedules now fire
Snapshot the running-run count once before the tick loop instead of re-querying
inside the loop. This prevents a run created for schedule A from counting against
schedule B's concurrency check when both share the same cron expression.
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Patch Changes
#9d418fc4 Thanks @G4brym! - Add daemon restart command with config validation and webui dependency checks. The install command now also validates config before proceeding. Invalid config values produce clear warnings with fix tips.
fix: use changesets output instead of npm view for GitHub Release
The npm registry has propagation delay, so npm view fails immediately
after publish. Use steps.changesets.outputs.published instead.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>