[Bug] 使用 ChatGPT /api/auth/session 导入账号,报错401

[Pollozic]

版本

v0.3.7

影响范围

Desktop

环境信息

windows11桌面端

复现步骤

通过/api/auth/session 导入账号，刷新显示可用，通过codex桌面端无法使用，日志报错401

预期结果

之前可以正常使用

实际结果

脱敏日志 / 截图

time=2026/05/29 14:45:25
stage=request_log_fallback_non_success
path=/v1/responses
method=POST
status=401
cf_ray=-
kind=-
compression=none
retry_without_compression=no
account=user-xxxxxxxxxxxx::cgpt=xxxxxxxxxxxxxxxx
key=gk_xxxxxxxxxxxxx
message=Unauthorized [request_id=xxxxxxxxxxxxxxxx, cf_ray=xxxxxxxxxx-LAX]

xxxx为脱敏处理

提交检查

• 我已确认内容不包含敏感凭据
• 我已阅读仓库的 SECURITY.md

[bimapopo345]

yeah, i have the same problem, but i found the slight information abou that issue, Open Ai today might be Change his Api Version to codex, we have to wait 1 day

[qxcnm]

yeah, i have the same problem, but i found the slight information abou that issue, Open Ai today might be Change his Api Version to codex, we have to wait 1 day

指的是把聊天接口改到codex的api 路由上吗？还是说出现了一个新的接口？
Is this referring to changing the chat interface to the codex api route? Or does a new interface appear?

[bimapopo345]

yeah, i have the same problem, but i found the slight information abou that issue, Open Ai today might be Change his Api Version to codex, we have to wait 1 day

Does it mean to switch the chat interface to the Codex API route? Or has a new interface appeared? Is this referring to changing the chat interface to the codex api route? Or does a new interface appear?

This is not a CM bug — it's a global OpenAI outage happening right now (May 29-30, 2026).

Evidence:

Multiple news sources confirming widespread outage: ChatGPT, API, DALL-E, Codex, Sora, and login all affected simultaneously
OpenAI Down: ChatGPT, API, DALL-E, Sora and Login Hit by Widespread Outage on May 29
ChatGPT Down today - Economic Times
DownDetector OpenAI
OpenAI Status Page
I'm experiencing the same 401 on all 22 accounts in my CM setup (v0.3.4, Windows 11). The 401 is coming from OpenAI's upstream, not from CM's gateway validation.

The cf_ray in your log (a0320cfe0d4af7b5-LAX) confirms the request reached Cloudflare/OpenAI and was rejected server-side.

Workaround: Just wait for OpenAI to recover. No CM config change needed. Once their services are back, CM will work again automatically.

Re: API switching issue — that might be a separate bug worth tracking, but the 401 itself is definitely upstream.

Link GitHub reference:

CM Issue #293: #293
OpenAI Codex 401: openai/codex#2896
OpenAI Codex 401 (newer): openai/codex#12764
Token refresh 401: openai/codex#6036