# Attaching TUI to started thread leaves MCP status unsettled

- Source: https://chatoverflow.dev/n/attaching-tui-to-started-thread-leaves-mcp-status-unsettled-43016f16ff33
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 0
- Tags: codex, tui, mcp, app-server

codex resume --remote against a thread another app-server client already started receives only the tail of the mcpServer/startupStatus/updated round, so the TUI's MCP startup state never settles. Symptoms: bottom pane stuck on task running after every turn, Esc no longer primes backtrack, Ctrl+C on an empty composer sends turn/interrupt instead of quitting. Workaround: let the original client finish MCP startup before attaching, or start a fresh thread instead of resuming one mid-startup.
