Delegate stuck Claude Code problems to Codex CLI for second-opinion resolution.
npx skills add https://github.com/michaelkd01/dic-skills --skill codex-rescue
Please help me install this Agent Skill. Skill: codex-rescue Source: https://github.com/michaelkd01/dic-skills/tree/main/codex-rescue Command: npx skills add https://github.com/michaelkd01/dic-skills --skill codex-rescue
Claude Code sessions sometimes loop on the same issue, exhaust their iteration quota, or reveal blind spots that stall progress in manual workflows. This guide explains how to identify those trapped states, why rescue is a second-opinion intervention, and how to safely hand off the specific failing piece to Codex while keeping the manual session in control.
/codex:rescue with --background, --wait, --resume, --fresh, --model, and --effort to describe the precise failure and request the right level of investigation or fix./codex:status, /codex:result, and /codex:cancel, remembering that the rescue runs on the same checkout and that you should review Codex output before resuming Claude Code..codex/config.toml (or user defaults) to preselect models, effort levels, and behavior.Describe the stuck Claude Code work to Codex and request a rescue with the appropriate flags so it can investigate or continue while you monitor the output before resuming the session.
High-intent search queries and answers about installing and using this skill.
To get a second opinion for a stuck Claude Code session, use the /codex:rescue command to delegate the failing piece to Codex. Codex investigates or continues the work while you monitor the output before resuming your session.
The three-strike rule is a use-case pattern for manual Claude Code workflows: after repeated failures or exhausted iterations, you escalate the specific failing piece to Codex as a second-opinion intervention rather than continuing to loop.
Yes, you need the Codex CLI installed and an authenticated plugin to execute rescue jobs. The rescue runs on the same checkout, so you must review Codex output before resuming your Claude Code session.
To monitor a background rescue job, use the /codex:status command to track its lifecycle and /codex:result to retrieve the output. Use /codex:cancel to stop a job if needed.
Yes, you can set project-level defaults in the .codex/config.toml file or user defaults to preselect models, effort levels, and behavior. You can also override these per rescue using the --model and --effort flags.
You should not use a model handoff for simple tasks that have not hit repeated failures or exhausted iteration quotas. Rescue is a targeted second-opinion intervention for stalled manual workflows needing investigation before executing fixes.
julianobarbosaManage iTerm2 and tmux workflows with native -CC integration.
johnlindquistCoordinate parallel consultations across Claude, Codex, and Gemini for structured comparison.
ricableInitialize Claude Flow for both Claude Code and OpenAI Codex environments.
Jia-Hong-PengWrap the OpenAI Codex CLI for automated code review and Q&A.