TUI still shows “Implement this plan?” after implementation starts from another client

What version of Codex CLI is running?

0.147.0

What subscription do you have?

Pro

Which model were you using?

No response

What platform is your computer?

No response

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

No response

Codex doctor report

What issue are you seeing?

I run Codex through app-server and connect the CLI with codex --remote.
The TUI shows “Implement this plan?”. I then start the implementation from another app-server client connected to the same thread.
The implementation starts normally, but the remote TUI still shows the old plan prompt.

What steps can reproduce the bug?

This setup uses one app-server process with two clients:

• Client A: Codex CLI TUI connected with codex --remote
• Client B: Agent Relay, connected through the app-server protocol

Both clients operate on the same thread.

1. Start one app-server: codex app-server --listen ws://127.0.0.1:4500
2. Connect Client A to it: codex --remote ws://127.0.0.1:4500
3. Connect Client B to the same WebSocket endpoint. Do not start a second app-server.
4. Start or resume a thread in Client A, then have Client B resume the same "threadId". Both clients are now subscribed to the same thread.
5. Enter Plan mode and complete a plan. Client A shows the “Implement this plan?” prompt.
6. In Client B, select "Implement" for that same thread. Client B switches the thread out of Plan mode and starts the implementation turn through the shared app-server.
7. The implementation starts successfully and Client A receives "thread/settings/updated" and "turn/started".
8. Check Client A.

Actual behavior

Client A still shows the old “Implement this plan?” prompt, even though Client B has already started implementation on the same thread.

Expected behavior

The remote TUI should dismiss the prompt when another client changes the shared thread out of Plan mode or starts a new turn.

What is the expected behavior?

No response

Additional information

I’m building an integration that lets users continue the same Codex session from either the CLI or an IM client.
A single app-server owns the session, while the CLI TUI and IM client connect to the same thread. Messages, streamed output, approvals, user-input requests, and Plan decisions should be available from either client.
The integration does not run the same action twice. Once an action is handled by one client, the other connected clients should reflect the updated thread state. This issue breaks that handoff: implementation starts from the IM client, but the TUI keeps showing the stale Plan prompt.

Start by tracing how the TUI handles shared app-server events, especially thread/settings/updated and turn/started, when two clients are subscribed to one thread. Reproduce the two-client Plan-mode handoff described above, then verify that the TUI dismisses the stale “Implement this plan?” prompt after Client B starts implementation.