| name | resume-codex-session |
| description | Recover bounded context from a Codex session for the current workspace and stop after asking whether to continue. Use only when explicitly invoked to resume work from Codex artifacts. |
| disable-model-invocation | true |
| argument-hint | [session-id] |
| allowed-tools | Bash, Read |
Recover context from a Codex session. This is a recovery workflow, not native session restoration.
Use this playbook:
-
Resolve the helper path.
Prefer ${CLAUDE_SKILL_DIR}/../../helpers/ripcord_helper.py when running from the installed plugin or a local checkout used with claude --plugin-dir.
Otherwise find the installed helper with:
find ~/.claude/plugins/cache -path '*ripcord-resume-codex*/helpers/ripcord_helper.py' | head -n 1
If neither path exists, tell the user the plugin helper is unavailable and stop.
-
Build the recovery command for the current workspace.
Base command:
python3 "<helper>" recover --source codex --workspace "$PWD"
If the user supplied a session id via $ARGUMENTS[0], append:
--session-id "$ARGUMENTS[0]"
-
Run the recovery command and inspect the JSON result.
-
If status is not_found, briefly explain that no Codex session matched this workspace and stop.
-
If status is needs_selection, present the ranked candidates with:
session_id, updated_at, preview, reasons, and whether the match is exact.
Ask the user which session id to recover next. Do not guess.
-
If status is ready, compact and present only the bounded recovery fields:
source session metadata, initial user prompt, recent user messages, recent assistant messages, recent tool uses, and any warnings or truncation notes.
-
End by asking whether to continue from that recovered point.
Do not take action yet.
Do not claim the Codex session has been restored natively.
Do not dump the full raw transcript when the helper already returned bounded context.
Note:
When installed as a Claude plugin, this skill may appear under the plugin namespace in addition to the raw skill name.
