jif 0ffcefaf3d feat: keep child MCP warnings out of parent transcript (#27174) ...

## Why

MCP startup status notifications are thread-owned, but `ChatWidget`
trusted upstream routing. If routing state delivered a tagged child
notification to the active parent widget, the child MCP failure could
still mutate the parent's startup state and transcript. Rejecting it
only inside the MCP handler was also too late because shared
notification handling could already restore and consume the parent's
retry status.

## What changed

- Validate a tagged MCP status notification against the visible
`ChatWidget` thread before shared notification handling mutates any
parent state.
- Cover child `Starting` and `Failed` notifications delivered to a
retrying parent widget, asserting that they preserve its visible retry
error and saved status header while producing no history or MCP status
mutation.

## User impact

Subagent MCP startup failures remain scoped to the child transcript
instead of appearing as duplicate warnings in the parent transcript.

## Testing

- `just test -p codex-tui mcp_startup_ignores_status_for_other_thread`
- `just test -p codex-tui
primary_thread_ignores_child_mcp_startup_notifications`
- `just fmt`

0ffcefaf3d · 2026-06-10 11:45:49 +02:00

History

..

frames

Rename tui_app_server to tui (#16104)

2026-03-28 11:23:07 -06:00

src

feat: keep child MCP warnings out of parent transcript (#27174)

2026-06-10 11:45:49 +02:00

tests

Simplify TUI startup test coverage (#22573)

2026-05-13 18:16:54 -07:00

BUILD.bazel

Remove CODEX_RS_SSE_FIXTURE test hook (#22413)

2026-05-13 03:08:01 +00:00

Cargo.toml

Move cloud requirements crate to cloud config (#24621)

2026-06-01 16:43:52 -07:00

prompt_for_init_command.md

Reduce TUI legacy core dependencies (#26711)

2026-06-09 13:26:00 -07:00

styles.md

Rename tui_app_server to tui (#16104)

2026-03-28 11:23:07 -06:00

tooltips.txt

feat(tui): add configurable keymap support (#18593)

2026-04-28 12:52:25 -03:00