Supervise
A tiny background utility starts and watches the official Codex app-server.
A tiny continuity layer that keeps Codex threads alive while the desktop app updates, quits, or restarts.
Open source · MIT · No desktop patching
Codex normally launches the process that owns your threads. When the window exits, that backend exits with it. Continuity moves one process boundary—and changes the failure mode.
A tiny background utility starts and watches the official Codex app-server.
The desktop talks to that backend over a loopback WebSocket instead of owning it.
Microsoft Store can replace the window while the externally supervised backend keeps running.
The bootstrapper verifies the release checksum, runs an isolated reconnect check, installs per-user, and starts the supervisor. It never restarts the desktop app.
Read the full install guidePS› $i="$env:TEMP\codex-continuity-install.ps1"; curl.exe -fsSL https://github.com/YesterdaysLemon/codex-continuity/releases/latest/download/install.ps1 -o $i; powershell.exe -NoProfile -ExecutionPolicy Bypass -File $i -StartNowAgents and automation can read a mutation-free JSON plan before downloading anything. The machine-readable guide lives at /llms.txt.
powershell.exe -NoProfile -ExecutionPolicy Bypass -File $i -Plan -JsonThis page and the first public release were built inside the same Codex thread after its desktop window restarted.
Verified migration run · Windows 11 · August 20, 2026
Codex Continuity relies on experimental app-server transport and undocumented desktop environment hooks. A future Codex release may change them. The utility is deliberately small, fail-closed, and removable with one command.