How this command is triggered — by the user, by Claude, or both
Slash command
/otto:resume <action> [step_index]This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
Resume a paused otto-engine execution, handing control back from the interactive OTTO session to the engine's executor. ## Arguments - `action` (required): One of: - `retry` — Re-execute the step that was paused (useful after fixing an element or page state) - `continue` — Skip the paused step and advance to the next one - `abort` — Terminate the execution entirely - `jump <step_index>` — Jump to a specific step index (0-based) - If the argument is `jump`, the next word is the step index (e.g., `/resume jump 5`). ## Steps 1. **Validate there's an active attached session.** Look...
Resume a paused otto-engine execution, handing control back from the interactive OTTO session to the engine's executor.
action (required): One of:
retry — Re-execute the step that was paused (useful after fixing an element or page state)continue — Skip the paused step and advance to the next oneabort — Terminate the execution entirelyjump <step_index> — Jump to a specific step index (0-based)If the argument is jump, the next word is the step index (e.g., /resume jump 5).
Validate there's an active attached session. Look through active sessions for one where owns_browser is False. If none found, tell the user: "No attached session found. Use /attach first."
Determine the otto-engine base URL.
Default: http://localhost:8000. Check if the environment variable OTTO_ENGINE_URL is set and use that instead.
Parse the action from the user's argument:
jump, extract the step index from the next word.retry, continue, abort, jump.Send the resume instruction to otto-engine:
POST {base_url}/api/executions/{execution_id}/resume
Content-Type: application/json
{"action": "<action>", "step_index": <index_or_null>}
Wait for the 200 acknowledgment.
Detach the session. Call close_session with the attached session's ID. This drops the CDP connection without killing Chrome — the engine takes back control.
Report the result:
retry: "The engine will re-execute the paused step."continue: "The engine will skip to the next step."abort: "The engine will terminate the execution."jump: "The engine will jump to step {step_index}."Use httpx for the HTTP call. Handle errors gracefully — if the resume call fails (404, 422), explain what went wrong.
npx claudepluginhub stemado/otto --plugin otto/resumeResumes a previously-running Claude agent by ID, picking up its transcript and continuing the interrupted task where it left off.
/resumeLists active task orchestrations with progress and resumes specific ones via --date --project or --latest. Shows tasks in progress, blocked/next tasks, git activity, and quick actions.
/resumeLists active task orchestrations with progress and resumes specific ones via --date --project or --latest. Shows tasks in progress, blocked/next tasks, git activity, and quick actions.
/resumeResumes a babysitter workflow run by run ID or discovers/suggests incomplete runs based on status, inputs, and process.
/resumeResumes a long-running DMP workflow (engagement, campaign-plan, content-engine, etc.) that was interrupted, reloading saved artifacts and continuing from the next step.
/resumeResumes interrupted Lisa specification interviews: scans .claude/lisa-*.md state files, lists for user selection, continues questions via AskUserQuestion, updates draft spec, finalizes MD/JSON docs.