openai / openai/codex

Please carefully review the problem I encountered.

Open
#39,747 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app browser bug
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)?

puls

What subscription do you have?

puls

What platform is your computer?

https://github.com/openai/codex/issues/21765

What issue are you seeing?

你的判断是对的——查了一下,这类"浏览器交互服务在读取页面控件时卡死"确实是 Codex 目前存在的一类已知、尚未修复的问题。GitHub 上有一个开放 issue(openai/codex#21765)描述的是同一类症状:插件能完成基础的会话/标签页信息读取,但一到实际抓取页面元素这步就卡住报超时("js execution timed out; kernel reset"),官方目前没有给出修复或 workaround,处于未分诊状态。虽然那个 issue 是 Windows 上、卡在 openTabs 初始化阶段,和你这次卡在小红书创作页控件读取不完全是一回事,但性质上是同一类"浏览器交互服务本身不稳定"的问题,不是你这边配置的锅。

两个可以试的方向,不确定能不能解决,但成本不高:

换成 Codex 内置浏览器而不是 Chrome 插件模式——如果 Codex 设置里有这个切换选项,内置浏览器和 Chrome 扩展走的是两套不同的实现,不一定会复现同样的卡死。
把这次的具体现象反馈给 OpenAI——你这个描述特别有价值(能读 URL/标题,但读登录/发布/创作等控件必超时),比官方 issue 里的描述更精确,值得直接提到 https://github.com/openai/codex/issues 或者应用内反馈里去,可能帮上其他人。

What steps can reproduce the bug?

Sources:

Codex Desktop Chrome plugin hangs during extension backend bootstrap/openTabs on Windows · Issue #21765 · openai/codex
ChatGPT Browser | 内置浏览器、Computer Use 与 UI 调试

What is the expected behavior?

No response

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

The report references openai/codex#21765 and describes a Chrome plugin timeout while reading page controls, but provides no concrete reproduction steps or expected behavior. Start by comparing the reported symptom with the referenced issue; done should include a reproducible scenario and a clearly documented expected result.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.