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>
* Give new agents plain UUID IDs
New Orca session IDs (chats, host-launched chats, terminal agent IDs) are
plain random UUIDs minted by createOrcaSessionId; the agent stays on the
record. Remove the two readers of the agent prefix: the agent.launch
sessionId refinement and the automation Open run guard. Hosts advertise
agent.launch.plain-session-id.v1; the phone reserves a plain ID only for
hosts that advertise it and keeps the legacy spelling otherwise. A replay
an older replacement host refuses as invalid params is now uncertain, not
a definite failure. Old IDs stay valid; nothing is migrated.
* Repair plain agent ID recordings and compatibility checks
* refactor: place shared settings profiles and host contracts with owners
* fix: retire stale cleanup validation contacts
* refactor: consolidate imports from concrete owners
* refactor: bind new card fixture to profile defaults owner
* style: format rebased concrete host import
* refactor: consolidate project header color owner imports
* fix: load released phone readers after folder moves
* fix: preserve released chat readers and current owner imports
A failed queued delivery (catch-up read, frame capture, work projection)
dropped the subscriber without ending its stream, so the client never
resubscribed and the structured chat froze. Route both delivery-failure
paths through one guarded drop-and-end that skips subscribers already
replaced by a same-id successor.
Fixes#43030
Co-authored-by: Neil <neil@stably.ai>
Co-authored-by: Hayden Flinner <14845292+haydenflinner@users.noreply.github.com>
v1.4.260 moved mobile/src/worktree/agent-row-display.ts under agent-lineage/
and was the first release to keep native chats in SQLite behind worker threads.
- Archive both phone row reader locations as optional paths and resolve moved
modules under mobile/src through releaseModuleLocation().
- Bundle each SQL-backed release's own journal worker/reader entries and mock
its worker-bundle fixture to point at them; read those releases' chats with
their own readTestJournalSnapshot instead of journal.snapshot().
* refactor: give chat tabs ownership of composer editors
* Retain pasted-text file paths with composer undo history
* Keep composer selection ownership with its editor
* perf: suspend hidden structured chat effects with Activity
* fix: keep pending chat actions independent of view replay
* Preserve hidden chat handoff and pending host actions
* Keep autocomplete ref writes in their owning hook
* Preserve disclosure geometry and pending images across chat reveals
* Use the native Blob implementation for image lifetime coverage
* Retain sent messages while hidden chats await history
* Wait for the held send request before hiding its test pane
* Preserve pending host reconnect state across chat switches
* Reset retained outage state after a hidden host recovery
* Observe retained chat outage transitions through shared host subscriptions
* Start outage observation for initially hidden chats
* Keep chat feedback timers alive across hidden views
* Settle the retained rail while its view ref is disconnected
* Track the rail node lit by the latest wake
* Preserve the lit rail when hidden input has no view node
Ships #43080: GitHub installs outside mainland China are steered to Google Play
for updates. Built with Play's automatic protection off, like 0.0.66.
Co-authored-by: Claude <noreply@anthropic.com>
A sideloaded dev.orca.app now opens the Play listing from its update card, the
Settings update row and the "update required" screen when the device is not in
mainland China (no CN language region and no mainland time zone) and the Play
Store app is installed and enabled. Play updates the install in place because both
carry Google's signing key. Mainland China keeps GitHub, since Play is unreachable.
Play installs and the retired app are unchanged.
Co-authored-by: Claude <noreply@anthropic.com>
README, its translations and the mobile docs now send Android readers to the Play
listing first and keep orca.dev/download/android as the APK fallback. The
Simplified Chinese README keeps the APK link only, since Play is unreachable in
mainland China.
Co-authored-by: Claude <noreply@anthropic.com>
* feat(jira): reorder the Tasks board lanes by dragging their headers
Jira's board configuration decided the lane order and there was no way to change it in Orca. Column headers are now drag handles, with ArrowLeft/ArrowRight as the keyboard equivalent, and the resulting order is saved per board on the device. Jira's Agile API exposes board column order read-only, so this is an Orca view preference and never edits the Jira board.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix(jira): make the saved lane order survive Jira column inserts and filtered lanes
Review follow-up. Board column keys were derived from the column index, so inserting a column in Jira orphaned every saved lane position; they now come from the column's status ids, which Jira keeps stable across config edits. Saving a reorder also replaced the stored order with only the lanes currently on screen, dropping the saved position of any lane a filter had hidden; the new order is merged into the saved one instead. A keyboard move now restores focus to the lane it moved, and the rendered probe asserts two arrow presses in a row land.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix(jira): tell screen readers a lane's issue count and its arrow-key move
Review follow-up. The lane header's aria-label replaced the visible header text, so assistive technology no longer heard how many issues the lane held, and nothing said the header moves with the Left and Right arrow keys. Both now ride on aria-description, translated in every catalog including the newly added Portuguese one, which also gains the existing reorder label.
Also registers the lane-order storage module in the WSL-move localStorage inventory, as the sibling view-mode change did, and follows the jira-types move on main.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(jira): keep the saved lane order across a runtime reconnect
Review follow-up. The lane order was stored under the status-order cache key, which ends in the provider runtime session generation. That counter restarts at zero on every launch and moves on every runtime focus change and remote session start, so a reconnect or a relaunch read the order back under a different key and silently fell back to Jira's order.
The storage key is now built from the task source, the owner's identity without the generation, and the Jira project. The generation-free identity is split out of getEnvironmentRuntimeContextKey rather than duplicated, and the status-order cache keeps its generation.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Neil <neil@stably.ai>
* test(acp): cover temporary restore recovery and cancellation
Co-authored-by: outworkAnton <anton.mazurov@reksoft.com>
* fix(acp): preserve saved conversations through temporary restore failures
Share temporary provider-answer classification and bounded abort-aware retries. Isolate each load attempt so partial failed replay cannot enter successful history catch-up.
Co-authored-by: outworkAnton <anton.mazurov@reksoft.com>
* fix(acp): end automatic startup after the restore retry budget
* test(acp): use the advertised resume preference type
* fix(acp): retry temporary moved-session lookup failures within the same flight
---------
Co-authored-by: outworkAnton <anton.mazurov@reksoft.com>
With "open links in Orca" on and an SSH host's browsing set to "This
device", links from SSH and managed-SSH workspaces (terminal, native chat,
markdown, dashboard preview, app links) skipped Orca's browser and went to
the system browser, even though New Browser Tab already opened a desktop
tab in that workspace.
canOpenRemoteLinkInWorkspaceBrowser now owns the remote-link rule in
lib/browser and passes allowSshDeviceBrowser (only while links open in
Orca) to the SSH route predicates, and executeHttpLink forwards the same
flag to openWorkspaceBrowserTab. Ports, links-in-Orca off, modifier
escapes, paired runtimes, WSL and local links are unchanged. The managed
SSH egress indicator now shows "Browsing from this device".
Fixes#41586
Co-authored-by: Neil <neil@stably.ai>
* fix(plugins): re-fetch the catalog before an update preview
Check for update on a plugin previewed against the cached catalog, so a
release published since the last fetch showed as 'X -> X, already
installed'. The update preview now refreshes the plugin's own catalog
first (one fetch shared by a multi-plugin review), falling back to the
cache when offline.
* fix(plugins): refresh from the lock entry's catalog, so a lost listing still refreshes
* ci: retrigger PR checks
First Android release built with Play's automatic protection turned off, so the
APK no longer carries the license check that closed the app when Google Play is
unavailable (#42973).
Co-authored-by: Claude <noreply@anthropic.com>
* feat(notifications): mute notifications per worktree
Add a per-worktree notification mute, toggled from the worktree context
menu. Muting silences the interruptions for that worktree (OS banner,
notification sound, mobile push, tray attention dot) while keeping the
passive unread indicators, and shows a small bell-off icon on the card.
The flag is stored in PersistedUIState as notificationsMutedByWorktree
(opt-in entries only), riding the same rails as showDotfilesByWorktree:
debounced writer baseline, hydration sanitizer, paired-client UiUpdate
schema, worktree delete cleanup, folder-rename re-keying, repo removal
pruning, and profile transfer.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* docs(notifications): document the touched per-worktree flag helpers
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* fix(notifications): adapt the mute gate to the attention-sink and WSL-move ledgers
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: Neil <neil@stably.ai>
A sender with no active Dispatch (for example a coordinator) that sends
--type escalation or decision_gate is refused with sender_not_assignee,
but the rewritten "Rejected ..." row was still delivered to the recipient
as unread mail and woke it, including on idempotent retries via the
replayed receipt nudge. Nobody can act on such a refusal, so keep the row
for audit but mark it read, record the receipt without a replay nudge,
and skip the wake. Refusals tied to a real Dispatch still reach the
coordinator. The refusal text now points the sender at --type status or
gate-create.
Fixes#42731
Co-authored-by: Neil <neil@stably.ai>
Co-authored-by: Shaukat Ibrahim <shaukati@amazon.com>
* refactor: give chat tabs ownership of composer editors
* Retain pasted-text file paths with composer undo history
* Keep composer selection ownership with its editor
* perf(mac): reuse verified terminal names across process-table captures
Each full macOS process-table capture ran one lstat per terminal on the
machine. On busy Macs that is millions of libuv pool jobs a day in the
terminal daemon, which is the load that wedges macOS's pool and makes
createOrAttach time out (#31926, #42958). Verified ttys names now last 60s;
misses and /dev scan aliases are still read live.
* perf(mac): keep verified terminal names for five minutes
Closed ptys stop reporting their device, so the TTL is only a safety
margin; a longer one removes the largest remaining pool-job source.
Play Console's automatic protection injects com.pairip's license check into every
APK Play generates, including the universal APK we republish on GitHub. On phones
where Google Play is disabled or unreachable (mainland China) the check shows
"Something went wrong ... Check that Google Play is enabled" and closes the app.
download_signed_apk now fails before the GitHub release when the APK's dex carries
com/pairip/licensecheck, and the README says to keep automatic protection off.
Co-authored-by: Claude <noreply@anthropic.com>
* fix(chat): keep replies before a mid-turn message visible in folded turns
A person's message is a boundary that keeps the reply before it, and
back-to-back replies stay visible, matching the common pattern for
completed turns. Tracked in #41393.
* fix(chat): fold a reply followed by its own tool work, judged within its turn
Tool-only rows merge into the reply before them, so a reply row that
draws tools is followed by work, not by the next reply. Adjacency is
judged within each turn, and orphaned tool results are not a person's
boundary.
* fix(chat): keep generated-image operations out of back-to-back replies
A generated-image row stripped of its preview still carries its
operation label; it is work, not a spoken reply.
* fix(chat): fold Codex image views and image status lines as work in finished turns
Codex's "Viewed image" rows and image-status lines ("Image generation failed", "preview unavailable") were stored as plain assistant text, so a finished turn counted them as replies and kept them, plus the sentence before them, visible. The Codex producer now marks them as image operations when it writes them, the same way it already marks generated images, and the fold treats them as work.
Tracked in STA-14968.
* fix(chat): keep response actions on the reply, not an image operation; tighten interleaved-turn fold test
* fix(browser): free hidden pages based on the current page only
Earlier back/forward entries no longer keep a hidden browser page alive. Edits,
child frames, audio, picture-in-picture, PDF, capture and file/document URLs on
the current page still protect it; freed pages restore their history as before.
* fix(browser): keep a hidden page whose current document is a POST result
The freed record keeps only URLs, so reopening a POST result would load a
different page by GET.
* fix(browser): restore scroll and form contents when reopening a freed page
Keep Chromium pageState in the in-memory freed-page record so reopen and
Back restore scroll position and form contents. It is never persisted,
logged or sent over IPC, and is dropped when the page closes or restores.
* fix(browser): drop a closed page's freed-page record immediately
* fix(browser): reset background-activity protection when a new document commits
* fix(browser): keep the favicon baseline across commits
* fix(browser): keep title and favicon baselines across commits
* fix(orchestration): count an approved terminal prompt as answered while its tool runs
* fix(orchestration): a deny counts as answered only once Claude records it
* test(orchestration): stop ticking once the slow allow is answered
* perf(orchestration): prune settled chat output copies and reclaim orchestration.db space
Background maintenance rewrites chat workers' saved output copies of Runs settled over a day ago
to the reference later releases store, every six hours at a tenth of the thread, and returns
free pages in bounded steps once the file uses incremental auto_vacuum. New databases start
that way; Settings > Agent orchestration can restart Orca to rewrite an existing one.
* fix(orchestration): prune only copies whose chat is readable here, in bounded pages
Pages now examine a fixed window of archive rows and check each Run once, so a large Run
cannot make one slice quadratic. A copy whose chat this host cannot read stays. The restart
rewrite keeps its temporary copy on disk and records a failure for Settings to show.
* fix(orchestration): check chat readability without re-registering released workers
The readability probe builds the identity from the durable row instead of rehydrating it into
the live registry. Free-space checks use SQLite's own temp folder; a page's Run verdicts are
shared across a pass; a failed failure record no longer hides the VACUUM error.
* chore(orchestration): annotate prune casts, follow Button spacing, sync the runtime catalog
* chore(i18n): resync the runtime English catalog after rebase
* fix(orchestration): share Run verdicts across a prune pass; check the temp drive SQLite uses on Windows
* perf(orchestration): compact legacy storage during update shutdown
* test(orchestration): mock filesystem space checks through ESM factory
* Align update maintenance checks with shutdown-only work
* Drop the one-time update VACUUM; keep prune and incremental reclaim
Existing non-incremental orchestration databases stop growing because freed
pages are reused; nothing shrinks them automatically.
* Launch provider CLIs without a per-chat runtime supervisor
* Initialize process-owner fixtures with an isolated app environment
* Retire provider output transports and failed ownership drafts
* Finish provider stops when the session group empties
* Complete native cleanup from verified watcher exit and cancel held launches
* Let native watcher finish one-shot provider exits
* Retire late ownership records after canceled provider launches settle
* Reap each provider subtree in an isolated native parent
* Preserve provider outcomes and compatibility with native parents
* Publish actual provider identities and retire native parent observers
* Retire numeric writer PIDs when their group is proven absent
* Retire provider transports and accept proven group absence
* Fence retired process identities across asynchronous cleanup
* Use native timer types and readonly process fixtures
* Reuse bounded timeout for compatibility output drain
* Release launch scopes held by late transport error handlers
* Keep processless launch failures out of watcher waits
* Align lifecycle validation with final ownership contracts
* Remove duplicate helper preparation from the dev launcher
* Keep legacy fallback in place and simplify native ownership handoff
* Defer background provider maintenance until the first window
* Release startup hook maintenance for terminal launches
* Use relocated artifact module in native prebuild scripts
* Preserve agent failure outcomes and clean tools before ownership is lost
* Budget ownership capture for its bounded identity reads
* Keep lifecycle regressions at their behavior-owning seam
* Explain the fake-clock process-read fixture
* Capture tool ownership before restart recovery removes the CLI
* Skip descendant inventories for absent provider roots
* Make final output drain regression test deterministic
* Keep output drain fixture assertions type-safe with IPC
* Use existing provider fixtures across Node and Bun
* Prepare native provider helper for Codex contract CI
* Verify provider ownership using its recorded start precision
* Preserve exact provider ownership through reader failures
* Retire exhausted recovery records without blocking watcher cleanup
* Distinguish exited descendants from unreaped zombies
* Preserve group retirement without trusting an exited root
* Keep CLI input owned through native parent loss
* Keep watcher cleanup proof through lost-parent retirement
* Guard retirement against late watcher cleanup proof
* Contain provider launches that fail before stdio setup
* fix(claude): preserve startup diagnostics after input pipe failures
* fix(provider): capture lost outcomes before native completion cleanup
* fix(provider): retire speculative captures after a valid outcome
* fix(provider): share spawn absence classification through its existing boundary
* fix(sidebar): keep delete dialog height stable and show full ignored-files list
* Replace delete dialog file popovers with inline collapsible sections
The unrenamed local host label ("Local Mac") and the four restart
continuation notes the host journals in English stayed English in every
UI language.
selectExecutionHostDisplayLabel and the automation host labels now
resolve the local host through the translated label, and desktop and
mobile notice rows map the exact English restart-note text to catalog
keys at display time, so saved chats and older servers read translated
too. Renamed hosts still show as typed.
Co-authored-by: x-Ai <5061489+x-Ai@users.noreply.github.com>
Co-authored-by: Neil <neil@stably.ai>
Add 361 desktop and 633 mobile translations for English keys that still
fell back to English: workspace cleanup, the MCP server panel and sign-in
requests, subagent views, automation runs, worktree cards, Memory Saver,
account rename, PR updates and the freeze report on desktop, and most of
the mobile pull request, source control, tasks, agents and session screens.
Mobile code often calls a plural key literally as t('key_one') when the
count is 1, and i18next looks that key up as written, so zh showed English
for a single item. Add the explicitly called _one keys, each equal to its
_other value.
Also correct two browser search keywords that rendered cookies as 曲奇饼,
and entries that called archive scripts 存档 where the catalog says 归档.
The worktree cards "New" badge keeps 新功能 via a key override, mobile
"Start workspace" matches the desktop wording, and an automation's Active
status and list group read 已启用 (paired with 已暂停) instead of 当前.
Co-authored-by: x-Ai <5061489+x-Ai@users.noreply.github.com>
Co-authored-by: Neil <neil@stably.ai>
Windows OpenSSH (seen with OpenSSH_for_Windows 9.5p2 behind a ProxyCommand)
can keep ssh.exe alive after the remote command exits while its stdin pipe
is still open, so connects and orcad installs stall until the 30s timeout.
spawnSystemSshCommand now takes a closeStdin option that ends the child's
stdin right after spawn, and SshConnection.execWithClosedStdin routes
no-input commands through it. The connect probe, loopback route probe,
cat download, Windows no-stdin commands, remote folder browse, SSH
automation prechecks, and execCommand without stdin all use it.
Fixes#38636
Co-authored-by: Neil <neil@stably.ai>
Electron can settle loadURL on the outgoing document's own events: a
beforeunload replaceState (vue-router 4 saves scroll this way, as on a
GitLab project home page) or the old page finishing its load. goto then
returned and notified the renderer with the previous URL, and the
renderer navigated the tab back to it.
When the requested URL has not committed and a main-frame navigation is
still pending, goto now waits for the committed main document's
did-finish-load (subframes ignored), the same point a normal load
returns. Reaching the deadline on that path reports the current page
instead of failing; the aborted-navigation path keeps its timeout error.
Fixes#42983