Skip to content

[macOS Desktop 26.1117] Command runner output channel repeatedly hangs while chat remains responsive #62983

Open

Description

@UnConundrum

The ChatGPT desktop app's Codex command execution channel repeatedly becomes unresponsive on macOS. The chat and other app functionality remain responsive, but even a trivial command invoked from /tmp produces no output and does not exit through the tool channel. Fully restarting the app temporarily restores execution, but the failure recurs.

This is not a command that is legitimately running for a long time and is not waiting for an approval.

Environment

  • ChatGPT desktop app with Codex: 26.1117.31558
  • Bundle build: 29513
  • macOS: 27.0.1 (26A434)
  • Architecture: Apple Silicon (arm64)
  • Session ID: 019fd2ea-cd5c-7920-a6f3-bb8aa51aeb77

Minimal reproduction / health check

After the runner enters the bad state, execute:

command: /bin/echo runner-ok; /bin/date; /usr/bin/uptime
working directory: /tmp
login shell: false
TTY: false/default pipes
initial yield: 3 seconds

Actual behavior

  • No output is returned, including from /bin/echo.
  • The tool remains running and must be terminated.
  • One captured call returned only a running-cell identifier after approximately 31 seconds, still with no command output.
  • Computer-use automation and ordinary chat remain responsive.
  • Restarting the desktop app restores command execution temporarily, but the failure has recurred several times after restart.

Expected behavior

The command should return immediately. If the command worker or output transport is unhealthy, the app should fail quickly with an actionable error or automatically restart the worker.

Isolation evidence

  • Reproduces from /tmp; it is not dependent on the workspace directory.
  • Uses absolute-path system binaries and disables login-shell startup.
  • Filesystem searches complete immediately whenever the runner is healthy.
  • Spotlight was effectively idle during one occurrence (mds about 0.2% CPU, mds_stores 0.1%/0.0%, mdworker 0.0%).
  • Other Codex facilities remain responsive during the command-channel failure.

Sanitized desktop-log evidence

During the affected window, the desktop log repeatedly contains:

[IpcClient] Received broadcast but no handler is configured method=thread-queued-followups-changed

At 2026-11-21T14:33:42Z, around restart/recovery, it contains repeated:

[IpcClient] Received broadcast but no handler is configured method=ipc-connection-reset

followed by:

[AppServerConnection] app_server_connection.state_changed cause=stop_process ... previous=connected next=disconnected ... transport=stdio

The local transcript metadata can report a trivial command as completed with zero duration while the calling tool waits roughly 31 seconds and receives no output. That suggests disagreement between execution state and delivery of the tool result.

Privacy note

The complete session transcript contains confidential legal/client information and cannot be posted publicly. I can provide additional sanitized excerpts or use a private upload route if an OpenAI maintainer requests them.

Related issues reviewed

Activity

  1. added
    bugSomething isn't working
    appIssues related to the Codex desktop app
    tool-callsIssues related to tool calling
    app-serverIssues involving app server protocol or interfaces
    on Nov 21, 2026
  2. github-actions commented on Nov 21, 2026

    @github-actions
    Contributor

    Potential duplicates detected. Please review them and close your issue if it is a duplicate.

    Powered by Codex Action

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appapp-serverIssues involving app server protocol or interfacesbugSomething isn't workingtool-callsIssues related to tool calling

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions