Skip to content

[Windows][Browser] Browser control fails with API-key authentication #43410

Open

Description

@lyd123qw2008

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

  1. Configure Codex Desktop/CLI with API-key authentication.
  2. Install and enable the OpenAI browser extension in Microsoft Edge.
  3. 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

Activity

  1. added
    bugSomething isn't working
    appIssues related to the Codex desktop app
    windows-osIssues related to Codex on Windows systems
    authIssues related to authentication and accounts
    custom-modelIssues related to custom model providers (including local models)
    app-serverIssues involving app server protocol or interfaces
    on Sep 7, 2026
  2. changed the title [-][Windows][Browser] Browser extension rejects API-key main config with unsupported Codex auth method[/-] [+][Windows][Browser] Browser control fails with API-key authentication[/+] on Sep 7, 2026
  3. DemosHume commented on Sep 10, 2026

    @DemosHume

    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?

  4. lyd123qw2008 commented on Sep 10, 2026

    @lyd123qw2008
    Author

    @DemosHume I am experiencing the same issue as you.

  5. renmengwen commented on Sep 10, 2026

    @renmengwen

    me too,why?

  6. GammaExpansion commented on Sep 10, 2026

    @GammaExpansion

    Me too

  7. wenxuanguo0-debug commented on Sep 10, 2026

    @wenxuanguo0-debug

    me too

  8. nguyenvuh2r commented on Sep 10, 2026

    @nguyenvuh2r

    me too. does anyone know how to fix it?

  9. Miles-FE commented on Sep 10, 2026

    @Miles-FE

    me too

  10. 26 remaining items

  11. wangchun-wapu commented on Sep 17, 2026

    @wangchun-wapu
  12. DemosHume commented on Sep 17, 2026

    @DemosHume

    https://mp.weixin.qq.com/s/xWqcPC0jUg-GGtDTRbZQNw?payreadticket=HMy-Gz8l4t09BEg_s90fDWzEf8x2JEqDhgDprf964B8aMjW3nc1A71jao2AqmdgCFC9aprw

    实际测试方法可以

    这烂钱也吃啊,不过现在官方都恢复了,也算赶不上热乎的

  13. LHLovNN commented on Sep 18, 2026

    @LHLovNN

    https://mp.weixin.qq.com/s/xWqcPC0jUg-GGtDTRbZQNw?payreadticket=HMy-Gz8l4t09BEg_s90fDWzEf8x2JEqDhgDprf964B8aMjW3nc1A71jao2AqmdgCFC9aprw
    实际测试方法可以

    这烂钱也吃啊,不过现在官方都恢复了,也算赶不上热乎的

    修复了吗?昨天更新完试了还是不行啊

  14. wangchun-wapu commented on Sep 18, 2026

    @wangchun-wapu

    https://mp.weixin.qq.com/s/xWqcPC0jUg-GGtDTRbZQNw?payreadticket=HMy-Gz8l4t09BEg_s90fDWzEf8x2JEqDhgDprf964B8aMjW3nc1A71jao2AqmdgCFC9aprw
    实际测试方法可以

    这烂钱也吃啊,不过现在官方都恢复了,也算赶不上热乎的

    没您清高~😂

  15. Sybiil commented on Sep 18, 2026

    @Sybiil

    https://mp.weixin.qq.com/s/xWqcPC0jUg-GGtDTRbZQNw?payreadticket=HMy-Gz8l4t09BEg_s90fDWzEf8x2JEqDhgDprf964B8aMjW3nc1A71jao2AqmdgCFC9aprw
    实际测试方法可以

    这烂钱也吃啊,不过现在官方都恢复了,也算赶不上热乎的

    请问官方修复了吗?我是最新版,还是有这个问题,用不了。
    能讲讲你是怎么处理的吗,谢谢

  16. bradcps commented on Sep 18, 2026

    @bradcps

    Nothing??

  17. LHLovNN commented on Sep 20, 2026

    @LHLovNN

    实测跑通一个间接解决方案:用codex内置浏览器平替,把一些需要登录态的网站在内置浏览器重新登录一遍。

  18. McDonald-is-over commented on Sep 20, 2026

    @McDonald-is-over

    https://mp.weixin.qq.com/s/xWqcPC0jUg-GGtDTRbZQNw?payreadticket=HMy-Gz8l4t09BEg_s90fDWzEf8x2JEqDhgDprf964B8aMjW3nc1A71jao2AqmdgCFC9aprw
    实际测试方法可以

    这烂钱也吃啊,不过现在官方都恢复了,也算赶不上热乎的

    请问官方修复了吗?我是最新版,还是有这个问题,用不了。 能讲讲你是怎么处理的吗,谢谢

    我是用腾讯的Browser Skill替代,不知道这里能不能贴其它的github仓库地址

  19. renmengwen commented on Sep 22, 2026

    @renmengwen

    https://mp.weixin.qq.com/s/xWqcPC0jUg-GGtDTRbZQNw?payreadticket=HMy-Gz8l4t09BEg_s90fDWzEf8x2JEqDhgDprf964B8aMjW3nc1A71jao2AqmdgCFC9aprw
    实际测试方法可以

    这烂钱也吃啊,不过现在官方都恢复了,也算赶不上热乎的

    请问官方修复了吗?我是最新版,还是有这个问题,用不了。 能讲讲你是怎么处理的吗,谢谢

    我是用腾讯的Browser Skill替代,不知道这里能不能贴其它的github仓库地址

    https://github.com/renmengwen/chrome-devtools-control 比内置的chrome插件好用

  20. renmengwen commented on Sep 22, 2026

    @renmengwen

    实测跑通一个间接解决方案:用codex内置浏览器平替,把一些需要登录态的网站在内置浏览器重新登录一遍。

    https://github.com/renmengwen/chrome-devtools-control 比内置的chrome插件好用

  21. renmengwen commented on Sep 22, 2026

    @renmengwen

    https://mp.weixin.qq.com/s/xWqcPC0jUg-GGtDTRbZQNw?payreadticket=HMy-Gz8l4t09BEg_s90fDWzEf8x2JEqDhgDprf964B8aMjW3nc1A71jao2AqmdgCFC9aprw
    实际测试方法可以

    这烂钱也吃啊,不过现在官方都恢复了,也算赶不上热乎的

    请问官方修复了吗?我是最新版,还是有这个问题,用不了。 能讲讲你是怎么处理的吗,谢谢

    https://github.com/renmengwen/chrome-devtools-control 比内置的chrome插件好用

  22. renmengwen commented on Sep 22, 2026

    @renmengwen

    https://mp.weixin.qq.com/s/xWqcPC0jUg-GGtDTRbZQNw?payreadticket=HMy-Gz8l4t09BEg_s90fDWzEf8x2JEqDhgDprf964B8aMjW3nc1A71jao2AqmdgCFC9aprw
    实际测试方法可以

    这烂钱也吃啊,不过现在官方都恢复了,也算赶不上热乎的

    修复了吗?昨天更新完试了还是不行啊

    https://github.com/renmengwen/chrome-devtools-control 比内置的chrome插件好用

  23. renmengwen commented on Sep 22, 2026

    @renmengwen

    大概是平台限制,不要等修复了

    https://github.com/renmengwen/chrome-devtools-control 比内置的chrome插件好用

  24. amd5 commented on Sep 30, 2026

    @amd5

    很久以前就发现这个问题了,至今还没有修复
    并且接管内置浏览器有时候也报这个错误,非常不稳定

  25. callmewenxi commented on Sep 30, 2026

    @callmewenxi

    很久以前就发现这个问题了,至今还没有修复
    并且接管内置浏览器有时候也报这个错误,非常不稳定

    其实这个不是bug,是官方做了限制,要求登录的账户才能用。我主页的补丁已经支持mac和Windows了,可以试试

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appapp-serverIssues involving app server protocol or interfacesauthIssues related to authentication and accountsbrowserbugSomething isn't workingcustom-modelIssues related to custom model providers (including local models)windows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions