[Bug]: Cannot take browser control on iPhone while another device retains control#33398
Before submitting
- Searched existing issues and PRs; no duplicate for explicit device-to-device takeover found.
- Included a reproducible case and source-level evidence.
Area
apps/mobile, apps/web and apps/server — streamed collaborative browser control.
Steps to reproduce
- Run a T3 environment on a Linux host and connect from both the macOS desktop app and the iPhone app.
- Open the same thread and browser tab on both devices.
- On the Mac, choose Take control and leave the Mac connected.
- On the iPhone, try to take control of the tab.
Expected behaviour
An authorised viewer should have an explicit way to take over from their other device without first returning to that device to release control. This should remain a deliberate action, and read-only viewers should still be unable to take control.
Actual behaviour
The Mac shows You have control. The iPhone streams the page successfully but shows Another viewer has control with Take control disabled. Leaving the Mac connected therefore prevents a handover to the phone while away from it.
This is not the no-input-after-successful-takeover bug in #19420, or the stream-connection hang in #24852. The stream works; the control action is unavailable. #17057 requested automatic/implicit interaction; this report retains explicit control and concerns switching devices.
Environment and version
Observed on 9 November 2026: Ubuntu host, macOS T3 Code desktop client and iPhone client, connected to the same environment. Host CLI reports t3 v0.1.7; exact Mac and iPhone client builds were not captured.
Source confirmed on upstream 6647b0a761ff7a1287047a9bb5fd5b63772f456b and b8c2cfad: both streamed client controls disable the button for another-viewer, and SessionControl.take rejects a second viewer with “Another viewer controls this browser tab.” A regression test reproduces that refusal.
Impact and workaround
Blocks browser input from the phone whenever the other connected client retains control. Releasing control on the Mac before leaving works, but requires access to the Mac.
Supporting evidence
| Mac retains control | iPhone cannot take control |
|---|---|
User-supplied screenshots of the original failure, with website content, addresses, project names, conversations and personal details blurred using an image-editing tool and approved by the reporter. These show the reported pre-fix state, not a successful handover or an after-fix capture. The originals have not been uploaded.
Prepared with GPT-6.1-Sol through the Codex harness in T3 Code.