Skip to content

[Bug]: Viewing an active terminal from mobile creates a duplicate desktop terminal tab #10486

Closed

Description

@wohsj110

Operating system

macOS

Orca version

1.4.153-rc.3

Details

Short summary

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?

  1. On the macOS host, keep an active agent terminal open in Orca.
  2. Connect to Orca from a phone and view that terminal.
  3. Return to the desktop Orca window.
  4. Observe that an additional terminal tab has appeared with the same content as the original tab.
  5. 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

Activity

  1. added a commit that references this issue on Jul 28, 2026
    c3447e3
  2. brennanb2025 commented on Jul 29, 2026

    @brennanb2025
    Contributor

    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, 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingos:macosIssues affecting macOS

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions