Rosalind Workbench MCP fails to start in TUI

What version of Codex CLI is running?

v0.150.1

What subscription do you have?

$100 Pro

Which model were you using?

5.6 sol

What platform is your computer?

Slurm HPC; Linux 3.10.0-1160.156.1.el7.tuxcare.els1.x86_64 x86_64 x86_64

What terminal emulator and version are you using (if applicable)?

tmux

Codex doctor report

What issue are you seeing?

I recently enabled the Rosalind Workbench in ChatGPT/Codex. However, on loading the TUI, I get this error:

⚠ MCP client for `structure-viewer` failed to start: MCP startup failed: handshaking with MCP server failed: Send message error Transport
  [codex_rmcp_client::stdio_server_launcher::StdioServerTransport] error: Broken pipe (os error 32), when send initialize request

⚠ MCP client for `sequence-viewer` failed to start: MCP startup failed: handshaking with MCP server failed: connection closed: initialize response

⚠ MCP client for `rosalind` failed to start: MCP startup failed: handshaking with MCP server failed: Send message error Transport [codex_rmcp_client::stdio_server_launcher::StdioServerTransport]    
  error: Broken pipe (os error 32), when send initialize request

⚠ MCP client for `slide-viewer` failed to start: MCP startup failed: handshaking with MCP server failed: Send message error Transport [codex_rmcp_client::stdio_server_launcher::StdioServerTransport]
  error: Broken pipe (os error 32), when send initialize request

⚠ MCP client for `ngs-app` failed to start: MCP startup failed: handshaking with MCP server failed: connection closed: initialize response

⚠ MCP client for `ngs-analysis-workbench` failed to start: MCP startup failed: handshaking with MCP server failed: connection closed: initialize response

⚠ MCP client for `ngs-compute` failed to start: MCP startup failed: handshaking with MCP server failed: connection closed: initialize response

⚠ MCP startup incomplete (failed: ngs-analysis-workbench, ngs-app, ngs-compute, rosalind, sequence-viewer, slide-viewer, structure-viewer)

I haven't even started to use Rosalind workbench yet so I'm not sure what this is.

What steps can reproduce the bug?

I just started codex TUI.

What is the expected behavior?

No response

Additional information

No response

Start by reproducing TUI startup on the reported Slurm HPC Linux environment with Rosalind Workbench enabled. Inspect MCP initialization around codex_rmcp_client::stdio_server_launcher::StdioServerTransport and compare the broken-pipe and closed-connection failures. Done means the configured MCP servers complete initialization without the incomplete-startup warning.