A Session History row from the user's own OpenCode store sent no account request, so the host fell back to the selected managed account, where OpenCode 2's --session silently creates an empty session with the same id. The resume now names the System store, and daemon spawns keep that choice for the private-server check.
The xterm helper's focusin now rebuilds the macOS input context when focus arrives from any text field, or after the page lost focus (a browser guest or another app) since the last terminal arrival. Refreshes for one helper within a frame share one refocus.
Fixes#23864
Co-authored-by: Fanzzzd <fanzzzd@outlook.com>
* fix(browser): stop refusing agent input while Orca's window is briefly busy
* docs(browser): say which focus refusals are safe to retry
* refactor(browser): drop the focus refusal phase that cannot happen
* fix(watchers): keep home-folder watches out of other apps' macOS data
A folder workspace rooted at the home directory subscribed to all of
~/Library. Parcel stats every changed path, and a stat inside another
app's container or group container makes macOS ask whether Orca may
access data from other apps, again for each write that app makes.
Exclude ~/Library from macOS watch roots that contain it, and only the
Containers and Group Containers stores when ~/Library itself is the root.
Ordinary project roots keep the same options.
* fix(watchers): exclude protected Library stores against the canonical watched root
Review follow-up. Decide the exclusion in the watcher supervisor, after the
root is resolved to the identity Parcel actually subscribes, and resolve
each home's Library the same way so symlinked or case-variant homes match.
Pass the paths as Parcel ignorePaths so a home containing glob characters
is still excluded literally, and protect both HOME and the account's own
home when a host runs with HOME pointed at a separate profile.
Callers go back to their previous options; every watcher gets this through
the supervisor.
* fix(watchers): fall back to no exclusion when home or realpath lookups fail
Read HOME, the account home and realpath inside the guarded lookup, as
root resolution does, so hosts or harnesses without them keep the
previous watch options.
* fix(watchers): decide Library exclusions in the watcher process
Resolve the protected Library paths where Parcel subscribes, in the
watcher child, so the realpath lookups stay off Electron main and the
supervisor is unchanged. Tests write fixture revisions instead of
wall-clock values.
* fix(watchers): apply Library exclusions where the watcher receives a subscribe
Keeps the existing Parcel options cast untouched.
* fix(watchers): count only real parent steps as outside the watched root
A home named like '..profile' inside the watched root is still a
descendant, so its Library must be excluded too.
* test(watchers): make simulated macOS paths portable
Tools like Expo, Claude and Node's spawn run BROWSER as a program, so the
"orca open-url --url %s" template failed with ENOENT. Point BROWSER at the
Orca CLI launcher this host already puts on PATH, and let the CLI treat a
lone http(s) URL as open-url.
Co-authored-by: fancive <10972140+fancive@users.noreply.github.com>
The copy took --standalone from the opencode2 row's launch command whenever the
history row said opencode2. That label never tells which OpenCode the opencode
binary is: the chat tab route always named opencode2, and OpenCode 2 copies 1.x
sessions into session_v2. OpenCode 1 rejects the flag and prints its usage.
The copy now opens with its own CLI's launch settings. prepareOpenCodePtyLaunch
already adds --standalone for OpenCode 2 when a private server is needed.
Fixes#42223
* feat(mobile): add chat text size, font and line spacing settings
Pinching in a chat now saves the size for every chat instead of resetting when you leave.
* fix(mobile): measure the screen on the first chat text read, not at import
On Windows, path.relative() returns an absolute path when the plugin root
and the file are on different drives or UNC roots. The plugin test hooks
and panel-check stack locator only treated '..'-prefixed results as
outside the plugin, so Orca's bundled testing runtime was resolved as a
plugin file and panel issues pointed at Orca frames.
Add a shared pathInsidePluginRoot helper (also backing isInsidePluginRoot)
that rejects empty, '..', '..<sep>' and absolute relative paths, use it at
both call sites, regenerate orca-test-hooks.mjs, and add win32-mocked
regression tests.
Fixes#43195
Co-authored-by: alaya <21375302+AlayaElla@users.noreply.github.com>
Co-authored-by: Neil <neil@stably.ai>
OpenCode /models, /help and similar commands open a dialog the Chat
view cannot show, and later chat sends were typed into it. Flag the
commands that open a TUI screen (OpenCode, Codex pickers, OMP's
in-Terminal commands) and switch the terminal-backed chat to Terminal
once the command is submitted, on desktop and mobile.
* feat(mobile): add a stepped slider control
* feat(mobile): terminal font, size, line spacing and weight settings
Terminal settings get a Font section with a live preview: a font picker
(system fonts plus JetBrains Mono, Fira Code and Geist Mono shipped as
variable woff2), a point-size slider replacing the old percentage presets,
line spacing and weight. Pinch now snaps to whole points. Tablets start at
15 pt, Normal spacing and Regular weight.
The size keeps its storage key as points over 13; the font, spacing and
weight live in a new negotiated page storage key. Both terminal hosts read
them at start and on a new set-font-style message; a style change keeps
the grid and lets the cell-box refit resize the PTY.
* fix(mobile): resume an interrupted desktop page download instead of starting over
The phone held hash-verified page assets only in memory until the whole
build arrived, so a cut link discarded them and every later entry started
the build from byte 0. Each verified asset is now kept under the host's
partial/<buildId>, and the next fetch of that build reuses it.
* fix(mobile): keep nothing for a build with case-aliased asset paths
Each NavBar side shrank to whatever the centred title left, so a long title
pushed a side's second button under the title view. On the leading side the
title paints above the button and swallowed taps, so Hide sidebar did nothing
on wide layouts with long host names. Floor each side at two buttons.
* test(editor): keep a draft whose workspace disappeared while closed
* fix(editor): keep unsaved drafts of workspaces gone at startup and offer Reopen
* fix(editor): settle recovered stranded drafts by identity; keep them over a clean returning tab
* fix(editor): reopen stranded drafts as dirty untitled tabs in the active workspace
* fix(editor): stamp the recovered tab's empty baseline and retry stranded drafts on host changes
* refactor(session): move the editor session builder to its own file
* fix(editor): retry stranded drafts after any dropped trigger, including paired-server SSH changes
* Revert "refactor(session): move the editor session builder to its own file"
This reverts commit 47d3a79eb8.
* refactor(session): move the terminal session builders to their own file
* refactor(session): keep terminal builders in place; move only the tab sanitizer
* fix(editor): don't flag a recovered draft's own placeholder create as a change on disk
* fix(editor): retry stranded drafts when the active workspace's host changes
* fix(accounts): restart busy Claude sessions at once when the account is switched
A restart accepted after a Claude account switch waited for each busy
session's turn to end, so long turns, subagents and background shells
kept spending the old account until it hit its limit. Accepted restarts
now interrupt the session and resume it on the new account right away,
the same as Codex.
* fix(accounts): say in the restart setting that busy sessions stop their work
* fix(accounts): keep each tab's queued Claude restart selection local to that tab
* fix(accounts): run a queued account restart once its pane's terminal attaches
* fix(accounts): wake queued restarts from the leaf bind path too
* test: mark the restart mount-race test's stub casts as safe
* fix(accounts): run the queued-restart wake without a new React hook
* Wake queued account restarts when mounted ownership ends
* Move or report every running Claude terminal on an account switch
A switch only saw panes whose hook status row said Claude, so Agent Teams panes (an `Orca` foreground), panes with hooks off, and panes whose row was dismissed were skipped without a word. The scan now also finds Claude from a saved session record, the pane's own process read, or a one-pane tab's launch; resumes from the saved record when the row is gone; and, when nothing on the outgoing account moves, warns about running sessions Orca can't resume that may still be on it, with Review.
Tracked in STA-15061.
Co-authored-by: Claudio <claudiofernandopinto@gmail.com>
* Keep Claude account restart discovery aligned with saved sessions
* Restart WSL Claude panes only with live evidence
* Keep the original conversation pane during account restart
* Keep retrying account restarts in their conversation pane
* Place the restart fixture cast rationale on its assertion
---------
Co-authored-by: Claudio <claudiofernandopinto@gmail.com>
* fix(native-chat): send other agents' mail as a pointer and let the person approve a denied action
Another agent's orchestration message reached a structured chat's agent as
ordinary user input, so Codex's automatic reviewer counted a coordinator's
words as the user's authorization. The chat card still shows the whole
message, labeled with its sender; the agent is now sent Orca's existing
pointer at `check`, so the content arrives as tool output. Mail stays unread
until `check` takes it, and a new coordinator is pointed at mail the old one
never read.
Codex automatic-review denials now show as a chat row with the reviewer's
reason and an "Approve once" button, which only this computer's own Orca
window may press; it uses Codex's thread/approveGuardianDeniedAction and
records the approval in the chat.
Tracked in STA-15406.
* fix(orchestration): wake any new mailbox owner after re-pointing stale mail
* fix(native-chat): settle check:changed for pointer mail and denial approval
Move the Codex approval and mobile review copy into their own modules, reuse the shared record guard, and update the tests that encoded whole-mail consumption to pointer delivery with mail read at check.
* style: format review notice copy
* fix(native-chat): hold accepted mail while custody is unreadable and show the whole denied action
* fix(orchestration): hold in-doubt mail while custody is unreadable and wake the new owner after a send-time handoff
* test(orchestration): keep crew reads off a chat host another test file left installed
* perf: reuse AI-vault title requests across a sync pass until an input changes
The title pass rebuilt every tab's conversation 2 + 2 x batches times per
20 s pass. Keep one request snapshot per sync and rebuild it only when a
conversation, tab, layout or owner input changed; request timing and
titles are unchanged.
* perf: look up saved titles once per pass and keep only request inputs
Index the request workspaces' saved titles once per pass instead of
searching a workspace's tabs per request, and keep only the store fields
the request list reads so an old snapshot doesn't pin unrelated data.
* fix: read a request's saved title from its own workspace
Two workspaces can hold the same tab id; key the per-pass lookup by
workspace and tab, keeping the first match like the per-workspace search.
* chore: build title request inputs from same-name copies
The layout-writer ratchet reads field-name string lists as computed-key
writes; spell the picked inputs out instead. Also apply formatting.
* chore: move title request inputs to their own file and read workspace records via selectors
* fix(agent-session): resend a chat's first snapshot when its capture is abandoned
A subscriber opened without a cursor gets a snapshot first. When live
authority moved during that read (a hand-off finishing, a start going
live), the capture was abandoned and the following delivery sent batches
from sequence 0 instead, so the client never received the conversation
and stayed empty. The subscriber now owes that snapshot until one is
emitted, and the next delivery sends it.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* test(native-chat): pin the owed snapshot after an abandoned capture
The opening snapshot's authority changes mid-read, so its capture is
abandoned; the next delivery must send that snapshot before any other
frame. Without the owed-snapshot check the client's first frame is a reset.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* test(native-chat): a chat store from before revisions were kept keeps its tabs on upgrade
* fix(native-chat): an upgrade no longer reopens closed chats or copies unchanged ones
A chat store copied by a build from before revisions were kept reopened every
closed chat and copied every converted one on its first launch after #42783,
with nothing written by an older Orca.
- The original's receipt is compared by meaning: a receipt saved before WAL
identity was kept matches on the fields it has, so the newer shape alone is
no write.
- A chat with no revision here takes what this file shows as its baseline. A
converted chat is kept as a copy only when the original holds an item it
never saw; one not converted yet converts from the current original. Only a
chat this file doesn't know joins, and only when the original changed.
- So only a chat an older Orca started or positively continued gets a tab;
every other chat keeps its open or closed state.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix(native-chat): tell a continued chat by its restored history, not raw rows
An older Orca saves a chat's turns as outcome records, and a rewind can retire
an alias, so a converted chat's raw journal rows are not what it shows. With no
revision to compare, a converted chat is now kept as a copy only when its
restored history, as conversion reads it, has an item the chat here never
held; nothing depends on save timestamps. An original whose identity can't be
certified records its baselines instead of rereading every launch.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix(native-chat): an original as copied takes every chat as shown
With no write since the copy, a converted chat this store moved on can't be
mistaken for one an older Orca continued, and the pass restores nothing. The
test of a store from before revisions were kept now checks that its copy saw
the original's WAL, as in the reported profile.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix(native-chat): keep deleted empty chats deleted and finish a partial pass
- On a store copied before revisions were kept, every chat with history was
cataloged at the copy, so only one with history is new when this store
doesn't know it; a deleted chat with no history stays deleted.
- A converted chat counts as continued also when the older Orca revised an
item past the revision it holds.
- A pass where one chat failed still records the baselines it read, so only
that chat is retried next launch.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix(native-chat): decide unknown chats by the copy's catalog alone
A chat with history always has a catalog row from the copy and one without
history has no revision, so the record lookup added nothing. The downgrade
test's original records its tab index, as every older Orca that saves tabs
does.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* style: format
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* Remote sender updates rejoin only their host and notify only the cards they move
With paired hosts, every remote agent-sender scope update rebuilt the window's whole sender index, including every unchanged local row, and every mounted sender label re-ran its store selectors on every store write; the sender-locations channel told every card to re-resolve.
The index is now partitioned: each publication is joined to this window's panes once (per alias change), each host's part is rebuilt only when that host's scopes change, and a sender's answer is resolved on demand from the host parts, with the cross-host principal/attachment joins and the pane-owner collision check read through reverse pane maps. A publication update notifies only the subscribed sender channels whose answer it moved; tab, owner, handle and publishing-host changes still notify every card. The label reads through the same leased selector as the avatar and link.
Resolution is unchanged: an equivalence test checks every sender against the old whole-window rebuild over random local and remote scope updates, cross-host joins, ambiguity and aliased chats.
* Build the sender label's selector outside render
* Type the equivalence test's hosts without the moved execution-host module
Some installers write a literal `~/...` entry to PATH (e.g. the macOS .NET
installer's /etc/paths.d/dotnet-cli-tools). observeChatProgram treated it as
workspace-relative and reported every uninstalled chat program as `unknown`,
so the new-tab menu showed "Couldn't check chat availability" instead of
"Not installed" or the setup chat. execvp/libuv never expand `~`, so bare `~`
and `~/`/`~\` entries no longer force workspace resolution; other relative
entries still yield `unknown`.
Fixes#43184
Co-authored-by: Neil <neil@stably.ai>
The tray read the chat's MCP servers once when it opened. Opened while the agent was at rest, it said "Connect when you send your next message" and kept saying it after the agent started, and running /mcp again on the open tray did nothing. The tray now re-reads when the host reports the agent starting or stopping and each time /mcp runs, on desktop and mobile. A read asked for while one is in flight now runs after it instead of being dropped.
Expo Router decodes query params twice, so a WSL runtime host id such as
runtime:wsl%3Aubuntu-22.04 reached screens as runtime:wsl:ubuntu-22.04 and
never matched the desktop host catalog, leaving the workspace on the
offline screen. Read the route executionHost through a shared
canonicalExecutionHostId that re-encodes runtime and SSH targets, and use
it in the workspace route, notification viewing state, and web page
location readers.
Fixes#43160
Co-authored-by: Neil <neil@stably.ai>
Child-agent and idle-group disclosures pointed up when expanded while the
agents group header (and other sidebar trees) point down when expanded and
right when collapsed. Rotate the child disclosures the same way.
Fixes#43169
Co-authored-by: Claude <noreply@anthropic.com>
Spawn the status helper directly instead of through LaunchServices, and have it re-exec itself as its own responsible process so TCC still checks the helper's grant. A timeout now stops the probe by PID, so a late LaunchServices launch can no longer leave a suspended helper behind. Startup kills suspended probes left by older builds.
Co-authored-by: Mikel Vallejo <58292517+VallejoM@users.noreply.github.com>
The Windows helper checked an agent's --window-id against Process.MainWindowHandle, a z-order guess that moves to a tooltip or another window of the same app. The window id is now the target: a live, visible top-level window of the target process, carried through the tree read, frame, screenshot, raise, keyboard input and the observe after the action.
Co-authored-by: toodeceptive <137078450+toodeceptive@users.noreply.github.com>
On Android, React Native reports the keyboard height as the IME inset
minus the system bars, but fill-height bottom drawers sit in an
edge-to-edge window that reaches under the navigation bar. The sheet
therefore stopped one nav-bar height short and the keyboard covered the
Start from field. Add the bottom safe-area inset back for Android fill
sheets, clamping after the sum so a floating IME never lifts the sheet.
Fixes#43127
Selecting, removing, or adding a managed Codex account from the CLI or a
paired phone updated settings without notifying listeners, so the desktop
status bar kept naming the previous account over the new account's usage.
Route every Codex selection write through CodexAccountSelection.saveSettings,
which passes notifyListeners: true, matching the Claude side.
Fixes#43107
Co-authored-by: Neil <neil@stably.ai>