Share feedback
Answers are generated based on the documentation.

sbx schedule update

DescriptionUpdate a schedule's settings or what it runs
Usagesbx schedule update SCHEDULE_ID [KIT] [flags]

Description

Update a schedule's settings or what it runs.

--name, --description, --cron, --timezone and --enabled change only those settings. Any other flag, or KIT, rebuilds what each run executes from the flags given, so restate --prompt or --command and every run flag to keep: --static-mcp, the network flags, --max-run-duration, --cpus, --memory, --platform, --env and --working-dir not given again are reset, with a warning. Without KIT, the schedule's current kit is resolved again.

Options

OptionDefaultDescription
--allow-networkNetwork pattern each run's sandbox may reach (can be repeated); other egress is denied
--commandShell command each run executes
--cpus0CPUs for each run's sandbox (default: the kit's)
--cronFive-field cron expression for when runs start, e.g. "0 9 * * 1-5"
--deny-networkNetwork pattern to deny within --allow-network (can be repeated)
--descriptionDescription of the schedule
--enabledtrueStart runs on the cron cadence; --enabled=false pauses the schedule
-e, --envSet an environment variable for each run (can be repeated): KEY=VALUE
--env-fileRead environment variables from a file (can be repeated). --env wins over any file; a later file wins over an earlier one
--max-run-duration0sLongest a run may take, at least 1h, e.g. 2h30m (default: 1h)
-m, --memoryMemory for each run's sandbox, e.g. 8g (default: the kit's)
--nameName of the schedule
--platformPlatform for each run's sandbox: linux/amd64 or linux/arm64
--promptPrompt each run passes to the kit's agent
--static-mcpCloud MCP gateway servers each run's sandbox gets, comma-separated or repeated
--timezoneIANA time zone the cron expression is evaluated in, e.g. Europe/Berlin
--working-dirDirectory the prompt or command runs in

Global options

OptionDefaultDescription
--cloudDispatch to Docker Cloud Sandboxes API instead of local sandboxd (supported by a growing set of verbs — run 'sbx --cloud --help' for the current list)
-D, --debugEnable debug logging
--no-inputNever prompt; commands that need an answer fail with the command to run instead

Examples

sbx --cloud schedule update SCHEDULE_ID --enabled=false
sbx --cloud schedule update SCHEDULE_ID --cron "0 6 * * 1-5" --timezone America/New_York
sbx --cloud schedule update SCHEDULE_ID --prompt "Triage new issues" --static-mcp github