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]: Viewing an active terminal from mobile creates a duplicate desktop terminal tab #10486
Viewing an active Orca terminal from a paired mobile client causes the macOS host to open an additional terminal tab. The new tab shows the same terminal content as the existing tab.
What happened?
An active Codex terminal was viewed from Orca on a phone. Afterward, the desktop Orca window contained an extra terminal tab with the same content as the original terminal.
The extra tab was manually closed. The issue then reproduced again after using the mobile view, so this was not a one-time stale UI artifact.
How can we reproduce it?
On the macOS host, keep an active agent terminal open in Orca.
Connect to Orca from a phone and view that terminal.
Return to the desktop Orca window.
Observe that an additional terminal tab has appeared with the same content as the original tab.
Close the extra tab and repeat the mobile-view flow; the duplicate tab can appear again.
Expected behavior
The mobile client should attach to or mirror the existing terminal without creating another terminal tab on the desktop host.
Actual behavior
A second terminal tab appears on the desktop and displays the same content as the original terminal.
Additional notes
Reproduced twice on Orca 1.4.153-rc.3.
The duplicate tab can be closed manually, but that is only a temporary workaround.
Terminal handles and PTY/process IDs were not captured before closing the duplicate, so it is not yet known whether this is a duplicate UI mirror of the same PTY or a separately resumed process.
A screenshot was captured, but it contains private conversation content and is intentionally not attached. A fully redacted tab-bar-only crop can be provided if needed.
One correction to the repro: a single-pane terminal was never affected — that tab matches on tab.ptyId, so the reveal adopts it. The reachable defect is the split-pane case with the worktree closed on the desktop: no pane is mounted, so ptyIdsByTabId is empty and tab.ptyId only holds one leaf's PTY. The other leaf's PTY exists solely in the persisted layout, which ownership resolution never consulted — so createTab ran with the tab id already in use, hit its collision guard, minted a fresh uuid, and you got a second tab on the same session.
If you can still reproduce it on a plain single-pane terminal, that's a different bug and worth a fresh issue with the tab bar crop.
Activity
fix(mobile): reuse host tab when viewing a live terminal from phone
brennanb2025 commentedon Jul 29, 2026
Fix up in #11259.
One correction to the repro: a single-pane terminal was never affected — that tab matches on
tab.ptyId, so the reveal adopts it. The reachable defect is the split-pane case with the worktree closed on the desktop: no pane is mounted, soptyIdsByTabIdis empty andtab.ptyIdonly holds one leaf's PTY. The other leaf's PTY exists solely in the persisted layout, which ownership resolution never consulted — socreateTabran with the tab id already in use, hit its collision guard, minted a fresh uuid, and you got a second tab on the same session.If you can still reproduce it on a plain single-pane terminal, that's a different bug and worth a fresh issue with the tab bar crop.
fix(mobile): stop a mobile reveal from minting a duplicate terminal tab
fix(mobile): stop a mobile reveal from minting a duplicate terminal t…
fix(mobile): stop a mobile reveal from minting a duplicate terminal t…
Reland canonical PTY hydration without evicting live legacy rows (sta…