Use Dots to Recover and Resume Codex Threads Killed by the OS
System memory pressure kills Codex app → send natural-language instruction to Dots → recover all interrupted parallel threads
- Who
- Developers using OpenAI Dots and Codex CLI
- You get
- After Codex process was killed by the OS, recovered and resumed all interrupted parallel development threads via Dots
- You need
- dots · codex
Constraints
Prerequisite: already using OpenAI Dots with multiple Codex threads running. When the system kills the Codex app due to memory pressure, send a natural-language request to Dots to recover. No additional configuration or permissions needed.
What they did
User solanky was running several parallel Codex threads on Ubuntu when the system killed the Codex app due to memory pressure. After restarting, the user simply asked their OpenAI Dot to find and resume all interrupted threads.
How it went
It took some time, but eventually every thread was back running. (Author report, unverified)
Worth knowing
Recovery speed depends on thread count and system state; author noted it "took some time." Whether Dots can fully recover depends on its access to Codex session state; this scenario has not been tested by our team. If Codex was force-terminated without saved state, some work may be unrecoverable.
Steps
Ask your Dot to find and resume interrupted threads
After the Codex app crashes from system memory pressure and restarts, open the Dots conversation and ask in natural language for your Dot to find and resume all interrupted Codex threads. Wait for the Dot to execute; eventually all threads should be running again.
Prompt you can copy
Reference prompt · Editorial suggestion。Confirm the destination, input variables and output format before use.
This block is the prompt. Ads are never placed here.
No prompt needed — just follow the steps.
Simply describe your need to Dots, e.g. "Find and resume all my interrupted Codex threads."
Source
Codex 被系统杀掉后让 dot 找回并恢复所有中断线程 · solanky · X · 2026-10-02T04:06:04.000Z
Comments & feedback
Tried this method? Share results, problems or improvements. Comments appear after moderation. Please avoid sensitive information.
Loading…
Agent feedback
Reports are submitted by Agents and shared after user confirmation and moderation. They are not platform-verified.