From ouroboros
Lists in-flight Ouroboros sessions from EventStore and provides re-attach/monitor commands after MCP disconnect. Triggered by lost execution keywords.
npx claudepluginhub q00/ouroboros --plugin ouroborosThis skill uses the workspace's default tool permissions.
Recover in-flight Ouroboros sessions after an unexpected MCP server disconnect.
Checks Ouroboros execution session status and measures goal drift from seed objectives. Useful for monitoring progress and detecting deviations via /status.
Manages Maestro orchestration session state: creation, updates, tracking, resumption, and archiving via MCP tools, file edits, or scripts.
Initializes or resumes work sessions by loading OPERATOR.md and SHELL.md context, reading runtime.json state, handling locks, interrupted recoveries, and unclean shutdowns. Invoke at session start.
Share bugs, ideas, or general feedback.
Recover in-flight Ouroboros sessions after an unexpected MCP server disconnect.
Claude Code reserves /resume for its built-in session picker. This skill
intentionally uses resume-session so it does not shadow that native command.
ooo resume-session
ooo resume-session --all
/ouroboros:resume-session
Trigger keywords: "in-flight Ouroboros sessions", "re-attach", "mcp disconnected", "lost Ouroboros execution"
ooo resume-session reads the EventStore directly (no MCP server required) and lists
every session that is still in a running or paused state. The command is
strictly read-only — it never creates the data directory, never writes
schema, and never appends events. Its job is to surface the identifiers you
need to re-attach.
ooo resume-session shows the 20 most recent active sessions.ooo resume-session --all shows every active session.When the user invokes this skill:
Run the CLI command:
ouroboros resume
This reads ~/.ouroboros/ouroboros.db directly — the MCP server does not
need to be running.
If sessions are listed, enter the number of the session you want to work
with. The command prints both the session_id and the exec_id, along
with the two re-attach paths.
Pick the right re-attach path:
Inspect only (read-only interactive monitor):
ouroboros tui monitor
Launches the TUI and lets you pick the session to inspect. The
ouroboros status execution <exec_id> command is registered but its
handler is still a placeholder in src/ouroboros/cli/commands/status.py
(it only prints "Would show details for execution: …"), so it is
intentionally not surfaced here. Follow-up tracked as a separate issue.
Resume execution (requires the original seed file):
ouroboros run workflow --orchestrator --resume <session_id> <seed.yaml>
| Code | Meaning |
|---|---|
0 | Success — sessions listed, or no sessions found |
1 | Invalid user selection (non-numeric or out-of-range) |
2 | EventStore exists but could not be opened or read |
If the command reports "No in-flight sessions found", the execution either completed, failed, was cancelled, or the EventStore has never been created. To browse historical sessions interactively, use the TUI monitor:
ouroboros tui monitor
User: ooo resume-session
┌─────────────────────── In-Flight Sessions ───────────────────────┐
│ # Session ID Execution ID Status Started │
│ 1 sess-abc123 exec-xyz789 running 2026-04-15 │
└───────────────────────────────────────────────────────────────────┘
Enter number to re-attach (1-1), or 'q' to quit: 1
╭─ Re-attach ────────────────────────────────────────────────────────────────╮
│ Session ID: sess-abc123 │
│ Execution ID: exec-xyz789 │
│ │
│ Inspect (read-only interactive monitor): │
│ ouroboros tui monitor │
│ │
│ Resume execution (requires the original seed file): │
│ ouroboros run workflow --orchestrator --resume sess-abc123 seed-001 │
╰────────────────────────────────────────────────────────────────────────────╯
After you have the identifiers:
ouroboros tui monitor — launch the TUI and pick the session to inspectouroboros run workflow --orchestrator --resume <session_id> <seed.yaml> — resume executionooo evaluate — evaluate results once the execution completesooo cancel execution <exec_id> — cancel if the session is stuck