Skip to content

[Bug] Tab Syncing Issue Across Devices (Seemingly Chat UI-Specific) #24256

Closed

Description

@orca-discord-issues

Cole Cole via Discord

Hi! These tests were conducted on a Mac Mini and MacBook Pro both connected via Remote Server. The rest of the Guideline details and the summary of the bug are within this artifact.

https://share.onorca.dev/a/XHYXTKLK1P1Z

Activity

  1. shaharmor commented on Oct 1, 2026

    @shaharmor
    Contributor

    I've actually seen it happening too when using the orca cli to open new tabs from the server, they don't always (sometimes do) sync to the mobile app

  2. orca-discord-issues commented on Oct 1, 2026

    @orca-discord-issues
    Author

    nwparker nwparker via Discord

    Thanks for sharing! We'll fix this one.

    Though we likely next week since a few sensitive changes are landing the next 2 days in this area.
    But then we'll clean up this for sure 🫡

  3. AmethystLiang commented on Oct 1, 2026

    @AmethystLiang
    Contributor

    Thanks for reporting. Looking into it

  4. self-assigned this
    on Oct 1, 2026
  5. LesleyMurfin commented on Oct 1, 2026

    @LesleyMurfin
    Contributor

    This is addressed by @brennanb2025's open PR stack:

  6. nwparker commented on Oct 4, 2026

    @nwparker
    Contributor

    Resolved on main by the merged structured-chat PR stack:

    Verification included reading the reporter's shared artifact (https://share.onorca.dev/a/XHYXTKLK1P1Z), checking the merged code and passing PR CI, and executing the actual tab-projection code with each version's desktop capability list. The v1.4.220 code hides a Claude structured-chat tab while retaining terminal tabs; current main retains both. The PRs also document live paired-Mac testing, including chat visibility, sending a message, and closing the chat. A fresh full two-device UI run was not performed for this verification.

    Release caveat: these fixes are not included in v1.4.220, which was built from an earlier snapshot plus selected fixes. Users on that release can still encounter this issue; the resolution requires a build containing the merged stack above. Closing as fixed on main, pending release.

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 working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions