Skip to content

[Bug]: On a secondary client Mac, empty "Terminal" tabs respawn infinitely, split groups cap at 2, and the window continuously resizes — same v1.4.145 works on the runtime-host Mac #9423

Closed

Description

@dannywelt

Summary

On a secondary client Mac, empty Terminal tabs respawn infinitely, terminal split groups hard-cap at 2, and the app window continuously resizes by itself. The exact same Orca version with the same sessions works perfectly on the runtime-host Mac. So the same account + same version behaves completely differently between the runtime host and the client machine.

Environment

  • Orca version: v1.4.145 (1.4.145) — confirmed identical on both machines
  • Machine A — WORKS (runtime host): Mac mini, macOS Tahoe 26.5.2
  • Machine B — BROKEN (client): MacBook Pro 14" (Nov 2024), Apple M4, 16 GB, macOS Tahoe 26.5.1, internal display only
  • Both machines are on the same account and view the same worktree/sessions (Machine A hosts the runtime; Machine B is a secondary client).

What happens (Machine B only)

  1. Empty "Terminal" tabs respawn infinitely. Extra empty Terminal tabs keep appearing in a group's tab bar. Closing them (X) makes them reappear immediately, over and over.
  2. Split groups cap at 2. I can form a left + right split group, but a 3rd group cannot be created. From the identical setup on Machine A, I can create 3+ groups with no problem.
  3. The app window continuously resizes on its own (shrinks/grows), most noticeably while terminal output streams and on focus changes. This resembles the previously-fixed "Zoom the app after leaving terminal focus" issue (v1.4.97) — possible regression on this hardware/OS.

On Machine A (runtime host) none of the above happens — same version, same sessions.

Steps to reproduce

  1. Use one Mac as the runtime host and a second Mac as a client viewing the same worktree/sessions.
  2. On the client, open a worktree with agent sessions and try to arrange three side-by-side split groups.
  3. Observe: only 2 groups form; empty Terminal tabs appear and re-appear on close; the window resizes itself.

Expected

  • No auto-generated empty terminal tabs.
  • 3+ split groups can be created (docs advertise nested/"infinite" splits, and pinned pane boundaries).
  • Window bounds stay where the user puts them.

What was already tried — did NOT fix it

  • Full quit (Cmd+Q) and relaunch
  • Reinstalling the app
  • Confirming both machines are on the identical version (v1.4.145)
  • UI zoom out (Cmd+-)
  • Removing the client's local profile state: ~/Library/Application Support/orca/profiles/local-default/orca-data.json (+ .bak.*), then relaunch — the empty Terminal tabs STILL respawn afterward. This strongly suggests the respawn source is runtime/session-side state, not the client's local layout file.

Diagnostic notes

  • The infinitely respawning empty terminals look consistent with a workspaceSession.defaultTerminalTabsAppliedByWorktreeId flag never sticking, causing default terminal tabs to be re-applied on every render/focus.
  • Split layout state lives in workspaceSession.terminalLayoutsByTabId; on the healthy machine expandedLeafId is null and multiple groups exist — so this is not a stuck "Expand Pane" state.
  • Keybinding note on the broken machine: Cmd+D splits a pane; Cmd+\ does nothing.

Impact

The client Mac is effectively unusable for multi-session side-by-side work. Only the runtime-host Mac is usable, which defeats the multi-device workflow.

Activity

  1. dannywelt commented on Jul 19, 2026

    @dannywelt
    Author

    Additional context — likely related to #9217, and this is remote (SSH relay / Orca server) mode.

    Confirming the setup: the broken machine (MacBook Pro client) connects to the runtime-host Mac (Mac mini) over SSH relay / "Orca server" remote mode — the exact mode #9217 is filed under.

    This looks like the same family as #9217 ("Ghost 'active' terminal/agent rows persist after remote connection loss"), though not an exact duplicate:

    Shared root theme: remote-mode session/terminal state is not being reconciled/cleaned up on the client, so ghost/default entries keep coming back.

    Key corroborating datapoint from this issue: deleting the client's local profile state (~/Library/Application Support/orca/profiles/local-default/orca-data.json + .bak.*) did NOT stop the respawning Terminal tabs. That points to the source being runtime/remote-side state, not the client's local layout file — consistent with #9217's analysis that the clear chain (clearProviderPtyState → clearPaneState → agentStatus:clear) doesn't fire correctly in remote mode.

    Filing separately because the surface (tab-bar terminal tabs + split/window layout) differs from #9217's sidebar rows, but they likely want to be looked at together.

  2. AmethystLiang commented on Jul 19, 2026

    @AmethystLiang
    Contributor

    Duplicate of #9352

    Same remote/secondary-client problem: closed or empty terminal tabs keep being restored/respawned while the runtime host is fine.

    Consolidating into #9352 (which already has root-cause notes around mirror/pty-exit / resume races). Please continue there; if split-group caps or auto-resize still happen after the restore fix, reopen with a focused repro.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions