Repository navigation
[Windows][Browser] Browser control fails with API-key authentication #43410
Copy link
Copy link
Open
Labels
appIssues related to the Codex desktop appIssues related to the Codex desktop appapp-serverIssues involving app server protocol or interfacesIssues involving app server protocol or interfacesauthIssues related to authentication and accountsIssues related to authentication and accountsbrowserbugSomething isn't workingSomething isn't workingcustom-modelIssues related to custom model providers (including local models)Issues related to custom model providers (including local models)windows-osIssues related to Codex on Windows systemsIssues related to Codex on Windows systems
Description
Summary
On Windows, browser control through the Edge plugin is unavailable when Codex is authenticated with an OpenAI API key. The browser extension and native host connect successfully, but the first browser operation fails with unsupported Codex auth method: apikey.
This issue is intended to clarify whether browser control requires ChatGPT OAuth authentication and whether API-key-authenticated users are expected to be unsupported.
Environment
- Windows
- Codex Desktop:
26.901.6511.0 - Microsoft Edge stable
- OpenAI browser extension:
1.26.901.11451_0 - Codex authentication: API key (
auth_mode=apikey)
Steps to reproduce
- Configure Codex Desktop/CLI with API-key authentication.
- Install and enable the OpenAI browser extension in Microsoft Edge.
- Start browser control and list the user's open tabs.
Actual behavior
The extension/native-host diagnostics pass, but the browser operation fails:
edge.user.openTabs()
unsupported Codex auth method: apikey
Verified locally:
- Edge is running.
- The extension is installed and enabled.
- The native messaging host manifest is present and valid for Edge.
- The browser runtime can select the Edge extension browser.
No token values or private credentials are included.
Expected behavior
- If API-key authentication is not supported for browser control, show a clear user-facing message and document the requirement for ChatGPT OAuth login.
- If API-key authentication is supported, browser read/control operations should work without this error.
Reference: https://learn.chatgpt.com/zh-Hans/docs/auth?surface=app
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
appIssues related to the Codex desktop appIssues related to the Codex desktop appapp-serverIssues involving app server protocol or interfacesIssues involving app server protocol or interfacesauthIssues related to authentication and accountsIssues related to authentication and accountsbrowserbugSomething isn't workingSomething isn't workingcustom-modelIssues related to custom model providers (including local models)Issues related to custom model providers (including local models)windows-osIssues related to Codex on Windows systemsIssues related to Codex on Windows systems
Activity
[-][Windows][Browser] Browser extension rejects API-key main config with unsupported Codex auth method[/-][+][Windows][Browser] Browser control fails with API-key authentication[/+]DemosHume commentedon Sep 10, 2026
Codex Desktop was able to connect to Chrome normally the previous day, but it suddenly stopped working afterward.
I did not intentionally update Codex, but the current version is:
26.903.61454
Both Chrome and Edge now fail to connect and return:
unsupported Codex auth method: apikey
Is this a known issue? How can I restore the browser connection?
lyd123qw2008 commentedon Sep 10, 2026
@DemosHume I am experiencing the same issue as you.
renmengwen commentedon Sep 10, 2026
me too,why?
GammaExpansion commentedon Sep 10, 2026
Me too
wenxuanguo0-debug commentedon Sep 10, 2026
me too
nguyenvuh2r commentedon Sep 10, 2026
me too. does anyone know how to fix it?
Miles-FE commentedon Sep 10, 2026
me too
26 remaining items
wangchun-wapu commentedon Sep 17, 2026
https://mp.weixin.qq.com/s/xWqcPC0jUg-GGtDTRbZQNw?payreadticket=HMy-Gz8l4t09BEg_s90fDWzEf8x2JEqDhgDprf964B8aMjW3nc1A71jao2AqmdgCFC9aprw
实际测试方法可以
DemosHume commentedon Sep 17, 2026
这烂钱也吃啊,不过现在官方都恢复了,也算赶不上热乎的
LHLovNN commentedon Sep 18, 2026
修复了吗?昨天更新完试了还是不行啊
wangchun-wapu commentedon Sep 18, 2026
没您清高~😂
Sybiil commentedon Sep 18, 2026
请问官方修复了吗?我是最新版,还是有这个问题,用不了。
能讲讲你是怎么处理的吗,谢谢
bradcps commentedon Sep 18, 2026
Nothing??
LHLovNN commentedon Sep 20, 2026
实测跑通一个间接解决方案:用codex内置浏览器平替,把一些需要登录态的网站在内置浏览器重新登录一遍。
McDonald-is-over commentedon Sep 20, 2026
我是用腾讯的Browser Skill替代,不知道这里能不能贴其它的github仓库地址
renmengwen commentedon Sep 22, 2026
https://github.com/renmengwen/chrome-devtools-control 比内置的chrome插件好用
renmengwen commentedon Sep 22, 2026
https://github.com/renmengwen/chrome-devtools-control 比内置的chrome插件好用
renmengwen commentedon Sep 22, 2026
https://github.com/renmengwen/chrome-devtools-control 比内置的chrome插件好用
renmengwen commentedon Sep 22, 2026
https://github.com/renmengwen/chrome-devtools-control 比内置的chrome插件好用
renmengwen commentedon Sep 22, 2026
https://github.com/renmengwen/chrome-devtools-control 比内置的chrome插件好用
amd5 commentedon Sep 30, 2026
很久以前就发现这个问题了,至今还没有修复
并且接管内置浏览器有时候也报这个错误,非常不稳定
callmewenxi commentedon Sep 30, 2026
其实这个不是bug,是官方做了限制,要求登录的账户才能用。我主页的补丁已经支持mac和Windows了,可以试试