1346 Commits
Author SHA1 Message Date
buf0-bot[bot] 19b2546c64 Update README downloads badge (#44061)
Co-authored-by: buf0-bot[bot] <252831055+buf0-bot[bot]@users.noreply.github.com>
2026-11-18 11:08:42 +00:00
Neil c7034b8852 docs: rotate WeChat community QR code (#44053) 2026-11-18 02:48:46 -08:00
Brennan Benson a7b5c0a8f2 Run supported Mac chats and background agents under Orca Agents (#41917)
* Name terminal agent hosts separately from Orca

* Account for one startup process naming write

* Use the Node runtime for the Linux naming contract

* Run supported local agents under the independent host

* Preserve retirement type narrowing and valid test plans

* Align restart warnings and satisfy changed-file lint rules

* Declare the current daemon protocol in build compatibility metadata

* Keep hosted agent output complete through process exit

* Keep the output regression focused on catalog failure and cleanup

* Keep output regression fixtures compatible with quality checks

* Publish Claude exits after hosted process absence is proven

* Pass session fences in the hosted Claude regression

* Fall back to direct chat launch when the host image is unavailable

* Keep the hosted Claude recovery fixture independent of OS signing

* Settle refused agent launches and preserve exit observation wakes

* Keep provider population fixture defaults independent of array indexes

* Document direct launch when agent host connection checks fail

* Retain native provider no-start outcomes before refusal

* Keep chats working when the agent host cannot read their folder

* Preserve native missing-folder coverage after the access preflight

* Keep desktop permission notices at the desktop launch boundary

* Bound hosted launch setup and keep hosted chats out of host process growth

A host still starting no longer holds a chat past its bootstrap deadline, the host's
code signature is read once per host process, and the native owners the host starts
for the app do not count as its terminal work. The hosted launch test runs under Node,
whose destroy closes only the host's own socket copy.

* Keep hosted owner pipes blocking, recheck the host before dispatch, and keep launch-folder errors

The native owner clears O_NONBLOCK that a host's sockets carry, so its gate read and the
CLI's stdio behave as on a direct launch. A reconnect to another host before dispatch
launches here instead of on an unprobed host, and a host spawn error keeps its code and
path so a deleted folder is still reported as missing.

* Skip hosted owner subtrees in the growth walk and expire the host image read

The growth sample now stops at hosted owners instead of walking their subtrees again,
so it never does more work than before. A host's code-signature read is reused only
for 10 s, so a bundle removed while the host runs is noticed on a later launch.

* Satisfy changed-code quality for the hosted launch wait and its test

* List provider requests in the daemon router's exhaustive switch

* Launch a chat here when the host's start fails before attach

The native owner runs its CLI only after this app opens its gate, which
attaching does. A host spawn error, a lost reply or pipes that never arrive
therefore leave no CLI running and no input sent, so the chat now launches
here instead of failing. Once attached, a failure still ends the launch.

Tests cover a host that can't read or can't start in the chat's folder, a
host that never answers the folder probe, a lost spawn reply, and the
folder-access notice verdicts.

* Keep fallback time inside the owner's startup deadline

A hosted start could spend 10 s on the spawn reply and 10 s on its pipes,
past the owner's 15 s bootstrap deadline, so a late failure ended the
chat instead of launching it here. The hosted attempt now has one 8 s
budget from the start of the launch.

A folder denial whose app-side recheck finished after a newer readable
verdict restored a cleared notice; the newest verdict for the same helper
and folder class now wins.

* Fit the hosted start inside the owner's bootstrap and proof budget

The hosted attempt's budget is now the bootstrap deadline minus the
ownership proof window, so a hosted owner or a direct fallback still has
time to prove ownership. A timer bounds the spawn request too, so a
stalled event loop can't let the bootstrap deadline fire first.

Only a newer readable verdict from the same helper supersedes a pending
folder denial, so a later denial in another folder no longer hides a real
notice, and the record holds one entry per folder class.

* Track folder re-allows per helper so a replaced helper can't erase a notice

Keying the re-allow marker by folder class alone forgot an old helper's
re-allow once a new helper read that class, so the old helper's late
denial overwrote the new helper's notice. Marks are per helper and class
again, capped to the most recent pairs.

* Supersede pending folder denials directly instead of keeping re-allow marks

Capped marks could evict a re-allow while its denial was still being
read, reviving the stale denial. A readable verdict now flags the same
helper's pending denials for that folder class, and only denials still
being read are kept.

* Keep folder verdicts off blocking reads and bound the whole hosted start

Native-chat folder verdicts now reach the shared verdict telemetry, so its
spawner-path check and pid-file read are now asynchronous instead of
blocking the main process. The extracted backlog code only builds the
sampler, so the server keeps calling the existing probe directly. Lowered
the blocking-helper baseline rows that shrank.

Connecting to the host and checking its signature and the folder now share
the hosted start budget, so a slow host still leaves a direct launch time
to prove ownership.

* Lower the sync-fs baseline row the async telemetry checks emptied

* Drop folder verdicts from host checks that outlived the start budget

A host check still running when the direct fallback took over could report
a late denial and bring back a notice a newer readable verdict had
cleared. Checks past the budget now count as abandoned and report nothing.

The integration test now ends the CLI's input only after it starts, since
its owner allows only a short grace once input closes.
2026-11-18 00:55:34 -08:00
Brennan Benson 3477418ccc Move 'Delete agent history when a workspace is deleted' to Settings > Agents (#43774)
* feat(settings): move 'Delete agent history when a workspace is deleted' to Settings > Agents

Same stored key (deleteChatHistoryWithWorkspace), default, host scope and confirm dialog;
only the row's place and title change. Row placement follows #42877.

* fix(settings): keep workspace cleanup rule names protected from language packs

* fix(settings): find the moved setting by its old name, toast failed local saves, keep it off paired web clients, update CLI docs

* fix(settings): leave the agent history setting out of search in paired web clients

* fix(settings): keep the agent history switch out of the composer's Agents dialog; say agent history in its confirm
2026-11-17 18:48:22 -08:00
Jinjing 91ea2bc3be fix(dialog): show dialog footer focus ring only for keyboard focus (#43409)
Dialog footer buttons used :focus, so the auto-focused action (for example
Cancel in the Delete workspace dialog) drew a grey ring on every pointer open.
Switch to :focus-visible so keyboard users still get the ring, and qualify the
styleguide note for focus-visible modality and aria-disabled buttons.
2026-11-17 18:37:06 -08:00
buf0-bot[bot] a9047a6984 Update README downloads badge (#43796)
Co-authored-by: buf0-bot[bot] <252831055+buf0-bot[bot]@users.noreply.github.com>
2026-11-17 23:24:01 +00:00
Neil 19e5992f0f chore(deps): resolve addressable RubyGems alerts and patch picomatch GHSA-fc5q-39xc-vjpf (#43775)
* chore(deps): resolve addressable RubyGems alerts and patch picomatch GHSA-fc5q-39xc-vjpf

* fix(cloud): keep picomatch patch inside cloud/ Docker build context
2026-11-17 14:49:30 -08:00
Kelvin Amoaba ae3fe2642c feat(cli): connect Linear on any Orca host with orca linear connect (#43770)
* feat(cli): connect Linear on a headless host with orca linear connect

* fix(cli): keep the selected server in linear connect hints and tolerate a failed status read
2026-11-17 22:38:51 +00:00
Brennan Benson 8aca61c8ed feat(cli): remove orca uninstall; uninstall lives only in Settings → Advanced (#43691)
Agents learn the orca CLI from skills and could run `orca uninstall --yes`, which strips every agent's hooks, unlinks the CLI, stops orca serve and kills all terminals.

- Remove the command, its spec, dispatch entry and the terminalDaemon.stopForUninstall RPC.
- Drop the CLI packaging entries only it loaded.
- SSH hosts that aren't connected now say "Connect this host, then Retry.", and Retry reaches them.
2026-11-17 13:17:41 -08:00
25bf885898 feat(native-chat): run Hermes Agent in Chat over its ACP server (#42895)
* feat(native-chat): run Hermes Agent in Chat over its ACP server

Hermes chats run `hermes acp` against the profile's HERMES_HOME, pinned to
the profile Hermes runs when the chat starts. Ask, Accept edits and Full
access set Hermes' own edit approval mode; command approvals come from the
profile, so under Full access Orca answers them itself instead of launching
with --yolo, and switching back to Ask asks again. Questions and model-switch
confirmations always go to the person.

The Hermes dialect reads terminal results as output and exit code, names
tools from their titles, shows the sign-in card for Hermes' "not connected to
any AI provider" reply, and sends /compact as /compress. Reopening looks the
session up with session/list first, since Hermes moves a session into the
folder it is loaded from. Tools run in Hermes' shared gateway, so these chats
carry no Orca caller identity.

ACP stderr tails are redacted where the connection exposes them, so a key an
agent prints no longer lands in chat errors or saved chats.

Co-authored-by: ysovanna <ysovanna@gmail.com>
Co-authored-by: kinarajv <kinara.varga@gmail.com>

* fix(acp): drop a credential the stderr tail cut through before redacting it

A full 8 KiB stderr tail starts mid-line, so a key there may have lost the prefix the redactor matches. The tail now starts at its first whole line.

* fix(acp): drop a private key body the stderr tail cut from its BEGIN marker

Redaction finds a key block by its BEGIN marker, so body lines left after a cut tail passed through. A tail that begins inside a key block now starts after its END marker.

---------

Co-authored-by: ysovanna <ysovanna@gmail.com>
Co-authored-by: kinarajv <kinara.varga@gmail.com>
2026-11-17 21:13:12 +00:00
Kelvin Amoaba 434bc4e752 fix(browser): default the browser identity to Native so Cloudflare checks pass (#43730)
* fix(browser): default the browser identity to Native so Cloudflare checks pass

Cloudflare's full-page check loops for any Chrome-shaped UA on the Electron
engine. Users who never chose a mode now get Native; an explicit choice is
kept. Teams gets the UA without the Electron token in request headers, and
Chase gets the cleaned identity per tab, since both turn Electron away.

* fix(browser): keep the Teams header rule to Native and share the token strip
2026-11-17 20:38:57 +00:00
Neil a16afc4e67 refactor(e2e): group journeys by feature and repair browser recovery (#43628)
* refactor(e2e): group journeys and fixtures by feature ownership

* refactor(e2e): consolidate remaining Playwright owner imports

* test(ci): stop copying retired route modules into fixtures

* fix(browser): preserve one-shot follow intent across equal snapshots

* refactor(settings): colocate commit message defaults with source control

* test(browser): await page registration and focus the concrete page

* fix(browser): keep viewport recovery progressing during incompatible frames

* fix(browser): wait for stale helper exit before replacement commands
2026-11-17 11:44:44 -08:00
Neil 1fadf2a59a refactor(renderer): organize sidebar and component ownership (#43611) 2026-11-17 06:24:13 -08:00
Neil ef2daeee80 refactor(tests): colocate runtime and compatibility contracts with owners (#43589) 2026-11-17 05:12:29 -08:00
buf0-bot[bot] 00dee71bec Update README downloads badge (#43591)
Co-authored-by: buf0-bot[bot] <252831055+buf0-bot[bot]@users.noreply.github.com>
2026-11-17 12:26:34 +00:00
NeilandClaude Opus 5.5 1cb11c6856 fix(plugins): queue plugin frame requests past the in-flight cap instead of refusing them (#43554)
A wide ES-module import level could exceed the 32 in-flight cap of an
orca-plugin-frame session; the extra imports got a silent 503, which
fails the frame's whole module graph.

Buffered requests past the cap now wait FIFO for one of 32 slots, with
up to 1024 queued for at most 10 s each before a 503. Streamed media
bodies get their own cap of 32 and are refused at once, so held-open
streams never fill the slots buffered requests wait for. The plugin is
re-resolved after admission, and refusals are logged once per burst per
lane.

Fixes #43532

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-17 01:39:26 -08:00
Brennan Benson c535dca47d Send messages between agents through Orca mail, not terminal input (#43309)
* Send messages between agents through Orca mail, not terminal input

* Point the inject refusal at commands that work; qualify mail receipts

* Keep the refused terminal's workspace in the inject recovery

* Describe chat mail as delivered whole, terminal mail as a pointer

* Describe chat coordinator wakes and terminal mail notes precisely

* Describe the terminal-mailbox warning as agents see it

* Name the full send command and the check command the wake gives

* Tell agents how to find a tab's agent, and that mail isn't the user's answer

* Cover chat tabs, ambiguous tabs and an unset handle when finding an agent
2026-11-17 01:17:13 -08:00
Brennan Benson 0f25432f11 feat(cli): add orca agent installed to list installed agent CLIs (#43505)
* feat(cli): add orca agent installed to list installed agent CLIs

* fix(cli): agent installed omits disabled agents, marks the default, and is in the agent guide
2026-11-17 00:33:39 -08:00
buf0-bot[bot] dc88463694 Update README downloads badge (#43480)
Co-authored-by: buf0-bot[bot] <252831055+buf0-bot[bot]@users.noreply.github.com>
2026-11-17 06:29:29 +00:00
Kelvin Amoaba fc50fb4075 feat(workspace-cleanup): delete Orca chats from deleted workspaces with their chat history (#43015)
* feat(workspace-cleanup): delete Orca's own chats of deleted workspaces with their history

* fix(workspace-cleanup): close a deleted chat's shown tab the usual way and leave its rows to the next tick

* fix(workspace-cleanup): keep a chat worker that still owes a dispatch

* chore(workspace-cleanup): baseline the forgotten-chat journal SQL, which runs in the journal workers

* fix(workspace-cleanup): follow the tab table's move after rebasing onto main

* fix(workspace-cleanup): check the gone folder after the catalog re-read, nearest the delete
2026-11-17 00:23:04 +00:00
Neil 9c0c9428ac fix(plugins): stop git prompts in plugin workers and say plugins can use saved logins (#43326)
Plugin workers now get GIT_TERMINAL_PROMPT=0 so git fails cleanly instead of
prompting. The full-access warning and the authoring docs now say a worker can
use saved logins and SSH keys and that the environment filter is not a sandbox.
Adds tests for dropped code-loading variables and Windows case folding.
2026-11-16 15:56:26 -08:00
Kelvin AmoabaandMax Hsu 11403c1475 feat(workspace-cleanup): delete Codex chat history with the workspace (#43000)
The sweep now also deletes Codex rollouts whose workspace folder is gone,
under the same folder rule. A rollout is deleted under every name it has
across the host's Codex homes (sessions and archived_sessions, .jsonl and
.jsonl.zst), only when every copy is idle, its last turn ran in the gone
folder and Codex holds no writer lock for the thread. History link passes,
backfill and resume skip a rollout while it is being deleted, and no longer
leave a dangling symlink when the source is gone.

Fixes #16776

Co-authored-by: Max Hsu <maxmilian@gmail.com>
2026-11-16 23:10:41 +00:00
Neil 919e22d454 fix(plugins): pass the session bus and runtime dir to plugin workers so git credential helpers work (#43284)
Plugin workers run with an allowlisted environment that dropped
XDG_RUNTIME_DIR, DBUS_SESSION_BUS_ADDRESS and SSH_AUTH_SOCK, so git
credential helpers backed by libsecret and ssh-agent could not reach the
user's session. Allowlist these socket pointers and strip Chromium's
`disabled:` bus marker so GLib falls back to $XDG_RUNTIME_DIR/bus.

Fixes #43189
2026-11-16 14:49:44 -08:00
NeilandClaude f7ddbb68ad feat(plugins): expose the app fonts to plugin frames as --orca-font-sans and --orca-font-mono (#43282)
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>
2026-11-16 14:49:28 -08:00
Neil c097acc64e fix(editor): new files use the owning host's line ending; add End of Line setting (#43253)
* fix(editor): give new files the owning host's line ending, add End of Line setting

A file with no line breaks yet took the ending of the OS the window runs on,
so a Windows client wrote CRLF into files on WSL hosts and Linux SSH hosts.
Such models now adopt the ending of the host that owns the file (LF on Linux
and macOS, CRLF on native Windows), and Settings > General > Editor gains an
End of Line choice (Auto, LF, CRLF). Files with line breaks keep theirs.

Fixes #43216

* fix(editor): resolve paired-host files by endpoint and keep new-file EOL through undo

- Resolve a file's host from its endpoint-relative authority, so a file on a
  WSL host or paired server reads that host's OS instead of this client's.
- Only a WSL host's own files fall back to Linux; SSH targets behind it do not.
- Track whether a model was loaded with line breaks, and keep a new model on
  its chosen ending through undo, late host reports, and setting changes.
- A model without line breaks adopts the ending of external text written in.
- Read remote OS facts directly so the selector builds no translated strings.
- Docs describe Auto by where the workspace runs (Windows projects in WSL get LF).

* fix(editor): keep undo valid across late EOL conversion; respect text written while unmounted

- Convert typed lines with an undoable pushEOL step instead of a bare setEOL,
  whose stale offsets corrupted Undo. Only a new choice (late host report or
  setting change) converts multiline text, so Undo of the conversion sticks.
- Record outside text with line breaks on the model from the content-sync
  paths, so a remounted editor never converts text the user did not type.

* fix(editor): never convert a new file's line endings once its lines are saved

A clean buffer with line breaks matches the file on disk, so it is treated as
an existing file: changing End of Line later no longer converts it, marks it
dirty, and lets autosave rewrite it. Only typed, unsaved lines are converted.

* fix(editor): treat a new file as saved only when its bytes match disk

The dirty flag ignores Markdown trailing whitespace, so a clean flag did not
prove typed line breaks were saved. Compare the model text with the buffer's
last known disk signature instead. Also type the line-ending state by its
model shape for the anti-slop lint, localize the LF/CRLF labels, and note in
the docs that autosaved lines keep their ending if the host reports later.

* fix(editor): only set a new file's line ending while it has at most one line

Converting text that already has line breaks kept running into cases where
saved or in-flight lines were rewritten. The editor now sets the ending only
while the model has at most one line, at mount and whenever the choice
changes, and re-applies it when Undo returns to one line. Text with line
breaks is never converted. This removes the multi-line conversion, its undo
step, the per-model state and the disk-signature check.

* fix(editor): keep an existing file's line ending after it is emptied

A model that already had line breaks when the editor mounted, or got them
from a programmatic or outside write, is flagged as an existing file and
never has its ending set again, so emptying and retyping it keeps the file's
ending. Line breaks the user typed do not set the flag, so Undo back to one
line still restores the chosen ending. Scope the docs sentence on outside text.

* fix(editor): carry a buffer's line ending through model rekeys and renames

A replacement model was built from text and language alone, so an emptied
or one-line existing file lost its ending and existing-file status. The rekey
carry now copies both to the model it creates. A rename remounts the editor
under a new view id, so the rename records the old model and the remount
carries an unsaved draft the same way. Existing models at the destination are
never touched.

* fix(editor): hand a renamed buffer's line ending over as a snapshot

The rename handoff stored the old model's address, which model cleanup could
dispose before the renamed tab mounted, and records were never cleared. The
rename now snapshots { ending, existing-file } from the old model, only for a
tab with an unsaved draft, keyed by the new tab id. The tab-close cleanup
drops it, and the remount applies it only to the model it builds from the
draft. Same-view re-keys still carry from the live model.
2026-11-16 14:49:08 -08:00
Neil 8edafc5aa1 docs(cli): describe artifact publishing as on by default for new profiles (#43280)
The CLI overview called artifact publishing opt-in, contradicting the CLI
reference and Settings docs, which say the gate is on by default for new
profiles while older profiles keep their previous setting. Align the
overview wording and drop the stale opt-in phrasing from the browser docs.

Fixes #43272
2026-11-16 14:39:05 -08:00
Brennan Benson c5733d7367 List and read any agent by its Orca session ID: orca agent list/show/read (#41815)
* 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
2026-11-16 14:07:46 -08:00
Kelvin Amoaba a92ec1672d feat(workspace-cleanup): setting to delete Claude Code chats of deleted workspaces (#42959)
* 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.
2026-11-16 21:43:40 +00:00
buf0-bot[bot] 83714e8863 Update README downloads badge (#43208)
Co-authored-by: buf0-bot[bot] <252831055+buf0-bot[bot]@users.noreply.github.com>
2026-11-16 18:23:47 +00:00
JinjingandClaude e7dad53566 docs: lead Android links with Google Play, keep the APK as the fallback (#42973) (#43084)
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>
2026-11-16 02:29:02 -08:00
Nikolai ShcheglovandNeil ba1f8f9eb4 fix(browser): open SSH links in Orca when the host browses from this device (#41589)
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>
2026-11-16 02:04:51 -08:00
Brennan Benson 8feab8456e feat(uninstall): remove Orca's hooks, CLI and services from Settings → Advanced and orca uninstall (#42889)
* 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
2026-11-15 23:29:03 -08:00
buf0-bot[bot] 2869f0f520 Update README downloads badge (#42996)
Co-authored-by: buf0-bot[bot] <252831055+buf0-bot[bot]@users.noreply.github.com>
2026-11-16 06:42:17 +00:00
Neil 15329fd804 fix(plugins): label the code languages category "Languages" (#42947)
"Translations" now holds interface-language packs, so the plain "Languages" label is no longer
ambiguous.
2026-11-15 20:31:20 -08:00
NeilandClaude bf0af4d026 fix(docs): only one search trigger answers Ctrl/Cmd+K so the page scrolls after closing search (#42912)
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>
2026-11-15 18:09:45 -08:00
Neil a13016fff1 chore(deps): upgrade vulnerable transitive packages and enforce 3-day release cooldown (#42868) 2026-11-15 16:54:04 -08:00
buf0-bot[bot] 568b4887f8 Update README downloads badge (#42892)
Co-authored-by: buf0-bot[bot] <252831055+buf0-bot[bot]@users.noreply.github.com>
2026-11-16 00:46:18 +00:00
Kelvin Amoaba b6173eff04 fix(computer): click macOS windows that refuse focus when --restore-window is allowed (#42824)
* 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
2026-11-15 22:07:37 +00:00
Kelvin Amoaba 8e693efda4 feat(computer): add flags for smaller screenshots on macOS, Windows and Linux (#42801)
* 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
2026-11-15 22:06:12 +00:00
Kelvin Amoaba 28fd7052ad feat(computer): list macOS apps without a Dock icon while they show a window (#42786)
* 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
2026-11-15 20:33:53 +00:00
mia-ambrandNeil c67c705a4c docs: correct Windows verification and contributor script paths (#42766)
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>
2026-11-15 10:22:04 -08:00
Neil c3a681f5b1 refactor: group process and platform modules by ownership (#42742)
* refactor: group process and platform modules by ownership

* refactor: preserve moved module workflow routing

* refactor: preserve native loader and embedded bundle origins
2026-11-15 07:23:28 -08:00
buf0-bot[bot] 132a973b91 Update README downloads badge (#42625)
Co-authored-by: buf0-bot[bot] <252831055+buf0-bot[bot]@users.noreply.github.com>
2026-11-15 12:23:26 +00:00
Neil 234e6de5f4 fix(plugins): date appearance and editor typography floors to their releases (#42691)
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.
2026-11-15 02:12:31 -08:00
Neil af82fa8634 feat(plugins): check host API calls against released Orca at validation (#42662)
* 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
2026-11-15 01:51:33 -08:00
Neil cb7eaf9dd3 feat(plugins): separate code languages from translations in the plugin browser (#42680) 2026-11-15 01:37:30 -08:00
Cristian LopezandNeil c62f65bc9a feat(plugins): list any workspace's agents with agents.list({ workspaceId }) (#40743)
* 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>
2026-11-15 00:30:45 -08:00
kaluli123123andNeil 1db3760528 fix(browser): keep Clear default cookies available, with confirmation (#15044)
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>
2026-11-15 00:27:08 -08:00
Kelvin Amoaba c53ba40801 fix(computer-use): put the pointer back after macOS --restore-window clicks, scrolls and drags (#42643)
* 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
2026-11-15 07:39:12 +00:00
OrcaWinandOrcaWin 360233857a test: remove low-value mobile transport config and docs suites (#42552)
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
2026-11-14 16:54:11 -08:00