resume-session · git:20261016.bd80495 · 2026-10-16 · sha256 9b57608c719dbf1a

resume-session git:20261016.bd80495A

Immutable. This exact content never changes and is served at /api/v1/blob/9b57608c719dbf1a.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_kc3adujikvyfoisc/9b57608c719dbf1a6b63e457eeaa04bd9d26606c5b1ead91ec26cc4544320807.json

Then /plugin install resume-session@markdownregistry-kc3adujikvyfoisc in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: resume-session
description: "List in-flight Ouroboros sessions and show the commands needed to re-attach after MCP disconnect"
---

# /ouroboros:resume-session

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.

## Usage

```
ooo resume-session
ooo resume-session --all
/ouroboros:resume-session
```

**Trigger keywords:** "in-flight Ouroboros sessions", "re-attach", "mcp disconnected", "lost Ouroboros execution"

## How It Works

`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.

## Instructions

When the user invokes this skill:

1. Run the CLI command:

   ```
   ouroboros resume --list
   ```

   This reads the configured runtime EventStore directly; the MCP server does
   **not** need to be running. `--list` prints the table and exits without the
   interactive prompt, which aborts when no terminal is attached. Add `--all`
   to show every active session.

2. If sessions are listed, show the table and ask the user which session to
   work with (active runtime's `ask_user` capability). Each row carries the
   `session_id`, `exec_id`, and seed id used by the re-attach paths below.

3. Pick the right re-attach path:

   - **Inspect persisted events** (read-only):

     ```
     ouroboros status execution <exec_id> --events
     ```

     Reads the configured EventStore without starting an MCP server.

   - **Inspect interactively** (read-only monitor):

     ```
     ouroboros tui monitor
     ```

     Launches the TUI and lets you pick the session to inspect.

   - **Resume execution** (requires the original seed file):

     ```
     ouroboros run workflow --orchestrator --resume <session_id> <seed.yaml>
     ```

## Exit codes

| Code | Meaning |
|------|---------|
| `0`  | Success — sessions listed, or no sessions found |
| `1`  | Invalid selection at the interactive prompt (not used with `--list`) |
| `2`  | EventStore exists but could not be opened or read |

## Fallback (No sessions found)

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
```

## Example

```
User: ooo resume-session

> ouroboros resume --list

┌─────────────────────── In-Flight Sessions ───────────────────────┐
│  #  Session ID          Execution ID        Status    Started    │
│  1  sess-abc123         exec-xyz789         running   2026-04-15 │
└───────────────────────────────────────────────────────────────────┘

Which session should I re-attach? → sess-abc123

╭─ 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    │
╰────────────────────────────────────────────────────────────────────────────╯
```

## Next Steps

After you have the identifiers:

- `ouroboros tui monitor` — launch the TUI and pick the session to inspect
- `ouroboros run workflow --orchestrator --resume <session_id> <seed.yaml>` — resume execution
- `ooo evaluate` — evaluate results once the execution completes
- `ooo cancel <session_id>` — cancel if the session is stuck

## RFC #1392 State Breadcrumb Footer

Your final response MUST end with exactly one breadcrumb footer line:

```
◆ <current state> → next: <recommended action>
```

Derive `<current state>` from live session state via `ouroboros_session_status` when that MCP projection is available; otherwise derive it from this skill's actual outcome. Never use a linear `Step N of M` footer because Ouroboros is an evolutionary loop. When the next action is genuinely a choice, list 2-3 honest options in the `next:` clause. The breadcrumb line must be the last line of the response.