The test polled for the compact turn's 'completed' state with vi.waitFor's 1 s
default while the completion committed through the child's event sink; on a
loaded runner (two CI runs) the commit outlasted the budget. It now flushes
the sink and checks once.
Co-Authored-By: Claude Opus 5.5 (1M context) <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
* feat(uninstall): add the uninstall cleanup contract shared by main and the settings UI
* feat(uninstall): remove Orca's OpenCode and Pi plugin files, also from the Windows uninstaller
Only files carrying Orca's marker are removed; OpenCode 1.x's TUI registration entry goes with them.
* feat(uninstall): main-process plan, steps and finish actions for Uninstall Orca
getPlan lists agent hooks, the orca command, orca serve units, ~/.orca/agent-hooks and SSH hosts
without changing anything; runStep removes one part and returns the updated plan.
* feat(cli): add orca uninstall, sharing the app's cleanup
* feat(uninstall): add the Uninstall Orca section to Settings → Advanced
* fix(uninstall): narrow plan agent ids with isTuiAgent instead of a cast
* fix(uninstall): show home-relative paths in the uninstall plan
* fix(uninstall): bound the SSH host sub-list with useBoundedHostRows
* fix(uninstall): async fs on the main thread and no type assertions in the cleanup
* fix(cli): bundle the uninstall cleanup modules the orca uninstall command loads
* fix(packaging): unpack the uninstall cleanup entries the packaged CLI loads
* fix(uninstall): call the orca command row the CLI on your PATH
* fix(uninstall): show hook scripts under the agents' hooks row
* fix(uninstall): remove hook scripts after the last agent retry and never show kept items as done
* fix(cli): give orca uninstall and agent hooks an app environment, and exit 1 on unfinished entries
Claude's remover resolves profile homes through it; without one the CLI reported Claude failed.
* fix(uninstall): drop Muse's Orca env-var allowlist and Claude's agent-view marker
Muse keeps names the user added. The agent-view marker only remembers opt-outs for a re-enable.
* fix(cli): bundle and unpack the node service environment orca uninstall loads
* fix(uninstall): settle the agent-view disable before deleting its marker, and report ok:false on unfinished --json runs
* feat(languages): discover and switch community language packs
Show community translations where people choose a language: in the
Settings language dropdown (with a link to the translations catalog), a
single-list language picker that pins the device-matching translation,
a Language button in onboarding, and a one-time quiet suggestion toast.
Switching back to the previous language is always available in English.
* style: format language browser imports
* fix(languages): keep the offer action hook compilable by React Compiler
* test(e2e): drive language catalog retry through the new picker
When a visible terminal read waits 750ms for a provider frame and times
out, hold the per-PTY visible retry gate shut while that capture is still
pending, so later visible reads return the fallback at once instead of
rejoining the same slow request. When the late frame lands in the same
PTY generation, adopt it into the visible-state cache (or re-arm the
normal backoff if it is null or stale).
The shared provider acquisition is not retired, so headless re-seeds,
restore/serialize callers, and mobile authoritative reads keep waiting
on a slow but healthy capture as before.
Fixes#16531
Co-authored-by: Neil <neil@stably.ai>
* fix(native-chat): make Skip and agent messages agree with the async question card
Skip on a Codex async question card now saves the skipped row on the chat's host
record (agentSession.skipAsyncQuestions, modelled on cancelUsageLimitContinue), so
the status, the desktop card and the phone card all honour it. The host status read
no longer ends at another agent's message, matching the card's rule from #35758;
two partial indexes, created without a schema version bump, keep that read bounded.
* fix(native-chat): gate phone Skip on relay support; roll back only its own hide
* perf(worktrees): patch heads on HEAD-only watcher bursts instead of re-listing
* fix(worktrees): fall back to re-list for headless or absorbed HEAD moves
* test(worktrees): cover orphan HEAD re-list fallback
* fix(worktrees): keep orphan fallback through merged scopes and patch hidden rows
* fix(worktrees): guard hidden-row head patches against stale listings and other hosts
* chore(worktrees): read detected rows through the selector; document test window cast
* chore(worktrees): read detected rows only through the selector
* fix(worktrees): skip the concurrent-head guard when no patch landed; keep pinned names on reattach
* Share Codex account history through folder links into ~/.codex
Each Codex account home keeps its login; its history folders become folder
links (junctions on Windows) into the user's ~/.codex, and Codex's databases
follow through a sqlite_home line in the account's own config. Migration is
automatic before the next launch in each home; the store's copy wins a name
conflict and the account's copy is kept beside it. The per-file history bridge,
its link pass and the WSL bridge are removed. Claude's merge-then-link moves to
a shared async module both providers use.
* Make account history moves safe under concurrency and keep the DB with the folders
Files move by link-then-unlink so a move never replaces an existing name, host
passes run one at a time per store, index markers are written before a move,
account-only folders are shared, lock folders are moved rather than deleted,
and sqlite_home is written only once a home's sessions are linked.
* Let the history pass own sqlite_home, link locks first, and index per store
The pass that links a home's folders now writes and removes its sqlite_home
line; the config mirror only carries it forward. thread-writer-locks is linked
before any history, index markers are kept once per store (hard-linked
duplicates included), WSL links the launched home before Codex starts, passes
queue per home in request order, and re-sharing after off then on works with
earlier conflicts still kept.
* Never overwrite on move, gate indexing on moves, and read the shared DB for backfill
Files move by link or exclusive copy; repeat conflicts get their own pending folder; secrets and
sandbox setup stay per home; the sqlite_home write retries against a concurrent mirror; indexing
waits until no move is running; backfill checks read the DB where sqlite_home puts it.
* Keep live writers' files, require both history links, and keep unmoved history on removal
Files move only by a new name for their inode; a home is shared only when sessions and
archived_sessions both link; reverted-thread rollouts get index markers; settled homes skip
repeat passes in either mode; account removal keeps a real history folder.
* Give resume test runtime-home mocks the account history step
* Keep unmoved WSL history on removal, prepare the launched home, and retry incomplete work
WSL account removal keeps real sessions/archived_sessions; a launch prepares the account it
returns even if the selection changed meanwhile; an incomplete unshare and a failed WSL index
pass stay eligible for a later launch; the guest helper rechecks the distro before each step.
* Keep pinned resumes reachable, finish interrupted unshares, and keep index work from racing moves
A pinned resume only shares; a launch re-prepares when the selection or setting changed; Orca's
sqlite_home line is read only at the config root; a writer-lock link elsewhere keeps the home
private; an unshare finishes its database move on retry; indexing keeps markers a newer move
recorded, retries an incomplete run on a later launch, and merges WSL marker lists.
* Move account history into a store one pass at a time and retry incomplete moves
Two homes merging into one store at once raced on its folders and stranded the second home's
history in its merge folder. Passes now run one at a time per store (host) and per distro (WSL),
a folder that appears mid-move is merged into, and a share with failed moves is not settled.
* Keep one rollout form in ~/.codex, record what sharing left behind, and guard Windows homes from older builds
- A rollout present as .jsonl and .jsonl.zst lands in the store in one form only; the other form moves to the home's .orca-set-aside-rollouts, never deleted.
- Each account home gets a versioned cleanup manifest: set-aside databases, left-behind rollouts with a background content check against the store, store twin pairs, and the shared streak.
- Native Windows homes get a renamed ownership marker before their first junction, so older builds refuse to use or delete them.
- Account removal keeps the set-aside rollouts and the manifest.
* Set a rollout form aside only beside its twin in the store, inventory leftovers off the launch path, and keep account databases on removal
- The .zst moves first and a form is kept out only when the store already holds its twin, so a failed move never leaves the store with neither form.
- The rollout inventory and store twin walk run in the detached check, not the awaited pass; manifest writes are serialized per home and a check applies only to unchanged files; checkpoints are time-spaced.
- A WSL check that runs out of budget resumes on a later launch instead of looping.
- The ownership check reads either marker in one step and the marker rename retries on Windows.
- Account removal keeps the account's Codex databases for the later cleanup release.
* Read the cleanup manifest through a type guard
* Read the cleanup manifest through a type guard over unknown
* Settle only a check's own request, skip queued WSL passes after quit, and validate manifest entries
- A pass finishing during a check keeps its new check request on host and WSL.
- A WSL pass queued before quit no longer starts guest work.
- Manifest rollouts must carry a path, size and mtime to be read.
- The store twin scan reuses the twin module's folder walk.
* Walk the store outside the manifest write and keep databases on removal only for shared homes
- The inventory writes only its own fields onto a freshly read manifest, so it never undoes a streak reset from another process and a launch never waits behind the walk.
- Account removal keeps the home's Codex databases only when the cleanup manifest shows the home was shared.
* Lock the cleanup manifest across processes and validate every field later passes read
- Manifest writes take a file lock, so a WSL check helper can't publish over another helper's streak reset.
- The guard also checks storePath, the content check's store facts, database entries and sharedPasses; anything else is rebuilt from disk.