Codex Tool Recovery Guide

Typical failure pattern:

1. File tools, write tools, or patch tools suddenly become unavailable
2. Codex still responds, but cannot actually write code
3. Planned implementation is interrupted mid-task
4. Repeating the request does not restore tool behavior
5. It looks like a model issue, but it usually is not

First ask Codex to do one explicit check:

1. Confirm whether file tools are currently available
2. Repeat back the currently available tool set
3. If file tools are unavailable, stop planning new implementation details
4. Do not accept "verbal completion" as real code delivery
5. Once tools recover, restart implementation from step one

Codex, first check whether file tools are currently available in this session.

If file tools are available:
1. Restart the implementation from step 1
2. Do not skip edit steps
3. Do not assume earlier draft text was written to disk
4. Re-run editing, verification, and save steps

If file tools are unavailable:
1. Tell me exactly which tools are unavailable
2. Stop expanding the implementation plan
3. Wait for tool recovery, then restart from step 1

This is a toolchain-state problem, not a model-quality problem.

Recommended recovery flow:

1. Confirm tool state first
2. If file tools are back, restart from the original edit path
3. If file tools are still broken, stop producing new implementation drafts
4. After tool recovery, do not continue from the broken midpoint
5. Restart editing, validation, and save steps from the beginning