Skip to content
CC Switch WikiUnofficial Community Wiki

unexpected status 403 Forbidden: CC Switch local proxy failed - Codex

Quick fix

Disable the cc-switch local proxy or check upstream API access to the codex-auto-review model.

Symptom

Section titled “Symptom”
Error output
Automatic approval review failed: unexpected status 403 Forbidden: CC Switch local proxy failed while handling Codex endpoint /responses. Provider: My Codex; model: codex-auto-review; upstream_status: HTTP 403; cause: This token has no access to model codex-auto-review (request id: 202606031817318386024528268d9d6DAnnzKsr), url: http://127.0.0.1:15721/v1/responses

Cause

Section titled “Cause”

This error occurs when Codex tries to call the automatic review model `codex-auto-review` through the cc-switch local proxy. cc-switch acts as middleware and forwards the request to the upstream provider. The upstream returns HTTP 403 Forbidden and explicitly states that the current token has no access to the `codex-auto-review` model.

This usually means the configured API Key belongs to an account tier that does not support automatic review, or that this specific model is disabled or not included in the plan on the provider side. Because the request must go through the cc-switch local proxy route, the error shows the proxy address (such as http://127.0.0.1:15721...), but the root cause is upstream authentication failure.

Fix

Section titled “Fix”

  1. Confirm whether your API Token supports Codex automatic review. If you are using a personal free quota or a non-subscription account, this internal model may be unavailable. Try an API Key with full access.

    # 在 cc-switch 界面中切换 'Provider' 或重新配置 'API Key'

  2. If token permissions are correct, the issue may be in the cc-switch local proxy routing configuration. Temporarily disable the cc-switch local proxy and connect Codex directly to the upstream to verify whether the proxy is causing a false failure.

    # 在 cc-switch 设置中找到 'Local Proxy' 或 '代理设置'，将其关闭

Affected Versions

Section titled “Affected Versions”
ToolCodex
Version3.16.1
PlatformsmacOS

Source Issues

Section titled “Source Issues”

This page is distilled from 1 real issues

FAQ

Section titled “FAQ”
Why does the error say cc-switch proxy failed instead of directly saying the token is invalid?
cc-switch is a local proxy server that forwards requests. When the upstream returns 403, the proxy returns this error to the client (Codex) and logs the source as a proxy handling failure, but the core cause is that the upstream rejected token access to the specific model.
I changed the API Key but still get the same error. What should I do?
Confirm whether the account type for the new Key includes Codex Auto-Review permissions. Also check that cc-switch is up to date; older proxy logic may be incompatible with newer upstream API versions.
Section titled “Related problems”
502 Bad GatewayCodex/Claude Desktop reports 502 due to CLI proxy conflicts or app-server bypassing proxy. Remove proxy config or downgrade versions to fix.4 issues mergedbash: cannot set terminal process group - cc-switchA known 3.18.0 bug when checking the local proxy environment on Linux. Downgrade below 3.18.0 and configure the proxy in the terminal by hand.5 issues mergedChatGPT will not authenticate even with the global proxy on - cc-switchUpgrade cc-switch to v3.16.4+ and set the proxy address under Settings > Routing > Global outbound proxy, fixing OAuth not going through the proxy.5 issues merged

This is an unofficial community wiki with no affiliation to the cc-switch authors or the project itself. Its content is compiled from the project's public GitHub issues. This site distributes no software.