Codex 503 biscuit_baker_service_me_circuit_open? Recover Safely

If Codex returns 503 Service Unavailable with biscuit_baker_service_me_circuit_open, check OpenAI status before changing your login, installation, or local task data. When the same error affects new and existing tasks across Codex, ChatGPT, or the API, preserve your local work, stop retrying, wait for the incident to resolve, and then test one new no-tools prompt.

That sequence matched the broad OpenAI incident on July 25, 2026. The official status page reported elevated errors across 12 API components, 15 ChatGPT components, and 4 Codex components from 09:17 to 11:08 UTC. A Codex issue with the exact error collected 42 comments and 19 reactions, while independent reports appeared on X, Reddit, and the OpenAI Developer Community within minutes.

The error name is useful evidence, but it does not reveal OpenAI's internal root cause. Treat it as a service-side incident only when the status and scope checks agree.

The Short Fix

1. Stop submitting the same prompt.

2. Save unsaved editor buffers and inspect the repository with git status --short.

3. Check the official OpenAI status page.

4. If an incident is active or the exact 503 spans multiple Codex surfaces, wait for recovery without signing out, reinstalling, or deleting local state.

5. After status returns to normal, restart Codex once and run a bounded control prompt in a new task.

Use this control prompt:

Reply with CODEX_RECOVERED. Do not call tools or edit files

Expected result: CODEX_RECOVERED returns once without a 503. Then return to the original task, review the current diff, and continue from the last verified step.

What the Error Means

A circuit breaker is a reliability control that stops forwarding calls to a dependency after failures cross a threshold. The code biscuit_baker_service_me_circuit_open therefore suggests that an internal request path was unavailable and its breaker had opened. That is an inference from the error wording, not a published explanation of OpenAI's July 25 root cause.

Three details make the July 25 reports look remote rather than repository-specific:

• users received the same code from https://chatgpt.com/backend-api/codex/responses in different regions;

• authentication, task-list, ChatGPT, and API calls failed during the same window;

• OpenAI's status incident covered Codex, ChatGPT, and APIs and recovered without a repository change.

A July 19 report also captured the same 503 from the remote task list while the local Codex task service continued responding. This matters because a blank sidebar or missing remote task list is not proof that local repository work was deleted.

Prerequisites

Before troubleshooting, record:

• the full error code and failing URL;

• the timestamp and time zone;

• the Codex surface: app, CLI, IDE extension, cloud task, or review;

• the running version;

• whether a new empty task fails too;

• whether ChatGPT or the OpenAI status page shows a wider incident.

Keep API keys, cookies, private prompts, repository names, and full local paths out of public reports.

Step 1: Preserve Local Work

Save unsaved editor buffers. Then run read-only Git checks from the repository root:

git status --short
git diff --stat
git diff --name-only

Expected result: you have an inventory of every tracked change and any visible untracked file. A 503 can interrupt the response after tools already changed files, so review the repository rather than assuming the task either completed or rolled back.

If the task was editing files, do not immediately send the same instruction again. A retry after partial execution can duplicate or conflict with the existing changes. Aident's guide to verifying an AI coding agent's work explains how to separate the diff from the agent's claimed test result.

Step 2: Confirm the Exact Failure Class

This guide applies when the response contains all three signals:

503 Service Unavailable
auth error: 503
auth error code: biscuit_baker_service_me_circuit_open

The auth error label does not prove that your token is wrong. During the July 25 incident, users also reported that OAuth and account pages failed while the broader service status was degraded.

Use a different diagnosis if the code changes:

Expected result: you avoid applying an account, model, or network fix to a broad service incident.

Step 3: Check Scope Before Changing Anything

Open OpenAI status in a normal browser. Record whether Codex, ChatGPT, or APIs show degraded performance.

Then compare one new empty task, without tools or repository access:

Reply with SCOPE_OK. Do not call tools or edit files

Interpret the result:

• If the same 503 appears in the new task and an incident is active, stop and wait.

• If Codex, ChatGPT, and account calls fail together, treat the scope as remote even if the status page has not updated yet.

• If the new task works but only one old thread fails, preserve a written handoff and continue in a new task.

• If status is normal and only one device or network still fails after recovery, continue with the narrow checks in the stream-disconnect guide.

Status pages can lag the first user reports. The July 25 GitHub issue opened at 09:07 UTC, ten minutes before the official investigation timestamp. One failed request is not enough to declare an outage, but matching failures across independent surfaces are stronger evidence than repeated retries on one thread.

Step 4: Back Off Without Destroying State

Once the incident is confirmed:

• stop automatic retry loops and parallel agent launches;

• do not sign out while the authentication path is also returning 503;

• do not delete .codex, local task databases, caches, or chat history;

• do not reinstall repeatedly or switch package managers;

• do not move the live repository to test a remote service error;

• keep the exact error and timestamp for later comparison.

Expected result: local files and diagnostic evidence stay intact while the remote dependency recovers. Waiting is an action here because repeated requests cannot close a provider-side circuit breaker.

Step 5: Verify Recovery Once

When the official incident is resolved, fully quit and reopen the affected Codex surface. Record the running version:

codex --version

Run the no-tools control prompt in a new task:

Reply with CODEX_RECOVERED. Do not call tools or edit files

Success requires:

1. the prompt returns exactly once;

2. no biscuit_baker_service_me_circuit_open error appears;

3. the repository remains unchanged by the control;

4. the original task can be opened or its work can be reconstructed from the repository.

Only then resume the original task. Start with:

Read the current Git diff. Summarize completed work, incomplete work, and the
smallest verification command. Do not edit files yet

Expected result: Codex rebuilds context from durable repository evidence before making another change.

If the Status Is Green but the 503 Persists

Wait a short propagation window and repeat the control once. If the exact error remains on one machine while another trusted device or network works:

1. record codex --version;

2. compare a new empty task on one trusted alternate network;

3. confirm system time is correct;

4. update Codex through the same installer that owns the running binary;

5. re-authenticate only if the error changes to an explicit account or token failure.

Do not combine all five changes at once. One-variable comparisons tell you which boundary changed the result.

If the exact 503 persists across devices while status is green, report the timestamp, request ID, surface, version, region, and sanitized endpoint to OpenAI Support or the matching Codex issue. Avoid uploading complete logs until you have removed credentials and private content.

Common Failure Modes

Why This Recovery Order Works

The order moves from durable local evidence to the broadest shared dependency, then back to one bounded control. Git checks protect the work. Status and cross-surface checks distinguish a provider incident from one repository. Backoff prevents duplicate execution. The no-tools prompt proves that response delivery recovered before tools can change anything else.

This applies the repeatable structure behind Aident's Ollama networking guide: name the exact symptom, test the boundary, state the expected result, cover look-alike failures, and explain why the fix works.

Verify One Read-Only Action After Recovery

After CODEX_RECOVERED succeeds, verify that your agent can discover an external capability without pasting provider credentials into the task. Install or update Aident Loadout with this prompt:

Follow https://aident.ai/SETUP.md

Then run:

aident account auth status
aident vault vault --action status
aident capabilities search \
  --query "find one connected read-only GitHub Action that searches issues" \
  --types '["action"]'

Inspect the exact returned Action before execution:

aident capabilities get --name "<canonical-action-name>"

Success means one live Action schema is returned, zero provider secrets are entered into the chat, and zero repository files change. This does not fix an OpenAI outage. It verifies a measurable external-tool boundary after Codex recovers.

Use Aident Loadout to verify one read-only Action after recovery.

Sources

• Elevated error rates on July 25, 2026, OpenAI Status, resolved July 25, 2026

• Complete service outage with the exact Codex 503, OpenAI Codex issue, opened July 25, 2026

• Auth 503 errors during server degradation, OpenAI Codex issue, opened July 25, 2026

• Remote task list returns the circuit-open code while local task state remains healthy, OpenAI Codex issue, opened July 19, 2026

• Codex stopped working during high demand, OpenAI Developer Community, started July 25, 2026

• Service Unavailable, r/OpenaiCodex, published July 25, 2026

• Stop spamming Codex does not work for you, r/codex, published July 25, 2026

• Elevated ChatGPT errors also affected some Codex requests on July 19, OpenAI Status, published July 2026

• OpenAI Codex CLI getting started, OpenAI Help Center, accessed July 31, 2026

Refresh this guide when OpenAI publishes a root-cause write-up for the July 25 incident, changes Codex error codes, documents a supported diagnostic command, or closes the primary issue with a client-side remedy.