[node_repl][macOS 13 Intel] sandbox-exec fails with unbound variable TIOCSTI
Nobody has claimed this yet.
- 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)?
26.908.40834
What subscription do you have?
codex pro
What platform is your computer?
macOS 13.7.8(Build 22H730),Intel x86_64,MacBookPro14,3
What issue are you seeing?
OpenAI feedback ID:
01a09dae-6b50-7220-9159-a4481f1dba89
Codex 的 Node 运行沙箱与当前 macOS 版本发生兼容错误
无法调起Chrome 浏览器工具
两次连接均在运行环境启动阶段异常退出,错误为:
unbound variable: TIOCSTI,退出码 65。
What steps can reproduce the bug?
-
在 macOS 13.7.8(Intel x86_64,MacBookPro14,3)上启动 Codex Desktop 26.908.40834(Build 8881)。
-
确认 Google Chrome 正在运行,并在“设置 → 计算机使用”中启用 Chrome:
- Chrome 扩展已安装并启用
- Native Messaging Host 存在且校验正常
- 使用的 Chrome 配置文件为 Default
-
新建一个 Codex 会话,通过
@Chrome请求执行任意浏览器操作,例如:
打开一个公共网页并读取页面标题。 -
Codex 调用
mcp__node_repl__js初始化 Browser Runtime。即使只执行最小测试:
nodeRepl.write("alive");
Node 内核也会在用户代码执行前退出。 -
实际错误:
node_repl kernel exited unexpectedlysandbox-exec: <input string>:144:33: unbound variable: | \tTIOCSTIkernel_status: exited(code=65) -
完全退出并重新启动 Codex、重新启动 Chrome、新建会话后,错误仍可稳定复现。
预期结果:
node_repl 应正常执行最小 JavaScript 调用,随后能够连接 Chrome 并操作页面。
实际结果:
node_repl 在 macOS 沙箱初始化阶段退出,导致 Chrome 和内置 Browser 均无法使用。
补充信息:
- 内置 Codex CLI:0.154.0-alpha.6.2
- Chrome:153.0.8010.37
- Chrome 扩展:1.26.901.11451
What is the expected behavior?
修复兼容问题
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing mcp__node_repl__js initialization on macOS 13 Intel with the minimal nodeRepl.write("alive") call, then inspect the sandbox-exec input around line 144 and its TIOCSTI handling. Done means the Node kernel stays running and can connect to Chrome for browser operations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, node.js
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100