You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: After main reconnects to the terminal daemon, terminals shown only on a phone, a paired desktop or via orca terminal send refuse input #38433
Short summary:
When the host's main process loses and re-makes its connection to the terminal daemon, the daemon releases main's attachments, and every session refuses input until it is attached again. Only a pane mounted in the host's own window re-attaches. A terminal shown only on a phone or a paired desktop, or targeted by orca terminal send, stays detached: its output stops and every keystroke is refused, while orca terminal list still reports it connected and writable.
What happened?
On 2026-10-31 a Windows host's main process re-made its daemon connection twice that evening while the daemon kept running. Afterwards a paired desktop's panes for host terminals whose workspace was not open in the host window went silent and refused every keystroke. Remounting or restarting the client did not help: its new subscription never re-attached the session.
How can we reproduce it?
On a host, open a terminal in a workspace the host window is not showing, and view it from a phone or a paired desktop.
Make main's daemon connection drop and reconnect while the daemon keeps running.
Type from the phone or paired desktop, or run orca terminal send against it: the input is refused.
Anything else that might help:
Expected: main re-attaches such a terminal when a remote view shows it, and input waits for that attach instead of being refused.
Activity
fix(runtime): re-attach every terminal a daemon reconnect detached (#…