manus-config

Use `manus-config schedule create` with `--title`, `--detail`, and either `--cron` or `--interval`, plus `--repeated` for recurrence. Cron requires six fields like `0 0 9 * * 1-5` for weekdays at 09:00, and recurring intervals must be at least 300 seconds.

Run `manus-config config load --search <service-name>` to find the connector, edit `~/.manus/config/config.json` to enable it, then run `manus-config config save`. Always load before editing so the baseline diff is correct.

The diff is computed against a baseline snapshot refreshed only by `config load`. If you edited without loading first, or ran load again mid-edit, the baseline is stale or your edits were overwritten. Always load, edit, then save in that order.

manus-config cron uses six fields (seconds minutes hours day-of-month month day-of-week), not the common five-field format. A five-field expression shifts every value and fires off-schedule; rewrite it with a leading seconds field.

Each task supports only one schedule, so a duplicate create is rejected. Inspect the existing schedule with `manus-config schedule status`, then use `schedule update` to modify, pause, or reschedule it instead.

Use it only when the user explicitly asks for fresh, isolated, or clean execution at each firing. It requires a self-contained `--playbook`; otherwise the default re-triggers the current task and preserves prior context.