Frames only got the colour tokens and --orca-radius, so a plugin panel could
not match a user's chosen app font. Add --font-sans and --font-mono to the
panel design token allowlist; the existing theme sync already refreshes frames
in place when the root style changes, so a font change now restyles them too.
Native chat visuals already listed both tokens and now get them from the
shared allowlist.
Fixes#42575
Co-authored-by: Claude <noreply@anthropic.com>
Without --worktree, a reuse start resolved the caller's workspace and was refused with terminal_worktree_mismatch whenever the terminal lived elsewhere. An explicit --worktree keeps today's behaviour, including the refusal.
* feat(cli): list and read agents by their Orca session ID with orca agent list/show/read
Live terminal and chat agents are listed, shown and read by Orca session ID on the selected host; sleeping native agents can be shown and read by ID. Chat reads walk the chat's own bounded history pages back to the latest /clear.
* fix(cli): agent show names a live agent and its last reply as agent list does; help says sleeping terminal agents aren't listed yet
* Bound agent reads and scoped workspace inventories
* fix(cli): agent read carries the conversation's state, so a running chat turn reads as working
agent read now reports the same state agent list/show report, from the same status
rows, in text (a leading state line) and --json (state). A turn still running no
longer reads like a finished chat with no reply.
* Fix agent conversation read consistency and limits
* fix(cli): agent read derives its state from the history it returns
agent read no longer samples live status. A chat's state comes from the
journal snapshot that produced its entries: an open turn or an accepted
send with no turn yet reads working; done needs an explicitly successful
latest turn whose reply is the newest entry shown. A terminal agent's
state comes from the provider turn markers in the same transcript bytes:
a prompt with no end after it reads working, done needs an explicit end
(Claude stop_reason, Codex task_complete) with the reply as the newest
entry. Anything else omits state. The journal lane wait added for the
live state is removed.
* Tighten agent read snapshot evidence
* Keep agent read done for finished turns
A dead owner now only voids working. Codex completion is proved by the turn's own
decoded reply rather than row adjacency, and Claude's by its end row's own reply,
without needing the prompt inside the read window.
* Adapt agent commands to reorganized shared contracts
* Warn on incomplete agent lists, read sleeping transcript paths, and retry unanswered provider id lookups
* Follow main's moved shared modules
* Bound live transcript recovery to conversation panes
* Show sleeping terminal agents where agent list lists them
agent list lists a finished terminal agent while its pane sleeps, since main keeps
that status row. agent show now counts the same sleeping place, and the help says
which sleeping agents are listed. Messaging still ignores sleeping panes.
* Clarify sleeping agent discovery and messaging help
* Say sleeping terminal agents can't be messaged and note the WSL read exception
* Follow the moved CLI argument boundary after rebasing
* Show plain Orca session IDs in agent command help
* Expect plain UUID Orca session IDs in the transcript source test
* Follow main's moved shared modules after rebasing
* Name Orca session IDs <id> in agent help, since older IDs keep their agent prefix
* Follow main's moved agent-session modules after rebasing
* feat(workspace-cleanup): delete chat history of deleted workspaces
Adds an off-by-default host setting. When on, each cleanup run deletes agent
transcripts whose Orca workspace folder no longer exists, through AI Vault's
validated delete, and reports the count and space in the run's activity.
* fix(workspace-cleanup): keep chat history of folders Orca never made a workspace
Skip workspace parents that are or hold a project checkout, protect folders
holding a still-listed workspace in any spelling, re-check each folder right
before deleting, batch scope paths, count companion bytes, sweep chats at most
every 6 hours on hourly runs, and refresh the report when the switch changes.
* fix(workspace-cleanup): treat only nested Orca workspace folders as deletable
Look for deleted workspaces only in <root>/<repo> of nested layouts, protect
renamed workspaces' earlier paths, folder workspaces and case variants, use the
recorded cwd only, re-check the parent and the setting before each deletion.
* fix(workspace-cleanup): protect flat workspaces and per-host rows from the chat sweep
Drop parents inside a still-listed workspace, also read this host's own
worktree rows, record a run only when a rule or a due chat sweep has work,
and cache per-folder protection with precomputed matchers.
* fix(workspace-cleanup): find deleted workspace folders by filesystem identity
Walk up from the recorded cwd to the deepest existing folder and require it to
be, by device and inode, an Orca <root>/<repo> folder without .git; key
protected paths the same way, so symlinks, case and Unicode spellings are the
OS's call. A failed history scan no longer fails the run, and an open session
history list refreshes after chats are deleted.
* fix(workspace-cleanup): close the remaining chat sweep gaps
Walk physical ancestors of a symlinked parent, skip a gone folder with a
lookalike sibling (parsers trim cwd), re-read listed paths after the scan,
never touch WSL paths, use bigint file identity, and report the next run
that actually sweeps when only chat history is on.
* fix(workspace-cleanup): keep chats resumed elsewhere and follow dangling listed links
Before deleting, re-read each transcript: skip it if it was written in the last
hour or its last recorded cwd is outside the gone folder (a chat resumed at a
live workspace's root). Listed symlinks protect their targets, and parents are
re-checked against the listed paths read after the scan.
* fix(workspace-cleanup): sweep only Claude chats, whose every message records its cwd
Keep a transcript unless its latest recorded cwd, read back past large blobs,
is still in the gone folder; agents that record cwd once can't prove a chat
wasn't resumed elsewhere. Follow symlinks along listed paths, dangling ones too.
* fix(workspace-cleanup): read only a record's own cwd and check each chat right before removal
Parse whole JSONL records backwards and use their top-level cwd, not tool
arguments; run the setting, folder, idle and last-cwd checks right before each
transcript's removal; resolve relative listed links from their real folder.
* fix(workspace-cleanup): protect subagent transcripts and re-read listed rows per folder
Check a chat's companion transcripts with the same idle and last-cwd rules,
read Orca's listed rows right before each gone folder's deletion, keep '..'
in listed link targets for the OS to resolve, and say Claude Code in the copy.
* fix(workspace-cleanup): fold names fully, keep POSIX repo names, re-stat rows only on change
Fold case with upper then lower (final sigma), take the repo name with this
host's basename, re-read listed rows per folder only when the catalog changed,
and sweep chats even when rule evaluation fails.
* fix(workspace-cleanup): re-check the chat itself after walking its companions
A chat resumed while its subagent transcripts were being checked has a new size
or mtime, so it is kept.
* chore(workspace-cleanup): sync localization catalogs and drop a cast in the cwd reader
* fix(workspace-cleanup): re-check every subagent transcript after the companion walk
Record each companion's version and require the same set, unchanged, before
approving deletion; skip the symlink-based sweep test on Windows.
* fix(workspace-cleanup): protect chats by what listed paths pass through, checked per chat
Each listed path claims the (existing folder, name) pairs along it, so a gone
folder holding one stays protected whether that path exists right now or not;
claims are re-read before every removal, and an unfollowable symlink chain
stops the sweep.
* fix(workspace-cleanup): an unreadable folder or a non-directory leaves the sweep fail-closed or ignored
A stat error other than absence while reading listed paths marks the snapshot
incomplete; ENOTDIR counts as absence instead of stopping every sweep.
* fix(workspace-cleanup): check row protection last before each removal and allow exactly eight links
Run the slow transcript checks first so the folder and listed-row checks are
the freshest before the rm, and resolve the eighth link instead of treating
it as an unfollowable chain.
* chore(workspace-cleanup): follow the shared settings and execution-host module moves
* chore(workspace-cleanup): mark an unreadable identity as undefined, not a string literal
* fix(workspace-cleanup): re-read protection when a listed symlink is retargeted
Listed paths that go through a symlink record where they led; a different
target before a removal re-reads every claim.
* 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
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>
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>
* 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
* 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
Let users name, rename and reset labels for saved Claude and Codex accounts without changing credentials or restarting agents. Keep the sign-in email visible across Settings, account switchers, chat usage, CLI and phone surfaces, and identify the account in removal confirmations.
Tracked in #21182.
Co-authored-by: Wooseong Kim <innocarpe@gmail.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
Each project can pick a browser profile (Default or a named one) for its new tabs, overriding the Browser setting's scope. Also settable with `orca repo set --browser-profile`.
Co-authored-by: Dunz Koi <258568505+dunzkoi@users.noreply.github.com>
* 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
`orca orchestration inbox` rejected --run even though the
orchestration.inbox RPC already accepted a run filter. Accept --run in
the CLI spec and forward it; the server now refuses an unknown Run
(hinting when a run:<id> mailbox address was passed instead of a bare
id), and the CLI refuses rows from other Runs when an older server
ignores the filter.
Fixes#42732
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* refactor: group process and platform modules by ownership
* refactor: preserve moved module workflow routing
* refactor: preserve native loader and embedded bundle origins
- Mention routing notes and terminal_busy / chat-session refusal pointers
now include the required --subject and --body flags for
`orchestration send`.
- `orchestration send --to <ctx_id>` refusals for a bare id of an existing
Dispatch now suggest `--to dispatch:<id>`.
- `orchestration check --help` documents its own --format meaning instead
of the screenshot image-format text.
- Remove an unused agent-reference test fixture.
Fixes#42735
Co-authored-by: Claude <noreply@anthropic.com>
On Linux the desktop app installs its CLI as `orca-ide` (GNOME's screen
reader owns `orca`), but help text, typo suggestions, missing-subcommand
hints, and runtime-unavailable hints all printed `orca`, so copied commands
launched the screen reader. Resolve the invoked command name (Orca terminal
shim via ORCA_CLI_COMMAND, `orca-dev` for dev launchers, `orca-ide` for the
Electron-run-as-node app launcher, `orca` elsewhere) and render it in those
outputs. macOS/Windows and SSH Node CLIs keep `orca`.
Fixes#42682
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* Move environment store operations off the main thread
* Preserve CLI startup speed with the serialized environment owner
* Handle absent paired host labels in the producer regression fixture
* Preserve publication ownership and copy selected environment results
* Correct publication and WSL readiness regression fixtures
* Include environment store worker in deployed server artifacts
* Check fresh listing publication across an intervening store update
* Await store-backed results in new recovery coverage
* Retire failed page publications and retain CLI worker support entries
* Unpack environment store support modules for the installed CLI
* Align async store callers with their return contracts
* Avoid hardening work for absent environment store files
* Keep permission repair bounded to one hardening attempt
* Align store test fixtures and await pairing replacement
* Use the semantic store operation for external pairing fixtures
* Provide the live sender frame in the timed subscription fixture
* Share pending server lookups and settle retired phone requests
* Keep the relay error type import
* Keep status ownership and transport imports acyclic
* Await replacement pairing in status retirement cases
* Keep asynchronous server rows bound to their admitted pairing
* Keep inventory snapshots and queued delivery at one publication boundary
* Await saved-host and graph test setup through publication completion
* Finish async fixture types and remove foreground timing probe
* Await renderer surface transitions in process identity coverage
* Await nested graph publication fixtures through their callers
* Await restored pane graph publication before hook assertions
* Include imported store worker and sidebar files in web typecheck
* Prepare saved host storage in source-based WSL test rigs
* Await saved server lookups in the source retirement diagnostic
* Preserve newer WSL status across async saved-host reads
* Fence stopped probes when a newer WSL Ready arrives
* Keep saved WSL host selection covered when admission is off
* Check WSL probe ownership after async admission
* Preserve WSL stop authority without cancelling Ready persistence
* Prune removed WSL E2E real-time wait from flaky-test baseline
* Limit WSL callback invalidation to confirmed stops
* Retire pending WSL notices on every confirmed stop
* Close the WSL picker dialog explicitly between scenarios
* perf(layout): skip unused normalization reports in pane commands (#42615)
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Clarify cleanup pinning and ignored-file protection (#42616)
* test: remove 55 low-value suites and assertion driver (#42605)
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
* fix(skills): skip Claude sync scratch folders during skill discovery (#42610)
Claude Code parks replaced skill copies in `.trash` and in-progress syncs
in `.staging` under its skills roots. Discovery walked into both, so each
synced skill showed up as duplicates. Prune those directory names in the
native file walk and in the generated WSL `find` command.
Co-authored-by: Neil <4138956+nwparker@users.noreply.github.com>
* test: remove 78 low-value suites and trim redundant cases (#42621)
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
* Keep quit teardown within the source line budget
---------
Co-authored-by: Jinjing <6427696+AmethystLiang@users.noreply.github.com>
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Co-authored-by: OrcaWin <alpha-eng@stably.ai>
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
Co-authored-by: BingZ <zzb@gxsmjx.com>
Co-authored-by: Neil <4138956+nwparker@users.noreply.github.com>
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
Add `orca fill --value-stdin` so passwords and other secrets stay out of
argv and shell history. Fill drops one trailing newline from stdin (secret
readers end with one) and rejects empty stdin so a failed reader cannot
silently clear the field; `--value ''` still clears.
Share one flag-or-stdin reader with `orca computer type`/`set-value` and
the `--body-file -` reader. Computer commands keep their existing
semantics: no newline trimming, set-value still accepts empty stdin, and
`--text-stdin=true` style keeps reading stdin.
Fixes#29849
Co-authored-by: Neil <neil@stably.ai>
* fix(updater): hold orcad's browser helper during every macOS install
* fix(updater): keep supervised serve self-updates out of the blocker-free park
* fix(updater): honor late park refusals and hold on any staged quit install
* test(orcad): run the install-park helper test off macOS
* fix(updater): commit the install-on-quit park with async writes
* fix(updater): make quit teardown wait for the install-on-quit park commit
* 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>
* 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
* perf(layout): skip unused normalization reports in pane commands (#42615)
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Clarify cleanup pinning and ignored-file protection (#42616)
* test: remove 55 low-value suites and assertion driver (#42605)
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
* fix(skills): skip Claude sync scratch folders during skill discovery (#42610)
Claude Code parks replaced skill copies in `.trash` and in-progress syncs
in `.staging` under its skills roots. Discovery walked into both, so each
synced skill showed up as duplicates. Prune those directory names in the
native file walk and in the generated WSL `find` command.
Co-authored-by: Neil <4138956+nwparker@users.noreply.github.com>
* test: remove 78 low-value suites and trim redundant cases (#42621)
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
* test: remove 53 low-value suites and trim redundant cases
---------
Co-authored-by: Jinjing <6427696+AmethystLiang@users.noreply.github.com>
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
Co-authored-by: BingZ <zzb@gxsmjx.com>
Co-authored-by: Neil <4138956+nwparker@users.noreply.github.com>