openai / openai/codex

# Codex Browser Connection Issue Report

Open
#46,180 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app browser bug connectivity windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What version of the Codex App are you using (From “About Codex” dialog)?

Powered by Codex & OWL 版本 26.908.70816

What subscription do you have?

Plus

What platform is your computer?

No response

What issue are you seeing?

Codex 浏览器连接故障反馈

环境与复现

  • Windows 11 家庭中文版(用户提供)。
  • 本地日志中的 Codex 安装版本:26.908.9136.0,WindowsApps 打包安装;仅凭此路径不能确认最初下载渠道。
  • 设置 → 电脑操控 → Microsoft Edge:用户截图显示扩展已安装,开关开启。
  • 用户已在 Edge 登录 Geeksend,页面为 https://app.geeksend.com/search/customs。
  • 在对话中 @Edge 后,枚举浏览器返回 nodeRepl.fetch request failed,未取得标签页。
  • 重置工具会话及新建对话后仍复现。
  • Chrome 安装入口跳转 Chrome Web Store 后显示 This item is not available

本地日志证据(2026-09-16)

  • Codex 日志多次出现:No ChatGPT browser route is available for browser session …。这些条目属于 browser-use-iab-api,指向内置浏览器路由,不能直接认定为 Edge 扩展故障的根因。
  • 当前分析任务曾出现:Timed out running CDP command "Emulation.setFocusEmulationEnabled" for tab 1
  • 另有 computer-use-app-icons.node 加载失败,错误代码 ERR_DLOPEN_FAILED。该条目属于应用图标模块,与浏览器枚举失败是否相关尚未确认。

请求支持排查

请检查该版本 Windows 浏览器连接服务及 Edge 扩展兼容性,说明 nodeRepl.fetch request failed 的诊断方法及可用修复版本;同时核查 Chrome 扩展安装链接是否有效。

尚未确认根因,未修改安全设置、扩展权限或登录凭据。此报告不包含海关记录、密码或令牌。

What steps can reproduce the bug?

在Codex任务对话框内,输入@Chrome 及相关指令时,Codex一直提示无法连接浏览器

What is the expected behavior?

希望尽快处理解决此问题

Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Windows browser connection failure with the reported @Chrome or @Edge steps and inspect the nodeRepl.fetch request failed logs. Compare the browser-use-iab-api route errors with the Edge extension behavior; done means identifying the responsible component and documenting a confirmed fix or supported version.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.