Repository navigation
Description
Operating system
Client: macOS 27.0, build 26A428, Apple silicon. Paired host: Arch Linux / Omarchy, desktop Orca.
Orca version
1.4.206 on both client and host. Source references below use the v1.4.206 release.
Details
The paired client's remote terminal tabs stop reflecting the host. New Terminal and Cmd+T start working shells on the host, but the client shows no new tabs. Later, several tabs appear together. The reverse also happens: closing the host terminals leaves their tabs visible on the client.
I reproduced this through the Mac UI and inspected the running renderer. The immediate cause is confirmed: the client has retired the publication epoch that the host is currently using. Fresh, authoritative snapshots from that publisher are rejected.
Reproduction observed on September 21, 2026
The client was already in the affected state. I have not isolated a deterministic cold-start sequence that first creates the poisoned epoch history.
- Select an existing paired-host Git workspace. The sidebar labels it Sleeping and the tab area is blank.
- Select New tab > New Terminal. No terminal tab appears.
- Press Cmd+T. Still no terminal tabs appear.
- Read the same workspace with
orca terminal list --environment <saved-environment> --worktree <workspace-selector> --include-visual-layouts --json. Both new terminals exist, are connected and writable, have tab/leaf IDs, and already show shell prompts. - Switch to another workspace and back. An early switch does not repair it. After further navigation, both terminals and an existing agent tab appear together.
- Close only the two test terminals by their runtime handles. Both close results report
ptyKilled: true. The host inventory retains only the pre-existing agent, but the client still displays three tabs.
The local Mac checkout of the same repository passed menu and keyboard terminal-creation tests in this run. The confirmed reproduction is the paired-host path.
Live debugger evidence
Before any recovery or mutation of the tracking maps, I read the affected workspace through the renderer's own runtimeEnvironments.call, using session.tabs.list. This succeeds through the same connection used by the UI.
The values below replace publisher identifiers with R, H, and H0. Versions and counts are unchanged.
| Observation | Value |
|---|---|
| Current host response | epoch renderer:R:client-navigation, version 187, 1 tab |
Renderer tabsByWorktree |
3 tabs |
latestSessionTabsSnapshotByWorktree |
epoch headless:H:client-navigation, version 181 |
latestReceivedSessionTabsSnapshotByWorktree |
same headless epoch/version, received frame 566 |
sessionTabsPublicationEpochHistoryByWorktree.current |
headless:H:client-navigation |
| Retired publication epochs | renderer:R:client-navigation, headless-hydrated:H0:client-navigation |
isRetiredSessionTabsPublicationEpoch(key, currentHostEpoch) |
true |
decideWebSessionTabsSnapshot(currentHostSnapshot, environmentId, runtimeId) |
{ apply: false, settlesHostMirror: true } |
workspaceSessionReady was true. The renderer knew the same runtime ID returned by the host. Both runtimes were ready/reachable. This is not a shell-start failure or merely a failed network request.
Faulty path and proposed fix
noteRetiredValueand the publisher fences retire the prior epoch when another publisher takes over. A live renderer publisher can return after a temporary headless publication, but its epoch remains retired.recordReceivedWebSessionTabsSnapshotandshouldApplyRecoveredWebSessionTabsSnapshotreject that retired epoch.decideWebSessionTabsSnapshotalso rejects it, matching the live result above.- Even the eager
refreshWebRuntimeSessionTabsSnapshotroutes a successfulsession.tabs.listresult through these gates. It has no authoritative repair path for this case.
The release already handles the analogous problem for local structured sessions in applyLocalStructuredSessionTabSnapshots, with returning-publisher tests, introduced in #18906. That repair requests an authoritative inventory and revives only the epoch it confirms.
Please add equivalent bounded, host-scoped repair to the remote terminal mirror. Do not simply accept every retired epoch: delayed frames from a genuinely superseded publisher must remain fenced. A regression test should cover renderer R, temporary headless H, then current renderer R again. Verify that new tabs and tab removals both reach the client after authoritative confirmation, and that delayed H frames remain rejected.
The exact host operation that introduced the temporary headless epoch in this session remains unconfirmed. The client-side rejection and poisoned history were directly inspected, not inferred from the screen recording.
Recovery verified
View > Force Reload on the Mac client cleared the poisoned in-memory state. It immediately removed the two stale tabs. I then created two remote terminals through the menu and keyboard shortcut. Both appeared without workspace switching. Closing both test terminals removed both tabs from the UI. The existing agent session remained running. No host restart or configuration change was needed.
This is a session recovery, not a permanent fix. The installed application and source checkout were not patched.
Related reports
- [Bug]: Desktop client paired to a remote runtime never mirrors a workspace created after the client connected (tabs and agent rows missing until reload) #19092, including the comment about new tabs in an already mirrored workspace.
- [Bug]: Paired client keeps a mirrored terminal tab for days after the host closed it (blank pane, "Remote terminal was closed.") #21236, stale terminal tabs after a host close.
This report adds a concrete live rejection reason for the observed missing/ghost-tab behavior. Browser Invalid guestInstanceId errors also occurred when closing a test browser tab, but terminal creation failed before that browser action. They are not required for this reproduction.
Activity
shahidbeig-a11y commentedon Sep 21, 2026
Working on a fix that mirrors the local structured-session retired-epoch repair (#18906) into the remote/web session tabs sync path, with a regression test for renderer → temporary headless → returning renderer.
GollyJer commentedon Sep 21, 2026
Cool, just came to report the same thing. Subscribed. 👍
rorar commentedon Sep 22, 2026
Another instance of this, with a deterministic trigger — which the report above notes is still missing — plus a workaround.
Setup. Client: Orca 1.4.205 on Linux (Wayland/GNOME). Paired host: a Linux machine running its own desktop Orca, which owns the sessions; the client only mirrors their tabs. Same
web-session-tabs-syncmodule as in the original report.Trigger.
View → Force Reloadon the client. Reproduced on demand, several times in a row.Symptom variant. Rather than tabs appearing late or lingering after close, an existing agent tab stays visible but its pane is dead:
What it is not.
runtimeEnvironments.getStatusSnapshots()verification: 'verified',transport: 'ready'pty.listSessions()on the clientThat last one is worth stating: the renderer's pane-recovery machinery is built on the premise that a remount reattaches over the live PTY and drains the buffer. For an orphaned mirror there is nothing local to reattach to, so the premise does not hold.
No diagnostics at all. With the renderer console open and "Preserve log" on across the reload, none of these appear:
[terminal-lifecycle],recovering pane tab,left the pane unbound,restored PTY reattach threw. All four strings are present in the shipped 1.4.205 bundle, so their absence is real, not a stripped build. Nothing notices the state — which matches this issue's finding that the snapshot is rejected rather than failing.Workaround. In the renderer console (focus a terminal pane before opening DevTools, otherwise the embedded browser's console opens instead):
then
View → Reload— the plain one, not Force Reload.<envId>comes fromruntimeEnvironments.list().Both halves are required. The reconnect alone leaves the pane empty, and a Reload alone does nothing (it had already been tried many times). Only the pair rebuilds the mirror. The host session is unaffected throughout.
If the epoch history is what rejects the publisher, a reconnect plus a fresh renderer is presumably what clears it — which would fit the proposed fix direction in the original report.
Written together with Claude Code (Opus 5).
AmethystLiang commentedon Sep 22, 2026
thanks for reporting. looking into it
johnmarktaylor91 commentedon Sep 30, 2026
Additional evidence, possibly a related path: a browser tab opened on the laptop client disappears seconds after it opens.
Setup: headless-served hub (Linux AppImage, server mode) with a macOS client, Orca 1.4.217 on the Mac. A browser tab opened from a link to a local http page (served through an SSH tunnel on 127.0.0.1) vanished right after it opened, three times in two minutes. The Mac client's main.trace.ndjson has a matching renderer_error each time:
The same error appears with guestInstanceId 8, 9, 11 and 12 (2026-09-30 19:23:44, 19:24:38, 19:24:56 and 19:26:18 UTC). The stack suggests the guest webContents is destroyed first;
handleDestroyedthen callsreleasePage, and detaching the<webview>throws because the guest id is already gone. So the throw looks like a side effect, not the cause: something tears down the guest right after creation.Right after that, a tab created from the hub (
orca tab create --worktree path:...) stays in the runtime's tab list but is never drawn on the Mac client. That matches this issue (new tabs hidden after a headless epoch) and #21052. Restarting the Mac client restores tab drawing.Two suggestions: guard
releasePageagainst an already-destroyed guest so it does not throw during teardown, and log why the guest was destroyed (crash, navigation to a blocked origin, or the mirror dropping the tab), which would show whether the vanishing tab and the hidden-tab bug are one cause.