[Bug]: New chat started from a remote-server chat is locked to that remote with no way to change the target host #16569

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/web

Steps to reproduce

1. Connect T3 Code to a remote server (remote connection / remote environment).
2. Open an existing chat whose thread lives on that remote server.
3. Start a new chat while that chat is selected.

Expected behavior

The new chat lets me choose its target host (local or any connected remote), the same way a new chat started from elsewhere does. Starting a new chat from a remote thread may reasonably default to that remote server, but the default should be changeable before the first message is sent.

Actual behavior

The new chat is locked to the remote server the previous chat was on. There is no option to change the conversation's target host, so the only way to start a chat on a different host appears to be leaving the remote thread first and starting the chat from somewhere else.

Impact

Minor bug or occasional failure

Version or commit

T3 Code (Alpha) 0.0.45 (desktop)

Environment

Desktop app (Electron 44.4.2, arm64), macOS 27.0 (build 26A428), Apple Silicon. Bundle ID com.t3tools.t3code.

Workaround

Select a thread (or project) on the desired host first, then start the new chat from there. (Not verified to work in every case.)