[Bug]: macOS stdio MCP repeatedly surfaces OpenScreen and accumulates long-lived processes in Codex

未关闭
  • 哪里不对？
#1,488 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
38/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
electron, macos, typescript
领域
audio-video-rtc, desktop

调研方向

Start by locating the stdio MCP entry point and macOS app startup code, then trace how MCP startup affects Electron windows and how client sessions are cleaned up. The report gives no source files or tests, and a single-client reproduction is still needed; first reproduce with the documented Codex configuration and inspect process and window behavior. Done means unrelated Codex use no longer repeatedly surfaces OpenScreen UI or leaves unnecessary MCP processes running.

由索引模型根据 Issue 内容生成。

描述

Search existing issues

  • I searched existing issues. #1137 is related to concurrent CLI processes but describes Chromium profile contention, not this repeated popup/process accumulation symptom.

Describe the bug

After following the documented demo skill setup and registering the installed macOS app as a global Codex stdio MCP server, OpenScreen repeatedly popped up during normal Codex usage, without an explicit recording request at those moments. Multiple long-lived Openscreen mcp processes accumulated in the background.

On November 6, 2026, process inspection found 38 OpenScreen MCP main processes. Their parents were Codex app-server processes (desktop bundled Codex and Homebrew Codex). Some instances had been alive for over a day; others were newly started. During cleanup, 111 OpenScreen app processes including helpers were sent SIGTERM, and a subsequent check found zero remaining.

The user-facing popup symptom and process accumulation are observed. I have not isolated whether the popup is a normal window, Dock activation, or another Electron startup UI, nor whether the instance accumulation is caused by MCP client lifecycle, OpenScreen lifecycle, or their interaction. No claim that all 38 processes displayed windows simultaneously.

Expected behavior

Registering the documented stdio MCP integration should not repeatedly surface OpenScreen UI during unrelated chats. Multiple client sessions should have a supported lifecycle that avoids leaving unnecessary Electron processes running. Recording or editing UI should appear only when requested, or otherwise be clearly documented.

To reproduce (observed workflow)

  1. Install OpenScreen 2.1.2 on macOS.

  2. Follow the install-page instructions: npx skills add getopenscreen/openscreen --skill openscreen-demo -y.

  3. Confirm the installed executable's help output lists mcp.

  4. Register it using:

    codex mcp add openscreen -- /Applications/OpenScreen.app/Contents/MacOS/Openscreen mcp

    Resulting config:

    [mcp_servers.openscreen]
command = "/Applications/OpenScreen.app/Contents/MacOS/Openscreen"
args = ["mcp"]

  5. Use Codex across chats/sessions over time. Desktop and Homebrew Codex app-server processes were both present in this environment.

  6. Observe repeated OpenScreen popups and accumulated processes with this exact main-process command:

    /Applications/OpenScreen.app/Contents/MacOS/Openscreen mcp

This has not been reproduced on a clean profile or with only one MCP client. A single-client minimal reproduction is still needed.

Environment

  • OpenScreen version/build: 2.1.2 / 2.1.2 (read from the installed app's Info.plist)
  • Bundle identifier: com.etiennelescot.openscreen
  • macOS: 26.5.2
  • Architecture: arm64 / Apple Silicon
  • MCP transport: stdio, global Codex configuration
  • Device: Mac laptop
  • Browser: not applicable

Workaround and limitations

Removed the global integration with codex mcp remove openscreen, stopped the remaining OpenScreen processes, and uninstalled the app at the user's request. Recordings and projects were preserved. There were zero OpenScreen processes immediately after cleanup; long-term popup recurrence has not been assessed.

Please investigate whether macOS MCP startup can remain genuinely headless and how concurrent MCP client instances should be managed. I cannot infer the internal cause from the process listing alone.

主要语言
TypeScript
星标
3.7k
派生
231
平均合并
19 小时 7 分钟
30 天内合并 PR
266

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

getopenscreen/openscreen 的其他 Issue

查看 getopenscreen/openscreen 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。