[Fix] Automation manager misses built-in schedule presets - #1001
Merged
Conversation
Contributor
Author
mrubens
marked this pull request as ready for review
August 2, 2026 19:39
mrubens
requested review from
brunobergher,
daniel-lxs and
mrubens
as code owners
August 2, 2026 19:39
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
The custom automation management MCP now names every built-in schedule preset (
off,every_hour,every_6_hours,daily, andweekly) and directs callers to prefer a matching preset over an equivalent generated schedule. The description is sourced from the shared preset list, with regression coverage for the exposed tool schema.Why this change was made
The MCP previously described the schedule input only as accepting a generic "preset," so agents could not discover the canonical values already supported by automation settings.
Impact
Agents can reliably select the same hourly, daily, and weekly cadence values used by built-in automation settings. Existing five-field cron and natural-language schedule support is unchanged.