ChatGPT sign-in fails with HTTP 403 on Windows — OpenClaw 2026.10.7

What are you trying to do?

Connect my ChatGPT Plus account to OpenClaw, then use it with my existing Telegram and Feishu bots.

Environment

- OpenClaw: 2026.10.7 (157d8c2)
- OS: Windows, running locally on my laptop
- I migrated from an older computer.
- I am located in a country/region not supported by OpenAI and use a proxy.

What happened?

1. “Codex login (browser)” showed authentication successful in the browser, but OpenClaw reported:
   Country, region, or territory not supported
   OpenAI Codex token exchange failed (HTTP 403).

2. “Sign in with ChatGPT (Beta)” also failed:
   openai-token-sharing:
   ChatGPT authentication request failed (HTTP 403).
   Retry sign-in later.

3. “openclaw models status” showed no OAuth/token credentials and:
   No enabled plugin owns agent harness "codex".

4. The bundled openai provider plugin is enabled.

What have you tried?

  • Tried both “Codex login (browser)” and “Sign in with ChatGPT (Beta)”.
  • The Codex browser flow displayed success, but OpenClaw reported a token exchange failure (HTTP 403).
  • The ChatGPT Beta flow displayed “Authentication failed”.
  • Ran openclaw models status: no OAuth/token credentials were available.
  • Checked openclaw plugins info openai: the bundled OpenAI provider plugin is enabled.

Safe diagnostics

OpenClaw version: 2026.10.7 (157d8c2)
Running locally on Windows.

Codex login error:
Country, region, or territory not supported.
OpenAI Codex token exchange failed (HTTP 403).

ChatGPT Beta login error:
openai-token-sharing: ChatGPT authentication request failed (HTTP 403). Retry sign-in later.

Models status:
OAuth/token status: none
No enabled plugin owns agent harness “codex”.

I am located in a region not supported by OpenAI and use a proxy. Is the regional restriction sufficient to explain these failures, or is there also a separate runtime/plugin configuration problem?

Questions:
Is this expected because of the regional restriction, or is there also a separate plugin/configuration issue?
Which diagnostic command should I run to investigate without exposing credentials?

Hi Sung, welcome to our community!

The regional restriction could explain the 403, especially since the token exchange explicitly reports an unsupported country or region. The browser showing “success” doesn’t necessarily mean the token exchange back to OpenClaw completed.

The No enabled plugin owns agent harness "codex" message looks like a separate configuration issue. The OpenAI provider being enabled doesn’t by itself establish that the Codex harness plugin is installed and enabled.

Could you check these locally?

openclaw plugins info codex
openclaw models auth list --provider openai

Please share only the plugin’s installed/enabled status and whether an OAuth profile exists. Redact account identifiers and don’t post tokens, callback URLs or complete config files.

If your location is unsupported, the supported route is to use the service from a supported location or choose a provider available in your region. If OpenAI is reporting the wrong location, their support team can investigate.