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

Abierto
  • ¿Algo no está bien?
#1,488 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
38/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
electron, macos, typescript
Área
audio-video-rtc, desktop

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
3.7k
Forks
231
Merge medio
19 h 7 min
PR fusionados (30 d)
266

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de getopenscreen/openscreen

Todos los issues de getopenscreen/openscreen

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.