429too many requests, Codex

Quick fix

A 429 occurs when using a third-party Responses API, but the original post does not provide a verifiable solution.

Symptom

Error outputCopy

codex客户端报429too many requests

English translation

The codex client reports 429too many requests.

Cause

The report states that, after the user followed the official steps to sign in to a GPT account, enabled enhanced features, and switched to a third-party Responses API without enabling a local proxy, the chat model failed after restarting the CLI or client. The CLI also showed the variant `We're currently experiencing high demand, which may cause temporary error`.

The issue was closed, but the original post does not include a maintainer-confirmed root cause, fixed version, or successful solution. Therefore, it cannot confirm whether the 429 was caused by cc-switch, the third-party relay service, or another component.

Fix

1. 1

   The original post does not provide a verifiable solution; refer to later discussion in this Issue or provide additional reproduction details.

Affected Versions

ToolCodex

Version3.16.1（报告版本；是否为受影响版本未确认）

PlatformsmacOS

Source Issues

This page is distilled from 1 real issues

• #3746Codex增强功能无法使用第三方API中转服务，cli中报We're currently experiencing high demand, which may cause temporary error，codex客户端报429too many requests

FAQ

(No FAQ yet)

Related problems

stream disconnected before completionUpdate CC Switch to 4.0 or the latest version and retry; the maintainer recommended this, but the original issue did not confirm a resolution.1 issues mergedProxy not working, constant reconnect after entering a question; CodexThe separate proxy feature in cc-switch was removed; set the proxy via $env:http_proxy in PowerShell, then run Codex.1 issues mergedToggling proxy or switching third-party accounts invalidates official Codex sign-inNo verifiable solution was provided; the issue was suggested for further reporting to cc-switch-cli.1 issues merged