Codex Auto Resume

Name: codex-auto-resume-windows
Author: songyb111-gachon

Automatically resume the exact same Codex task on Windows after a usage limit resets.

_{🇰🇷 한국어 README · The app speaks sixteen languages: English · 한국어 · 日本語 · 简体中文 · 繁體中文 · Español · Deutsch · Français · Português (Brasil) · Русский · Italiano · Türkçe · Polski · Українська · Tiếng Việt · Bahasa Indonesia}

Codex stops mid-task and tells you to try again at 6:34 AM. You are asleep at 6:34 AM, and in
the morning the task is exactly where it stopped.

Typical use: the Codex desktop app on Windows, left working overnight or on a long task, hits
a usage limit - the "5-hour limit", as many people call it, or the weekly one - and should carry
on in the same conversation once the limit resets.

Codex Auto Resume waits for the reset time Codex itself reports, not a fixed number of hours,
checks that continuing is genuinely safe, and sends one continuation message to that exact
conversation through the official codex queue command - found by its thread UUID, never
guessed with --last, and never by typing into the Codex window.

It also recovers temporary rate limits (HTTP 429), network failures, timeouts, server errors and
interrupted streams - but only a failure it can name, and only where it is safe to retry.
It deliberately does not retry everything, and it fails closed: when unsure it waits rather
than sends, and never resends a message that may already have been delivered.

This page is the short version. The full guide has everything else: every
setting, the notification, the command line, the safety model and privacy in full.


Recovers	Codex usage limits, and - when Codex records a specific error for them - rate limits (HTTP 429), network failures, timeouts, temporary server errors (5xx) and dropped response streams
Never touches	user cancellation · permission · approval · content policy · invalid requests · context length · permanent authentication failures · anything unclassified
Identity	the exact conversation UUID only — never `--last`, never "the most recent one", never a title or a folder name
Configure it	the Dashboard from the Start Menu, a settings panel inside Codex, or the command line
Languages	English · 한국어 · 日本語 · 简体中文 · 繁體中文 · Español · Deutsch · Français · Português (Brasil) · Русский · Italiano · Türkçe · Polski · Українська · Tiếng Việt · Bahasa Indonesia
Privacy	no telemetry, no analytics, no automatic update check. Setting it up from Codex downloads the release from GitHub, and Check for updates asks GitHub which release is newest, and reads its list of releases on api.github.com for a newer pre-release, only when you press it; Install another version... reads that whole list there when you open it and again when you confirm a version, and downloads only the version you confirmed. The watcher has no network code; the usage check and the resumed turn go to OpenAI through Codex, as Codex's traffic always does

One honest limitation, up front. Codex has to currently have that conversation open for a
recovery to be delivered. If the app restarted since, open the conversation once and recovery
continues on its own. Why.

Install

Windows 10/11. No Python needed. No administrator rights.

It comes in two editions, of which you install one:

Standard is the default, and the one the routes below install. It keeps every one of the
project's standards, every promise on this page among them.
Advanced is the same program plus capabilities that each depart from at least one of those
standards on purpose, and say which. Every one is off until you turn it on in the Dashboard's
Advanced features page, after reading its warnings. To install it instead, take the files
with Advanced in their name, or ask Codex to set up the advanced edition.
docs/EDITIONS.md says what each capability does and risks.
Switching: an update stays in the edition you have. To change edition, install the other one
over it. It says first what the change means, keeps your settings and everything waiting to
resume, and starts every advanced capability off.

From Codex (recommended)

Add the plugin, then ask Codex to set up auto resume.

codex plugin marketplace add songyb111-gachon/codex-auto-resume-windows
codex plugin add codex-auto-resume@codex-auto-resume-windows

The plugin's setup script downloads the matching release from this repository over HTTPS, checks
its SHA-256 against the digest recorded for that version in
scripts/release.json,
and installs it for your Windows account only.

With the setup program

Download CodexAutoResume-Setup-vX.Y.Z.exe from the
latest release (every release
carries one from v0.6.11 on) and double-click it. It carries the release archive below and
runs its Install.cmd, so there is nothing to unzip. It is not code-signed: if Windows says
Windows protected your PC, choose More info, then Run anyway.
docs/VERIFY.md
shows how to check it first.

From the release archive

Download CodexAutoResume-vX.Y.Z-win-x64.zip from the
latest release.
Check it before you extract it, in PowerShell, in the folder you downloaded it to:
```
(Get-FileHash .\CodexAutoResume-vX.Y.Z-win-x64.zip -Algorithm SHA256).Hash
```
The value must match the .sha256 file published beside the archive and the digest for that
version in scripts/release.json.
docs/VERIFY.md has the full check.
Extract it and run Install.cmd.

Either way

Every route ends at the same installation, by default in %USERPROFILE%\.codex-auto-resume.
Running any of them again upgrades or repairs it, and keeps anything already waiting to resume.

First steps

There is nothing to set up: the recommended settings are on from the start.
When a task stops, a notification names it, as a card beside the notification area (or Windows'
own notification where a card must not show). Doing nothing resumes it,
Don't resume cancels only that one, and Open Dashboard shows what is waiting.
The notification-area icon shows what the watcher is doing; click it to see what is waiting or
to pause recovery.
Change anything from Start Menu → Codex Auto Resume, or just ask Codex: "show auto resume
status", "show pending auto resumes", "open auto resume settings", "turn auto resume off".

What it looks like

The status light breathes wherever it is shown - on the card, in the Dashboard, in the panel inside
Codex and on the notification-area icon - and the pictures below breathe with it.

The notification card, as the product draws it:

The notification card in the light theme: Codex Auto Resume with a cyan status light and a Usage limit chip, the task example-project, the line Codex usage limit reached. This task will resume at 08:42., the conversation's exact identifier, and the buttons Don't resume and Open Dashboard

The panel inside Codex - its own page, rendered from the exact resource the plugin serves to
Codex, rather than a photograph of the Codex window around it:

The Codex Auto Resume panel: a status card saying two recoveries are waiting, the two waiting conversations each with an Auto-resume switch, the interface language, the recovered failure categories, Limits and Notifications folded away, the continuation language and message style, and a Preview of the Standard message for a usage limit

The Dashboard from the Start Menu, drawn from synthetic sample data (the conversations in these
pictures are examples, not anybody's work):

The Codex Auto Resume Dashboard overview: automatic recovery on, the watcher running and the Codex engine compatible, two recoveries waiting with the next check in a minute and a half, the last seven days' interruptions, continuations sent, recoveries and success rate, and the four most recently finished recoveries

The Pending page of the Dashboard: two conversations waiting, one for the usage reset and one with a retry scheduled, each with a state chip and an Auto-resume switch, the Why it is waiting checklist for the selected task, and Retry now, Cancel, Timeline, Turn off for this conversation and Cancel all buttons

The Continuation message section of the Dashboard's Settings page: the continuation language, the four message styles with Standard selected, and a Preview of the message sent for a usage limit

The notification-area icon, moving:

The full guide shows every part in every theme and language.

Please read this limitation first

This tool can only auto-resume a thread that the Windows ChatGPT/Codex desktop app currently has
loaded. After the app restarts, a thread is notLoaded, and there is no verified, supported way to
wake an unloaded thread programmatically. Codex may still deliver such a message later, when the
thread next loads. So this tool queues only for a thread it has just confirmed is loaded, and an
unloaded thread is resumed only after you open that conversation in the app yourself. It will
not use GUI automation, will not force the conversation open, and will not queue a message on the
off chance. The full guide has the measurement
behind it.

Safety and privacy

It resumes only the exact conversation that stopped, by its UUID, and only for a failure it can name;
anything unclassified is left alone, and whenever it cannot be sure, it waits rather than sends. It
reads Codex's own state read-only, and never resends a message that may already have been delivered.
The watcher itself has no network code and nothing is sent to this project: the usage check and the
resumed turn go to OpenAI through Codex, and setting it up from Codex downloads the release from
GitHub. PRIVACY.md says what is read, stored and sent, and SECURITY.md
gives the threat model and how to report a vulnerability.

Requirements

Windows 10/11 and the official Windows ChatGPT/Codex desktop app, running.
No Python for either install route; the installation brings its own runtime. Python 3.12 or newer
is needed only to run it from a source checkout.

Uninstall

Run Uninstall.cmd from a release archive, or ask Codex to uninstall auto resume. By default your
settings and pending recoveries are kept, so reinstalling picks them up; Uninstall.cmd -Purge
deletes them too. It removes only what it can prove is its own: directories it can show it owns (by
its provenance marker), and Windows registrations that belong to this installation.

Learn more


The full guide	Everything above in full, and every setting, the notification, the command line, the safety model, privacy and testing.
docs/VERIFY.md	How to check a downloaded archive is the one this project published, and how to rebuild a release.
docs/FEATURE_MATRIX.md	Every capability this product claims, beside the evidence it has actually earned.
docs/PLUGIN.md	The Codex plugin layer: what setup fetches and checks, updates and removal.
docs/COMPARISON.md	Other projects in this space, and what each does better than this one.
docs/ROADMAP.md	Where the project is heading, release by release: a planned direction, not a promise.
docs/EDITIONS.md	The standard and the advanced edition: what each is, what each advanced capability does and risks, and how to choose and switch.
docs/STANDARDS.md	Every rule the product keeps, by id, with how each is held and the tests that hold it.
PRIVACY.md	What is read, what is stored, and what is sent anywhere.
SECURITY.md	The threat model and how to report a vulnerability.
SUPPORT.md	Where to report each kind of problem, and what not to paste into a public issue.
CONTRIBUTING.md	Tests, the release build, and the safety properties a change has to keep.
CHANGELOG.md	What each release changed.
codex-compat-reporter	A separate tool you can run to report how this product behaved on your machine, with your Codex version. It writes one file of counts, states and times - no conversation text, no identifiers, no paths - which you read before you send it. Such a report is counted under Reported, a grade of its own that never raises a version to verified or checked.

Credits and license

Built by songyb111-gachon with the assistance of two AI development tools, OpenAI Codex and
Anthropic Claude Code; CONTRIBUTORS.md has the full breakdown.

MIT. See LICENSE.