Watching a remote turn from the local terminal too

If you happen to be sitting at the paired machine's own terminal at the exact moment a remote-triggered prompt is sent, you will see it appear there too, in the same terminal window.

This is because it is genuinely the same tCode process handling both the local and the remote path, simply relaying a copy of everything to the browser as well, not two separate processes running in parallel.

There is no separate hidden process quietly running in the background specifically for remote turns; local and remote both flow through the exact same running instance of tCode.

This is a useful thing to know if you are trying to understand what tCode is currently doing on a machine you have physical access to; the local terminal is always an accurate, real-time view of everything happening on that machine, remote-triggered work included, never a partial one.

It also means there is nothing to specifically monitor or check for on the local side to know whether remote turns are active; if a remote turn is running, it is visible in the same terminal window you would already be looking at.