schedule

Schedule

Manage scheduled workflow jobs for the Claude Octopus scheduler.

Usage

Preflight — Ensure plugin root is resolvable (run via Bash tool FIRST):

OCTO_ROOT="${HOME}/.claude-octopus/plugin"
if [[ ! -x "$OCTO_ROOT/scripts/orchestrate.sh" ]]; then
  helper="$OCTO_ROOT/scripts/helpers/ensure-plugin-root.sh"
  if [[ ! -x "$helper" ]]; then
    helper="$(find "${HOME}/.claude/plugins/cache" "${HOME}/Library/Application Support/Claude" "${LOCALAPPDATA:-/dev/null}/Claude" "${XDG_DATA_HOME:-${HOME}/.local/share}/Claude" -maxdepth 8 -path "*/nyldn-plugins/octo/*/scripts/helpers/ensure-plugin-root.sh" -print -quit 2>/dev/null)"
  fi
  [[ -x "$helper" ]] && bash "$helper" >/dev/null 2>&1 || true
fi
test -x "$OCTO_ROOT/scripts/orchestrate.sh" && echo "plugin-root:ok" || echo "plugin-root:missing"

If the output is plugin-root:missing, stop and ask the user to run /octo:setup.

${HOME}/.claude-octopus/plugin/scripts/scheduler/octopus-scheduler.sh [subcommand]

Instructions for Claude

This command supports natural language and provides two primary experiences:

• No args / "show jobs" / "what's scheduled" → Dashboard table
• "add a job" / "schedule X" / add with no file → Guided wizard

MANDATORY COMPLIANCE — DO NOT SKIP

When the user explicitly invokes /octo:schedule, you MUST use the scheduler command paths below. You are PROHIBITED from inventing job state, editing scheduler files by hand, or bypassing the dashboard/wizard flow.

---

Step 0: Parse Intent First

User says	Action
No args, "show jobs", "status", "what's scheduled", "list"	Dashboard (Step 1A)
Describes a new job, "add", "create", "schedule a...", any time/frequency reference	Wizard (Step 1B)
"remove", "delete" + job name/id	Run remove <id> directly
"enable", "turn on" + job reference	Run enable <id>
"disable", "pause", "turn off" + job reference	Run disable <id>
"logs", "what happened", "last run"	Run logs [id] + summarize
Wants to change schedule/budget/prompt on existing job	Modify (Step 1C)