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>
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>
* 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
The docs layout mounts two SearchTriggers (sidebar and mobile nav), each
with its own window keydown listener, so Ctrl/Cmd+K opened two
SearchDialogs. Their body scroll locks restored out of order, leaving
body overflow stuck at 'hidden' after closing. Route the hotkey to the
first visible trigger so only one dialog mounts.
Fixes#42903
Co-authored-by: Claude <noreply@anthropic.com>
* fix(computer): click macOS windows that refuse focus with --restore-window
A raised window that never becomes the focused window (Archicad's CEF start window) failed every --restore-window click with window_not_focused, because the click fence required the target to be focused as well as topmost at the point. A real click reaches the topmost window whether it is focused or not, so when the target stays unfocused the click now goes ahead while the target is topmost at the point, and is refused before anything is sent when another window covers it. Afterwards the app the user had in front comes back if the raise or the click left the target app in front without the target window.
* fix(computer): restore the front app only after a click on a window that refused focus
* fix(computer): keep the target app in front when an unfocused-window click opened something
* fix(computer): count small popups and re-read the front app last before restoring it
* feat(computer): add opt-in flags for smaller computer-use screenshots
Every observe and action screenshot came back as a full-resolution PNG, so a Retina window cost about four times the pixels it needed. --screenshot-scale caps pixels per window point, --screenshot-max-edge caps the longer side, and --screenshot-format jpeg re-encodes it, on macOS, Windows and Linux. Defaults are unchanged.
* fix(computer): treat requested screenshot sizes as ceilings and skip repeat encodes
* feat(computer): list macOS apps without a Dock icon while they show a window
list-apps on macOS only listed regular apps, so menu bar and other accessory apps could not be found or targeted by name. Accessory apps are now listed while they own an on-screen window between the normal and status bar levels, which keeps the dozens of windowless system agents out, and each listed app says whether it is an accessory app.
* fix(computer): list only normal-level accessory windows and resolve hidden accessory apps
* fix(computer): prefer a same-named regular app when resolving, not in the list order
Align the Windows update harness docs and CLI help with the implemented
cold-restore/survival profiles, document the daemon-log reader, drop
links to unavailable plan/postmortem docs, and fix relocated script and
source paths in freeze-repro, process-host, and crash-survival docs.
Remove stale French Windows RC claims in favor of the stable latest asset.
Fixes#42765
Co-authored-by: Neil <4138956+nwparker@users.noreply.github.com>
* refactor: group process and platform modules by ownership
* refactor: preserve moved module workflow routing
* refactor: preserve native loader and embedded bundle origins
The appearance methods first shipped in v1.4.251 and editor.readTypography
in v1.4.257, so a plugin requiring the old floors installed on Orca that
lacks them.
* feat(plugins): check host API calls against released Orca at validation
orca plugin validate and pnpm validate:plugin now read the literal host
method names a plugin's worker, panel and editor code calls, and report
methods this Orca does not have, proposed methods, wrong-surface calls,
and methods newer than engines.orca (unless guarded by orca.host.has).
Deprecated methods warn with a stable 'deprecated host method <name>'
prefix. Adds the Host API minor to first-Orca-release table.
* fix(plugins): avoid host-call validation false positives
Guarded proposed and wrong-surface calls warn instead of failing, and an orca.api.minor comparison counts as a floor guard. Only host.call/has receivers count, comments are stripped, files are stat-capped and read through their real path inside the plugin, root-relative script sources resolve, and each file is read once.
* fix(plugins): keep has-guarded host calls as errors before orca.host.has existed
* fix(plugins): fail only certain host-call problems and bound the scan
Floor and wrong-surface findings are warnings, since guards and per-surface reachability are not visible to a text scan; unknown and proposed methods without a literal has guard stay errors. Read attempts, references per file and queued files are capped, has?.() counts as a guard, and HTML script and comment scanning is linear.
* fix(plugins): treat any orca.host.has call as feature detection for unknown methods
* build(cli): ship the host-call validation module with the packaged CLI
* feat(plugins): list any workspace's agents with agents.list({ workspaceId })
* feat(plugins): version agents.list workspaceId as host API 1.10
An added param is new surface a plugin must be able to require, so specs
gain paramsSince and api.minor counts it. Regenerates the declarative
typings the first commit missed.
* fix(plugins): report runtime failure codes for agents.list workspaceId
The param is 1.10, after the runtime failure codes, so a call naming a
workspace reports unavailable for a disconnected host; calls without it
keep action_failed.
---------
Co-authored-by: Neil <neil@stably.ai>
The Default profile's trash button was disabled whenever the profile had
no import record (`disabled={!profile.source}`). Clearing the jar resets
`source` to null, so the button locked itself after one use, and users
who signed in directly in Orca could never clear the default partition.
The button is now always enabled, labeled ("Clear default cookies"
tooltip and aria-label), and asks for destructive confirmation before
wiping the default partition. Strings are added to every locale.
Co-authored-by: Neil <neil@stably.ai>
* fix(computer-use): put the macOS pointer back after --restore-window clicks, scrolls and drags
HID gestures left the user's pointer at the target. Save it first, and after a
200 ms settle warp it back unless it no longer sits where the last posted event
left it, which means the user moved it. The HID idle counter can't tell: posting
to the HID tap resets it too.
* fix(computer-use): keep the pointer where the user moved it during a macOS HID gesture
* fix(computer-use): save the macOS pointer right before the first HID event
* Use theme colors for active workspace selections
* Check dedicated upstream selection token overrides
* fix(theme): keep active sidebar accents legible
* fix(sidebar): preserve selected title contrast in card templates
* test(sidebar): require both active tool layouts in contrast fixture
* fix(theme): keep built-in sidebar colors and mark active tools with the tab indicator token
- Active right-sidebar tools keep the foreground icon; their top/side line uses
--tab-active-indicator, so plugin theme accents show while built-in themes
paint exactly as before.
- Restore main's tinted sidebar resolver: 0% tint is the app background again.
Themes that want their own sidebar colors use the Default appearance.
- Drop the resolver tests (main removed this file as low value) and keep the
fixture presentational.
* fix(theme): gate the active tool line on the sidebar and fall back to the foreground
- Check --tab-active-indicator against --sidebar too, since the same line now
marks the active right sidebar tool.
- The tool line falls back to --foreground (never --tab-active-foreground), so
themes without an indicator paint exactly as before.
- Mark the active tool with aria-current like the overflow menu; it selects a
view rather than toggling one.
* fix(fixtures): follow the activity bar move in the theme selection fixture
* docs(plugins): note the tool line's own fallback for the tab indicator token
---------
Co-authored-by: Neil <neil@stably.ai>
* feat(chat): tidy native chat text typography
Default chat text is 13px in the system UI font on 20px lines, with
paragraphs and list items sharing one line height, bold set by weight in
the body color, and the CI and opened pull request card headers at body
size. Labels, icons and spacing keep their earlier sizes.
* docs(chat): update the chat type scale; trim default-only typography tests
Pi's launch catalog now opts into launch-time model/effort preferences, so
`orca agent launch --agent pi` and `orca orchestration worker-start --agent pi`
accept `--model <provider/id>` and `--effort <level>` instead of refusing.
Pi models without a provider/id shape are refused up front, before a
worktree or worker is created. A new host capability,
`agent.launch.pi-model.v1`, lets the CLI refuse a Pi model/effort on older
execution hosts that would otherwise start Pi on its default model.
Co-authored-by: Neil <neil@stably.ai>
macOS Local Network caches one executable UUID per bundle id, and the terminal host shares the app's bundle id. With a UUID of its own the cache flips between the two, which blocked some connections and prompted again after an update. Give the host exactly the main executable's UUID per CPU type, and check that in packaging and after notarization.
Orca terminals run under the signed helper, whose executable was stock Node,
sharing its LC_UUID with every install of that Node build. macOS Local Network
privacy maps a responsible process to an app by that UUID, so terminals could be
attributed to another program and blocked from the LAN while Orca showed allowed.
Rewrite the helper executable's UUID during assembly (same scheme as #41676),
and fail packaging and the release check if it drifts.
Fixes#21988
* fix(computer): press, set and scroll Windows native controls without activating the window
Measured on Windows CI: UI Automation's Invoke, Toggle, ValuePattern and
ScrollPattern focus a background WinForms control first, which activates its
window. Native controls now go through their own messages instead, each
owner-checked: BM_CLICK for buttons, check boxes and radio buttons, select-all
plus EM_REPLACESEL for set-value on edits, CB_SETCURSEL with CBN_SELCHANGE for
combo boxes (exact-text match, read back after the app's handler runs) and
LB_SETTOPINDEX for list box pages.
* fix(computer): refuse read-only Windows documents before typing keys, document the caret fallback
* fix(computer): keep Windows native routes to measured controls and refuse partial writes
BM_CLICK only for WinForms buttons, multi-column lists stay on ScrollPattern, a
list already at its end reports success, edits refuse text past their limit,
the combo's owner is checked right before the selection, a cleared selection
reads as a mismatch and a disabled control is element_not_enabled.
* fix(computer): hold Windows edit limits without a readback, require a complete combo search
* fix(computer): read a long Windows edit's length from the field for its limit check
* test(computer): share the Windows fixture action helpers
* feat(computer): add launch-app to start apps without taking the foreground
* fix(computer): leave running apps alone and keep the launch env clean
* fix(computer): recheck aliases, keep focused launches visible, refine launch hints
* chore(computer): document the launch result casts
* test(computer): check launch-app reports where the app ended up on Windows CI
* docs(computer): point app_not_found at launch-app
* test(computer): format the merged Windows background e2e
* fix(computer): match launch paths to the running file and word background launch as an attempt
* fix(computer): type into Windows text fields without raising the window
Adds type-text --element-index on Windows through EM_REPLACESEL for user32,
RichEdit and WinForms edits (owner-checked, read back with WM_GETTEXT), or a
ValuePattern write merged with the TextPattern selection. Keyboard verbs on a
background window now refuse with background_unavailable before sending
anything and point at type-text --element-index. Foreground typing uses one
SendInput KEYEVENTF_UNICODE batch instead of WM_CHAR posted to the top-level
window, and get-app-state shows multiline edit text again.
* fix(computer): refuse typing into Windows list items, keep the caret on a confirmed prefix
* fix(computer-use): observe minimized, hidden and other-Space windows on macOS without a restore
macOS only enumerated on-screen windows and dropped minimized AX windows,
so an app whose window was minimized, hidden or on another Space (any
full-screen app) could not be observed, and agents fell back to
--restore-window, which activated every window of the app and switched
the user's Space.
Enumerate every window, keep the off-screen ones accessibility can still
read (other-Space windows by remote token, closed windows dropped by
their Space membership), and report their real minimized and off-screen
state. Background pointer and key input on such a window refuses before
sending anything. --restore-window now raises only the target window,
once per request, and delivery is measured from whether the target
became frontmost.
* fix(computer-use): pin the restored window and prefer visible windows by default
* fix(computer-use): keep window-index cache keys and stale-element checks across a restore
* fix(computer-use): restore only this app's resolved window and refuse a closed target before raising
* docs(computer-use): say macOS reads minimized, hidden and other-Space windows
* fix(cli): keep Orca in the background when orca open launches it
* docs(cli): say orca open leaves the foreground alone
* fix(cli): ask a running Orca to open its window in the background
* fix(main): keep background reveals inactive on Linux maximize and drop the flag on admin restart
* fix(cli): narrow the open status before returning it
* fix(main): keep focus-existing-window free of main-window contracts for the web typecheck
* fix(cli): cap the open window request at five seconds
* fix(computer): ask the user before retrying with --restore-window
Error hints, recovery steps, the skill guide and the CLI follow-up command
told agents to retry with --restore-window on their own, which raises the
target app and takes the user's screen. They now say to ask the user first,
stop recommending a restore just to observe, and fix stale per-platform
background claims.
* docs(computer): name the Linux keyboard gate and the Wayland limit
#41870 added hover/focus/press outlines to every Button, Toggle and
SelectTrigger, which read as noise on dense toolbar icon buttons.
Restore the previous focus-visible ring for those primitives and keep the
outline treatment only for buttons inside DialogFooter.
* fix(computer-use): refuse Windows pointer fallbacks without --restore-window
Coordinate, right, middle, modified and multi-clicks, clicks on elements with no
primary pattern, unscrollable wheel scrolls and drags raised the window and
moved the real cursor without being asked. They now refuse with
background_unavailable before anything is sent. Coordinate and fractional
scrolls go through ScrollPattern first. With --restore-window only the target
window is raised (never a cloaked one), with a UIA activation fallback and a
second attempt, points are validated first and the cursor is put back behind
the input. A failing UIA pattern or disabled element is an error instead of a
real click, and delivery is measured after the post-action observe.
* fix(computer-use): settle Windows clicks before restoring the cursor and keep scroll writes honest
* fix(computer-use): restore the Windows cursor with SetCursorPos and hit-test coordinate scrolls
* test(computer-use): assert Windows raise outcomes, not attempt order
* fix(computer-use): report a Windows page scroll the provider ignores as not scrolled
Add an on-by-default Claude usage polling switch with live-terminal-only behavior when disabled, cancellation and account attribution safeguards, and translations for all supported locales.
Fixes#27151.
Fixes#39502.
Fixes#37037.
Co-authored-by: Sibyl <scauyb@qq.com>
* fix(notifications): lift toasts and corner cards onto a shared notice surface
* fix(notifications): keep corner-card shadows unclipped and match the StarNag toast
* fix(notifications): keep the stack's scrollbar on screen and its overflow off the status bar
* fix(notifications): collapse stack shadow room while scrolling and paint lower cards above upper shadows
* fix(notifications): pair re-pointed surfaces with popover foregrounds and keep close-hover border
* fix(notifications): keep notice text readable on plugin themes and catch card growth in a capped stack
* fix(notifications): track stack cards from mutation records and tidy test types
* fix(notifications): check painted notice colors and outline unfilled secondary buttons
* fix(notifications): paint app-theme notice colors as the exact hex measured, with a one-step margin
* fix(notifications): keep muted panels on the notice surface's polarity for app themes
* fix(notifications): keep toast descriptions and outline buttons readable on notice surfaces
The surface lift now also keeps the 80% toast description blend readable, so
mid-gray dark popovers no longer drop descriptions under 4.5:1. The notice scope
remaps --background with --foreground, so outline buttons keep a dark surface
under light popover text in light-base themes with dark popovers.
* Give every Settings pane the same card structure
Settings cards that hold rows were built several ways (the non-grouped
SettingsSection px-7 card, shadcn Card, the Appearance accordion, one-off
bordered boxes), each with its own side padding and row inset. Every one
now goes through SettingsGroup: one 20px inset, rules between rows, title
outside the card. SettingsGroup gains an id, a collapse prop for the
Appearance groups, SettingsGroupSubsection, SettingsGroupNestedRows and
SettingsGroupDisclosure (the old Appearance advanced disclosure), plus
shared bleed classes for rows that span the card. The non-grouped
SettingsSection body is removed.
* Fix settings card typecheck errors
* Keep collapsible group headings valid and restore notification row padding
* Keep Chat names anchor on its group, toggle Appearance groups from the whole header, and steady the Machines row padding
* Show Appearance groups as plain cards and even the Computer Use card's top inset
* Restore the SettingsGroup subsection exports dropped with the collapse mode