Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
You can pick up work after a restart, but the recovery steps depend on which product surface you were using. Claude Code’s CLI can continue the latest conversation in the current directory or resume one by session ID. Codex app-server resumes a thread using its saved thread ID. An application using the OpenAI Agents API retrieves its session and may need to resolve pending actions before continuing.
Choose the recovery method for the surface you used
| Surface | Identifier or selection | Recovery method |
|---|---|---|
| Claude Code CLI | Latest conversation in the current directory, or a specific session ID | claude --continue or claude --resume <session-id> |
| Codex app-server | Saved thread ID returned when starting the thread | Initialize app-server, then send thread/resume with that ID |
| OpenAI Agents API application | Saved session ID | Retrieve the session, inspect status and required actions, then continue according to its state |
These are distinct workflows; the documented procedures do not establish one universal resume command shared by all three surfaces.
Resume a Claude Code CLI conversation
Run the command from the project or current directory associated with the conversation. The Claude Code CLI reference documents two options:
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesclaude --continue, or its short formclaude -c, loads the most recent conversation in the current directory.claude --resume <session-id>, orclaude -r <session-id>, resumes a particular session when you have its ID.
Use the first when you want the latest conversation for that directory; use the second when you need to select a known session. These options load or continue a conversation. The CLI reference does not promise restoration of every detail of the previous terminal or process state.
Resume a Codex app-server thread
This procedure applies to the Codex app-server protocol, not necessarily to another Codex surface such as a command-line workflow. Save the thread ID returned by thread/start somewhere your application can retrieve it after a restart.
- Start the new app-server process and initialize it.
- Load the saved thread ID for the conversation you want to continue.
- Send
thread/resumewith that thread ID.
OpenAI’s Codex app-server sign-in example demonstrates this protocol pattern. Without the saved thread ID, this documented resume procedure cannot select the existing thread.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Recover an OpenAI Agents API session
An Agents API session is an application-level workflow, separate from Codex app-server. Keep the session ID with your application’s conversation record so the application can retrieve the session after a restart or stream disconnect. OpenAI’s session guide and session management guide describe continuing and managing sessions.
- Retrieve the session using its saved session ID.
- Inspect the session status and any
required_actions. - Handle each required action before following the events to determine the turn outcome.
- Continue based on that outcome. If the session itself has failed, create a new session and provide the inputs that are still needed.
A failed turn does not necessarily mean the session has failed. The Agents API errors and recovery guide distinguishes session recovery from creating a new session after session failure.
Quick Recap
Best Value
Rank #3
If you cannot resume
- Claude Code: Check that you are in the directory associated with the conversation. If you have the session ID, try
claude --resume <session-id>rather than selecting the latest conversation. - Codex app-server: Check that your application persisted the thread ID returned by
thread/start, then pass that ID tothread/resumeafter initializing the server. - Agents API: Retrieve the session and inspect its status and required actions. If the session is failed, create a new one with the still-needed inputs; do not treat a failed turn by itself as proof that the session failed.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
