skills.rest
xaionaro
xaionaroCOMMUNITY
Explore all skills by this author →
GitHub

codex-crash-recovery

Rebuild interrupted Codex sessions from summaries, plans, git, ledgers, and handovers.

Updated May 4, 2026
Search Tags:#codex#resume#error-handling#state-reconstruction#agent-context#crash-recovery#workflow-continuation
One-click install
npx skills add https://github.com/xaionaro/.config-codex --skill codex-crash-recovery
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codex-crash-recovery
Source: https://github.com/xaionaro/.config-codex/tree/main/skills/codex-crash-recovery
Command: npx skills add https://github.com/xaionaro/.config-codex --skill codex-crash-recovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codex crash recovery solves the problem of continuing work after Codex crashes by reconstructing state from summaries, plans, git, ledgers, handovers, and active-mode state to resume tasks without restarting.

Core Features & Use Cases

  • Rebuilds in-progress state from summaries, plans, git, ledgers, and handovers to resume work.
  • Preserves agent context: resume_agent active ids, then issue exactly continue; if lost, prompts replacement.
  • Continue main-thread work from the last in-progress task and inspect dirty files before edits; report resumed/missing agents and current main-thread task.

Quick Start

Reload Codex after a crash and follow this workflow to reconstruct state, resume the main task, and report agent status.

Frequently Asked Questions about codex-crash-recovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resume Codex agent work after a crash without restarting?▼

Codex crash recovery rebuilds interrupted sessions by reconstructing state from summaries, plans, git ledgers, and handovers, issuing a continue step to resume the main task without restarting.

What is agent context preservation during Codex session reconstruction?▼

Agent context preservation resumes active agent IDs and issues exactly a continue command; if agent context is lost, it prompts a replacement to maintain workflow continuation.

How do I check dirty files and main-thread task status after Codex crashes?▼

Crash recovery inspects dirty files before applying edits and surfaces the current main-thread task status, reporting which agents resumed successfully and which are missing.

Can I recover an in-progress Codex task from git ledgers and handover summaries?▼

Yes, crash recovery reconstructs in-progress state from git ledgers, handover documents, plan files, and session summaries to continue the interrupted workflow.

What are the limitations of Codex crash recovery for missing agents?▼

Crash recovery reports missing agents that could not be resumed from reconstructed state, requiring manual replacement prompts when active agent IDs are lost from the session context.

Does Codex crash recovery work with active-mode state and repository data?▼

Yes, crash recovery applies across scenarios where agents were active, reconstructing state from active-mode data, repositories, ledgers, and handovers to guide task continuation.

Related Skills

Explore More Software Engineering Skills→
uoyoCsharpuoyoCsharp
19

mvt-resume

Reconstruct in-progress development state from workspace YAML and plan files.

Community
Advanced
wpfleger96wpfleger96
9

continue-crash

Reconstruct task context from Git state and TODO files after a crash.

Community
Intermediate
kivo360kivo360
1

moai-alfred-session-state

Manage Alfred session state across workflows with session_state.json persistence.

Community
Advanced
sogadaikisogadaiki

resume

Resume a development session by loading restart.md and git status.

Community
Intermediate