Codex CLI 429 Auto Continue

Codex CLI 429 Auto Continue starts a 继续 turn in the same thread after Codex exhausts its HTTP 429 retries. It waits 15, 30, and 60 seconds between attempts and stops after three automatic continuations.

The project provides two commands:

• codex-429-sidecar keeps the standard Codex terminal interface and runs the continuation policy in the background.
• codex-429-guardian runs one foreground App Server thread and prints the response directly.

The repository also contains a hook component for Codex hosts that provide structured failed-turn data.

Requirements

• Node.js 22.4 or newer
• Codex CLI
• PowerShell 7 when using a custom .ps1 launcher

Install

Install the package globally from npm:

npm install --global codex-cli-429-auto-continue

This installs the codex-429-sidecar and codex-429-guardian commands.

Sidecar

Use the Sidecar for normal interactive Codex sessions:

codex-429-sidecar
codex-429-sidecar -C <project-directory>
codex-429-sidecar -C <project-directory> "task description"
codex-429-sidecar resume --last

All regular Codex arguments pass through to the terminal interface. Non-interactive commands such as exec, review, plugin, and doctor run directly without starting the Sidecar.

Sidecar options must appear before a literal --:

| Option | Description | | --- | --- | | --sidecar-data-dir PATH | Set the retry-state directory | | --sidecar-launcher PATH | Use a custom Codex launcher | | --sidecar-disable | Run Codex directly for this invocation | | --sidecar-help | Show command help |

Set CODEX_429_SIDECAR_DISABLE=1 to bypass the Sidecar for every invocation in the current environment.

Guardian

Use the Guardian when the full terminal interface is unnecessary:

codex-429-guardian --cwd <project-directory> -- "task description"
codex-429-guardian --interactive --cwd <project-directory>

The Guardian owns one App Server thread. Exit code 75 means the current retry sequence reached the three-continuation limit.

How it works

1. The Sidecar starts a Codex App Server on an automatically assigned loopback port.
2. It connects the Codex terminal and a policy client with a process-local capability token.
3. The policy client joins the thread created by the terminal.
4. A structured failed turn with an exhausted-retry HTTP 429 starts 继续 on the same thread after the configured delay.
5. A newer user turn cancels pending work. The fourth matching failure stops the retry sequence.

Custom launcher

Pass a launcher file when Codex must start through a local wrapper:

codex-429-sidecar --sidecar-launcher .\custom-codex-launcher.ps1 -C <project-directory>
codex-429-guardian --codex-launcher .\custom-codex-launcher.ps1 --cwd <project-directory> -- "task description"

You can also set a shared launcher:

$env:CODEX_429_LAUNCHER = (Resolve-Path .\custom-codex-launcher.ps1).Path
codex-429-sidecar

PowerShell scripts run through pwsh. Windows also accepts .exe and .com launchers. Other platforms accept executable files. The project does not run .cmd or .bat launchers.

State

The Sidecar stores retry state in <CODEX_HOME>/429-sidecar. Set CODEX_429_SIDECAR_DATA or use --sidecar-data-dir to choose another path.

The Guardian stores retry state in <CODEX_HOME>/429-guardian. Set CODEX_429_GUARDIAN_DATA or use --data-dir to choose another path.

Disable or remove

Use the normal codex command or pass --sidecar-disable when automatic continuation is not needed.

Remove the installed commands with:

npm uninstall --global codex-cli-429-auto-continue