* fix(plugins): wire the plugin service on a headless serve, and turn plugins on from the CLI
* test(plugins): build the switch test's RPC context inline after main dropped the shared helper
---------
Co-authored-by: Justas Brazauskas <brazauskasjustas@gmail.com>
`serve service install` copied the caller's PATH into the systemd unit or
LaunchAgent. Run from the AppImage, that PATH starts with the launch's
temporary /tmp/.mount_* directory (and $APPDIR/usr/sbin), which is gone by
the service's next start; another process's mount could later take the
same name.
The unit PATH now drops every directory the service command lookup
already refuses as tied to one Orca version or AppImage launch: profile
and orcad artifact dirs, the AppImage FUSE mount, and extract-and-run
copies (appimage_extracted_*), plus relative entries. AppImage mount
detection now lives in one shared helper used by the service command
check, the unit PATH and the daemon host-image probe; the command check
previously missed extract-and-run copies.
Fixes#36000
* feat(themes): per-folder-name icons in plugin icon themes
Icon themes could only set one generic folder and folder-open icon, so
themes like Material Icon Theme could not give src, docs or tests their
own icons. Add VS Code's folderNames and folderNamesExpanded maps. They
use the same lowercasing, duplicate checks, own-key records and limits
as fileNames, and older Orca builds skip them. Every folder icon now goes
through FolderIcon: the explorer, Source Control, diff and conflict trees,
and the remote, sparse and symlink pickers.
* fix(themes): match the common icon-theme fallback for open folders
One table-driven test keeps every concise orchestration list row short when stored text is huge. Concise run-list cuts each Run's objective to one line of at most 160 characters; --full is unchanged.
Concise task-list rows carry id, status, title and ids only; specs and results stay in --full (407 KB to 11.5 KB text on a 138-task Run). Concise gate-list rows drop resolutions and timestamps.
orca orchestration send --to dispatch:<id> now works whatever the worker's state: a working worker reads it now; a finished worker still open gets it as a follow-up Task in place; a closed worker is reopened in its saved conversation, or started fresh with the earlier task and report when no conversation is saved. Unread mail at worker_done becomes a follow-up automatically. An older paired server refuses send to a finished worker with an update message.
worker-start and task-create take --spec-file <path> (or - for stdin). worker-start --keep-open keeps a worker open after it finishes in one step, and worker-keep-open replaces worker-retain (kept as a hidden alias). Concise text output escapes terminal control characters in worker-written values.
Orchestration commands print small flat fields in text and --json by default; --full prints the previous output. Failures exit non-zero with error: <code>: <message> on stderr.
* Chat UI leaves Experimental: each agent's Chat | CLI choice decides launches
Remove the experimentalNativeChat switch and every gate on it. The Chat
settings page, Default Agent Chat | CLI choice, + menu Chat/CLI rows,
source-control surface choice, Antigravity chat section and orchestration
chat-error switch are always present. What a new launch opens comes only
from the per-agent choice (no saved choice opens a chat) plus the existing
support checks.
- One lookup, nativeChatPreferenceFor, keyed by agent id so host-registered
agents read the same way; unreadable settings still open a terminal.
- A relayed desktop stamp (nativeChatDefault) maps onto the launched agent;
an explicit surface still wins. Old phones' createSupport keeps admitting
by the host's per-agent choice.
- settings.get stops publishing the retired switch keys; nothing in the
repo reads them from a host.
- Startup chat sync and hydration run when some agent can open as a chat
or the machine already holds chats.
- The retired key is stripped on load. The one-time upgrade tip from the
chat upgrade is retired with its audience record; a new record, captured
once from the raw profile, marks which existing profiles had Chat UI off.
- The window-side AI-button tab path, which only ran with the switch off,
is deleted.
* Keep profiles that had Chat UI off on the terminal
Existing users who never turned Chat UI on would otherwise see new agent
launches open as chats, since an agent without a saved choice now opens as
a chat. The one-time load step that records the new audience also sets
every known agent to CLI for those profiles, in the same save and only
when the record was absent, overwriting saved chat choices the old switch
masked. Profiles that had Chat UI on and new profiles are untouched.
Browser profiles keep their own settings, so the web client does the same
once: a stored switch that is not on seeds CLI choices, and dropping the
key marks the step done.
Agents first seen after this step open as chats.
* Agents without a saved Chat | CLI choice open as their CLI
An agent with no saved choice now opens in the terminal for everyone,
including fresh installs and agents first seen later. The one-time load
step carries what launches opened while Chat UI was experimental: with
the switch on, every known agent without a saved choice is saved as
chat; with it off, chat choices the switch masked are saved as CLI.
Existing profiles join the launch tip audience whether the switch was on
or off. Browser profiles get the same carry from their saved key.
The startup chat restore and host agent list now run only when some
agent is saved as chat or the runtime holds chats.
* Preserve owned terminal launches and local chat choices
* Clarify chat and terminal support
* Explain worker CLI integration timeout budget
* Use checked annotations for chat graduation test fixtures
* Store agent surface default separately from per-agent overrides
* Preserve explicit Chat intent across default changes
* Preserve current browser settings during host replies
* Correct browser settings factory and regression types
* Name exported launch fixture mock types and clarify agent defaults
* Preserve settings fallbacks and complete launch test lifecycles
* Check allocated tab identity before launch fixture interpolation
* Register combined integration project for compiler parity probes
* Use checked settings in the launch test fixture
* Preserve retired Chat preference data privately
* Align chat E2E fixtures and capture pane lifecycle evidence
* Use typed raw settings in retention contracts
* Consolidate transcript diagnostic imports
* test: align chat fixtures with live pane and native menu contracts
* test: capture relay tab selection loss diagnostics
* test: wait for owned shells before synthetic chat fixtures
* test: preserve all-host visibility in SSH observer
* test: bind synthetic transcript fixtures before provider seeding
* test: assert selected chat owner after narrow image preview
* ci: allow fifth compiler project to complete comparison
* Type the web-terminal fixture's chat map without an assertion
* Right-click the selection itself in the chat copy spec
* fix(agents): accept launch-time --model and --effort for grok
Grok's session option catalog already maps model and reasoning effort to
-m / --reasoning-effort, but it did not opt into worker launch
preferences, so orchestration worker-start rejected --model/--effort for
grok. Opt the catalog in and list Grok in the CLI help and docs.
Fixes#36199
* test(orchestration): use an agent without launch preferences in the federation rejection test
* fix(orchestration): keep a terminal's mail from being consumed by another terminal, and let settled structured workers take further tasks
A plain orchestration check consumed the named terminal's mail whatever terminal ran it, so a
coordinator checking a worker's handle took the worker's message. A consuming check from a
terminal whose own live pane is a different terminal's is now refused; --peek and --all still read
it without consuming.
worker-start --terminal and dispatch --inject routed a structured worker (structworker_ handle) as
a terminal and failed with terminal_unsupported_for_agent_session. Any agent-session party now
takes its task as a send into its session, while a structured worker keeps the pane and process
authority its first Dispatch had.
* fix(orchestration): fence check by live terminal incl. acks; defer injecting structured workers
Review fixes for the mail fence and structured worker reuse:
- The check fence compares the caller's and the mailbox's live terminal process instead of
recorded panes, so exited terminals keep the old behaviour and two processes sharing a
recorded pane are told apart. It also covers --ack in every read mode. The caller lookup is
shared with the lifecycle caller fence.
- dispatch --inject to a structured worker stays refused as before: an injected Dispatch takes
no custody, so releasing the first Dispatch could close a session working on the second.
worker-start --terminal reuse transfers custody and stays supported.
- worker-start decides pane-less chat authority from the resolved party and passes the session
down, so delivery and next commands no longer re-derive it from the address spelling.
- Receipts name an agent session, not a chat.
* fix(orchestration): an exited caller's env pane names no caller
The caller lookup fell back to the env pane key whenever the env handle was not live, so an
exited terminal's pane resolved to whatever terminal now occupies it, and a tmux worker's own
check was refused. The pane fallback now applies only when the env handle is not proven exited.
* fix(terminal): keep surviving terminals streaming to main after a restart
Main now attaches every live local daemon session it adopts at startup,
not only ones a window pane or remote view is showing, and re-attaches
after a daemon endpoint drop. The attach snapshot seeds main's screen,
tail and title, and an attached-but-silent agent gets an output clock so
readiness can see it has gone quiet. Waits on a survivor main could not
attach fail at once instead of timing out.
* fix(terminal): restore only pane-less streams after endpoint loss; one attach state
- Endpoint loss re-attaches in main only sessions no renderer view reports; a pane restores its own.
- The attach hide skips views mid-attach and leaves a pane's own hidden claim alone on failure.
- One per-session stream state (attaching, attached, lost) replaces three sets and is forgotten on exit.
- Waits retry the attach before failing, including after a failed re-attach.
- The output clock starts wherever a reattach result is seeded, so pane reattaches get it too.
* refactor(terminal): attach survivors at inventory adoption only; waits on unattached survivors fail at once; one ptyId output clock
* test(e2e): scope the restart attach spec's terminal listing to the unopened workspace
* fix(terminal): narrow survivor attach: waits behave as on main, one quiet clock per generation, keep main's hidden mark on failed attach
* Teach the orchestration guide when to hand off and to end the turn after dispatch
* Rewrap a messaging reference line
* Keep the original placement default and skill trigger; keep the accuracy fixes
* Point DAG retries at --retry-of and drop the last blocking-wait instruction
* Check the served orchestration guide by its new worker heading
* Apply council review: best-effort wake, full completion rule, restored safety rules, fixed scope and settled wording
* Say when the orchestration skill applies, and prefer own subagents otherwise
* Name the polling, steering, checkout, and worker fan-out habits to avoid
* fix(orchestration): wake a coordinator whose turn ended while its program still reports working
Claude Code keeps its OSC 7501 report on working while an agent-teams
teammate is alive, even after the lead's own turn ends. The mailbox gate,
idle edges and tui-idle all read that report, so worker mail was stored and
never typed. A hook turn end newer than the program's working report now
counts as rest; hook rows re-classify the PTY so the existing idle edge
delivers. Agent Teams panes now join their claude hook rows.
* fix(orchestration): compare the lead's own turn end, not the row's receipt
A child's hook restamps the row's receivedAt while the lead's turn is still
the old one, which could mark rest under a newer program working report.
Use the lead's turn-end stamp on this runtime's clock, after the latest input.
* feat(orchestration): a consuming check marks the batch it returns as handled
* Say why watch scripts and open waits block the wake
* feat(orchestration): release settled workers automatically after a grace period
* fix(orchestration): use checked row reads for delivery cursors
* fix(orchestration): trust a live own-process turn end instead of comparing clocks
Drop programActivitySince and the turn-end clock mapping: replays and SSH
host clocks made the comparison unreliable. A Claude lead counts as at rest
under a program working report when its hook turn end is a live transition
from this pane's host and launch, past the existing input and respawn floors.
* test(orchestration): drop cast in ack no-op check
* test(orchestration): seed legacy outstanding batch for held chat nudges
* test(orchestration): built CLI check hands its batch over
* test(orchestration): annotate unchanged casts and stub the keep item in tab menu tests
* fix(orchestration): let real input, explicit release and host releases converge with automatic release
- Record worker takeover at the owning runtime when it accepts UI input, before the bytes reach the PTY.
- Run remote attachment releases through the same per-resource single-flight as local ones.
- Apply the confirmed-release home projection when host observation reports a host-side release, and carry the host deadline in fleet snapshots.
- Prove restart recovery with a file-backed database reopened by a fresh runtime.
* test(orchestration): classify the keep RPC's worker fields instead of counting methods
* fix(orchestration): checked delivery reads and observer and recovery help
* refactor(orchestration): end a check when it hands over a batch; wake rides the wait result
* fix(orchestration): refuse an automatic close after real input, join remote releases, converge the home
- An automatic close checks the terminal's last driving-input time right before closing and keeps a worker someone typed into after worker_done; typing itself does no orchestration database work.
- Remote releases share the per-resource single-flight with local release, so a home worker-release joins the host timer's close.
- Host fleet snapshots and federationShow report released and the pending deadline; the home applies the existing release projection inside its observation fence.
- Real restart tests: a file-backed database reopened by a fresh runtime releases a missed deadline once and finishes interrupted requests.
* fix(orchestration): receipt a shared wake batch on arrival and report the applied Run ack
* fix(orchestration): deliver the wake to a working coordinator; agents queue mid-turn input
The wake was typed only into a live idle pane, so a Claude lead whose program
status stayed working (teammate alive) never got it. Agents queue or steer text
typed mid-turn, so a pane takes mail when live idle or working; dialogs,
permission prompts, exited agents, unsettled panes and cold-parked Enter still
hold it. Drops the held-batch Enter deferral and the per-turn-end hook logic.
* fix(orchestration): record each remote release request before joining, publish archives only through the conditional commit
- Each remote release caller records its own request before joining a close under way, and the close decides on the current row, so an explicit release that overlaps the host timer clears the automatic deadline.
- Remote capture publishes its archive through commitWorkerTerminalArchiveForRelease, so a retain during capture leaves no stale archive for worker-read.
- Remote worker-show projects the fenced host deadline and its next action.
- The input guard lives in its own module instead of the scheduler.
* feat(orchestration): start a worker in one step; worker-start creates the coordinator's Run when none is bound
worker-start --spec now creates and binds a Run for a root coordinator with
no bound Run, through the same path run-create uses, and names the Run it
created or joined in every receipt. Workers on a Dispatch keep starting
helpers in their own Run and never get a new one. A new CLI against an older
runtime runs run-create and retries; old CLIs need no change.
* fix(orchestration): drop the older-runtime fallback; check the spec before a Run is created
The CLI fallback matched a refusal text the client decorates, could not
prove the caller was a root coordinator on an older runtime, and recovered
an inner run-create under the worker-start command. Older runtimes keep
their refusal and the guide says to run-create first there. The prompt
budget check now runs before worker-start can create a Run.
* Route report-back requests to coordinators, complete the steer command, and label the wake loop branches
* Say workers are done only when worker_done confirms, wait for helpers to settle, and let bare-shell workers exit
* Route report-back requests away from handoff and steer supervised workers through their mailbox
* docs(orchestration): teach auto-handled check, retry-request and inbox recovery in the guides
* Describe the mid-turn wake in the messaging reference
* docs(orchestration): say terminal workers are released 2 minutes after worker_done
- The guide's Completion section, the reuse recipe and the recovery reference now describe the automatic release and its autoReleaseAt deadline: reuse or worker-retain before it; explicit worker-release still works and is required for chat workers and workers without a deadline.
- The worker preamble says the terminal stays available until Orca releases it, about 2 minutes after worker_done unless retained.
- Regenerated the bundled guides.
* feat(orchestration): receipts say when to end the turn
* feat(orchestration): tell the coordinator when a worker stops without worker_done
* test+docs: worker stop reports
* fix(orchestration): judge the empty-check stop with execution-host verdicts
* test: drop casts from worker stop tests
* Say that report-back requests still mean end the turn
* Say that report-back requests still mean end the turn
* fix(orchestration): stop reports wait for children, keep their Dispatch, and relay intact
* fix(orchestration): a stop belongs to the Dispatch active when it was seen; restored stamps announce nothing
* fix(orchestration): never say to stop while a remote worker runs
* Shrink the orchestration guide to the end-state workflow
* fix(orchestration): stop reports quote the agent's last words, or the screen for errors and prompts
* fix(orchestration): withhold the stop while chat failure mail is off
* test: a clean finish quotes the agent's last words
* fix(orchestration): stop asking workers for heartbeats
Workers are no longer told to send periodic heartbeats. A heartbeat that
still arrives from an older worker or peer only records last_heartbeat_at:
it is stored already handled, so it never lands in a coordinator inbox and
never wakes a coordinator or a check --wait. Removes the stale-heartbeat
warning and the heartbeat interval plumbing that only fed the preamble.
* fix(settings): remove the worker heartbeat controls
The Worker heartbeats switch and Heartbeat interval field only changed the
worker preamble text, which no longer mentions heartbeats. Saved values are
dropped on load as retired settings.
* fix(orchestration): wake a coordinator that reports program status but never sets a title
Program status only re-classified a pane that had a title, so a titleless
agent (agy) never got a live status and the wake gate refused it.
* fix(orchestration): a new Run no longer cuts a coordinator off from its earlier Run
* test(orchestration): drop heartbeat-batch cases the handled heartbeat row removed
* fix(orchestration): redact capabilities from a stop report's quoted output
* fix(orchestration): never wake a mailbox for a heartbeat
One rule at the runtime notification entry replaces per-call-site read
checks, so mutation replay and federated control-mail import stay silent
for heartbeats too.
* Shrink the orchestration references and worker preamble to the end-state workflow
* Name the older-Orca bind refusal as worker-start prints it
* Owner-fence test: a refused foreign ack changes nothing, whatever the worker's own check already handled
* Integration: drop the duplicate consumingCheck after merging #34043 and #35293
* Integration: await the worker-start next receipt before naming its Run
* Apply review round 1: drain to zero, release without auto-release, retry after stop, Run before a DAG
* Apply review round 2: start ready DAG Tasks, block when no failure wake, replay sends by request ID
* Apply review round 3: one receipt-based wait rule for starts and wakes
* fix(orchestration): a worker stopped without reporting needs action, and stop keeps its output
worker-list projected a stop-reported attempt as live, in_progress, no action. It now
projects finished_unverified with a worker-read recovery until mail reaches the worker.
worker-stop closed the terminal before anything archived it, so release reported the
archive unavailable; stop now archives the output first.
* Revert "Owner-fence test: a refused foreign ack changes nothing, whatever the worker's own check already handled"
This reverts commit 336ff91737.
* Revert "Merge #34043 (terminal mail guard, chat worker reuse) into integration"
This reverts commit 9c01b1a06e, reversing
changes made to d4b0c6c5f7.
* Revert "Merge #33720 (restart: attach surviving terminals) into integration"
This reverts commit d4b0c6c5f7, reversing
changes made to 53f9735bfe.
* Integration: restore #35293's check-methods after removing #34043
* fix(orchestration): bound the pre-stop archive and keep it through retain
* fix(orchestration): a failed pre-stop archive never blocks the stop
* fix(orchestration): answering a question says to end the turn while the worker runs
* fix(orchestration): a settled worker whose terminal moved owes nothing
* Cut the orchestration guide to what Orca does not already enforce or explain
* Drop the terminal-send recovery the CLI already prints
* Restore a short never-do block: no polling, no terminal steering, no hand-made checkouts
* Trigger on named-agent review requests, define failure in specs, show the reuse commands
* Restore six guide rules from the cut review and drop the preamble heartbeat block
* Integration: drop the removed heartbeat interval from preamble tests
* Drop the outside-Orca wait and run-use lines; Orca's errors teach both
* Release finished chat workers like terminal workers unless the user touched them
A finished chat worker now closes ~2 min after its accepted worker_done, like a
terminal worker. Clients report a touch when a chat is on screen at rest (opened
idle, or its turn ends on screen); the owning host keeps a finished worker's
chat on that report, until its automatic release commits the archive and closes
in the same tick. Chat workers arm only while every connected client advertises
the touch capability; old clients keep today's manual release.
* Decide an automatic chat close in the session lane, recheck clients there, re-touch after reconnect
The automatic close now asks the database in the chat's session lane right before
Stop: a touch until then keeps the chat, and a client that cannot report touches
(joined during the grace or after a restart) sends it back to manual release.
Touch reports wait for a read chat, so a reconnect re-reads and reports again.
* Keep explicit chat releases eager and re-touch a desktop chat after lost contact
* Resolve a chat touch by durable worker identity, so a closing chat's hidden tab stays touchable
* Keep the mobile touch report free of route and app-state hooks: shown counts as seen
* List workerChatTouch's identity fields and the close's optional admission in their census tests
* Release a settled remote worker from the home when its host predates automatic release
* Replace Keep Worker Open with an auto-close setting, and tell agents when an older server needs a Run
The coordinator's runtime decides whether finished workers close: it gates local arming, the
settlement ack's autoRelease opt-in to a remote host, and the home deadline for older hosts.
worker-start and run-create name an older server's one-Run-per-coordinator behaviour instead
of failing or rebinding silently.
* Escalate a parent's prompt or error even while its helper is open
* Report a chat touch when a worker chat is opened while working, and on each turn edge
* Record worker takeover when the host admits a person's chat send, so mobile sends keep the worker
* End a reported worker stop when the worker resumes, not only when Dispatch mail arrives
* Recheck a chat mail notice at admission so mail a check consumed starts no turn
* Type the resumed-turn stop test's pane move directly
* Keep the stop decision in an empty check, report muted chat failures as stops, and bind a new Run only once a start passes preflight
A start or reply receipt now sends the caller to drain its mail with check instead of ending its turn, so a mid-batch answer cannot skip a later report and a replayed receipt carries no stale stop. With chat error mail off, a failed chat request still reports a plain stop through the existing stop report path. worker-start creates and binds its Run just before the Task and Dispatch, so a start refused in preflight leaves no Run behind. worker-release help no longer says chats never auto-release.
* Reuse a Run a parallel first start bound, refuse dependencies before creating a Run, and relay a paired-server worker exit home as a stop report
* Read a reported worker stop against live agent status instead of recording resume observations
A stop report is mail the coordinator reads once. Whether a worker shows as
finished now comes from its live status: a fresh working agent status (local
pane, chat session, or the execution host's fleet snapshot) outranks the
report, so nothing needs clearing on resume.
* Drop agent steps Orca already covers: start receipts say Orca wakes you, a check asks for another only when a capped batch leaves mail, workers get no mail-check or ack lines, and chat errors always report with the exact error
* Keep the home's remote auto-release deadline until the host answers, and let a retain win at the send
Claiming a due deadline postpones it instead of moving it to a releasing state, so a restart or
a failed attempt runs it again; the release send rechecks the deadline with no await before it.
A host that cannot be asked at settlement still gets the deadline, and a host upgraded since
settlement is released by the home, since it never armed its own.
* Close a finished worker automatically only if the user never opened it
Seeing a worker's terminal or chat now writes the user's Keep record (owned,
retained) on its host, at any point before its close is admitted, so a worker
seen while it worked is never armed and a pending automatic close is cancelled;
the coordinator can still release, stop or re-engage it. Desktop reports from
the on-screen attention scan for every on-screen terminal pane and chat once a
present user is on that workspace; mobile reports the tab a session opens on
and each tab switch. The weaker chat-only touch hooks are removed. A chat send
admitted after the automatic close committed its archive now keeps the chat.
* Show only live facts for a worker that reported a stop
A stop report is escalation mail that wakes the coordinator once. worker-list
and worker-show no longer project it as finished_unverified with a recovery
action, so the live-working override that cleared that label goes too.
* Report a paired-server worker's process exit home even while its ask or check --wait is still registered
* Report a seen worker until its host records the keep, including chats shown before custody and mobile auto-selections
The touch reply now says pending while a structured worker's custody row is
not yet recorded; desktop and mobile keep a subject unreported after a
failed or pending reply and retry on the next scan, snapshot or reconnect.
Mobile reports whichever terminal or chat is displayed, tapped or selected
by a snapshot, instead of only the first per workspace.
* Record a person's chat send or command takeover inside the session lane
Takeover moves from the RPC wrappers into the host's in-lane acceptance
of userSend sends, /compact and /clear, so a close queued behind an
accepted send cannot admit before the keep, including during /compact's
handover wait. Host orchestration sends never set userSend.
* Say which stop reports a deliberate wait suppresses
* Align merged tests with the shorter preamble and the fixed start hint
* Retry an unrecorded mobile worker touch when the phone reconnects
* Drop the removed worker check line from the CLI boundary test
* fix(orchestration): wake a coordinator that survived an app restart
After a restart, main typed the mail wake only into an agent whose status it
had seen live since starting, so a coordinator whose turn had already ended
never woke. At reattach, take the agent's own last hook report, which the hook
server restores from disk and from its offline spool, as that observation while
an agent still holds the surviving process.
* fix(orchestration): restore the lead's own turn, hold a restored draft, fence respawns
Read the lead agent's turn from the restored report so background work does
not hide an ended turn, keep the wake out of a composer that still holds text
typed before the restart, and drop a restore that a respawn has overtaken.
* fix(orchestration): restore a reattached status only from a current screen without a draft
The whole-screen accessor hides a model the provider still owns after attach, so a
draft there read as none. Read the screen the way wait gates do, provider image
included, and decline the restoration when it is unavailable.
* fix(orchestration): restore a reattached status without reading the screen
After a restart main has no record of typing, so the existing draft hold cannot
apply; a screen read here could miss a draft and, when slow, strand the
coordinator for good. A draft left before the restart now meets the same rule
as an abandoned one.
* fix(orchestration): let a slow foreground probe still restore a reattached status
A probe answering after the interactive two-second bound was dropped for good,
stranding the coordinator. Restoration has no caller waiting, so it takes the
real answer; the existing fences still guard application.
* test(orchestration): mark the slow foreground probe as fake-clock driven
* Report a terminal worker whose agent died while its shell lives
A killed agent sends no stop hook and its shell keeps the PTY open, so its
Dispatch stayed open and the coordinator was never woken. The shell's
command-finished already retires the PTY's launched-agent authority; the
panes it retires now go to the worker stop reporter as an 'exited' stop
(same mail and wake as a PTY exit, once per Dispatch, none once settled).
* refactor(orchestration): key mail, waits and settle checks by terminal
Reapplies #34056 on the integrated orchestration work: mail delivery, the
settle recheck and terminal waits are keyed by ptyId instead of the window
pane, deleting the pane-keyed leaf lane and the headless-only PTY lane.
Keeps #34706's delivery rule (a terminal taking input, idle or mid-turn,
gets the wake; dialogs, permission prompts and unsent drafts hold it; the
cold-park fence still defers a parked Enter) and #35274's multi-Run
coordinator mailboxes.
* fix(orchestration): keep best-effort delivery's catch; stage the remount e2e
deliverForHandle keeps the integration branch's catch: ownership resolution
still reads SQLite, and a notification queued before teardown must not throw.
The remount e2e now asserts each stage on its own (mid-turn mail before the
workspace opens, the wait across the remount, mail after it), since #34706
types mail mid-turn and the old single mail check could pass before the
remount happened.
* refactor(orchestration): settle a new terminal wait from its first reading
A wait now keeps the PTY record it resolved, and nothing runs between the
first evaluation and the waiter's registration, so the second evaluation
re-read the same evidence. Starts the poll from the first verdict instead.
Deletes the leaf wait-result builders the leaf lane left without callers,
and adds a unit test that a tui-idle wait survives its pane remounting
(the e2e cannot order the wait's registration before the remount).
* Report a dead worker agent only once its shell is proven alone
A command-finished marker alone does not prove the launched agent exited: a
nested interactive shell in a live worker emits the same marker. The exit
report now waits for the execution host's shell-alone proof and is fenced to
the Dispatch and launch seen at the marker, so a relaunch in the pane is not
reported by an older completion. It no longer hangs on launch-authority
retirement, so a nested completion that retires metadata does not stop a later
real death from being reported. The agent-exited fact feeds the same path for
shells without OSC 133.
The shell-alone report and a paired-server worker's PTY exit share one exit
entry point and key, so the Run home gets one report per process.
* fix(orchestration): resolve a terminal's mailbox across every pane that shows it
Two panes can show one PTY; ownership read only the first listed pane, so a
Run bound to the other was never woken. The mailbox terminal now carries
every pane alias and ownership, discovery and the delayed-Enter recheck
consult them all.
* Report a killed worker agent from its launch's exit receipt
The launch command now ends with a per-shell marker the shell prints once
the agent returns, however it ended. The execution host scans it before
thinning (main and daemon), checks it against the PTY's current launch and
incarnation, and reports through reportWorkerExit. A nested shell has no
receipt and a relaunch names a new one, so the shell-alone inference is gone.
A later local PTY exit reuses the same exit message id, so it settles the
Dispatch without a second report.
* Revert "Revert "Merge #33720 (restart: attach surviving terminals) into integration""
Reapplies survivor attach (72b3b79fd3, fe906ea2a2, f46777ba18) so the
#33720 merge that follows carries it; integration reverted it in 2f945fa715.
The output clock now feeds v3's terminal-keyed wait path; the leaf lane it
also fed is gone in v3.
* test(orchestration): give exit-path DB stubs the remote-attachment lookup
The paired-server exit relay now asks the Orchestration DB for an active remote
attachment on every local pty exit; partial stubs without it threw.
* Report a worker killed after a restart from its Dispatch's launch commitment
The exit receipt ID is now derived from the launch-token hash a Dispatch
persists, so a PTY reattached after restart (no launch token in memory)
accepts its receipt when the pane's active Dispatch committed that launch
in the same shell process.
* test(orchestration): stub main's session-dispatch presentation read in the stale-leaf DB
Main's projection scope now reads listSessionDispatchesForPresentation on every
projection; v3's hand-rolled stub predates it.
* test(orchestration): drop the stale-leaf stub key integration's merge now supplies
* test(orchestration): align main's new tests with integration's mid-turn mail, admitted close and nameless worktrees
Main's titleless-turn test assumed mail waits for Stop; v3 types it into a working agent.
Main dropped the --name requirement, so that preflight case now fails on the missing repo.
The evict close now forwards the session lane's admitClose.
* perf(orchestration): read the next federated release deadline through its partial index
The armed-state filter alone cannot use the non-null partial index, so every rearm walked retained federation history.
* perf(terminal): keep unviewed restart survivors to the daemon's live window
Main now attaches every surviving terminal at startup; each mirror took the full
5,000-row depth with no viewer. A survivor nobody views keeps the 1,000 rows the
daemon itself holds, and grows to full depth from those rows once a view subscribes.
* chore(orchestration): clear check:changed findings on the main merge
Format a listing statement, prune the flaky-pattern baseline, and justify or remove the
test casts the changed-code gate flags.
* Revert the unviewed-survivor mirror cap: it can lose desktop history after a restart
A capped survivor mirror is still served as complete history to desktop recovery, and a desktop pane
added after inventory never lifts the cap. Restart memory for unviewed survivors moves to a follow-up
that defers the screen model instead of truncating it.
This reverts commit 4ea934ca7f.
* Key main's new null-agent idle-wait test by terminal, as integration's waits are
* fix(orchestration): type mid-turn mail only into a recognized agent
An unrecognized terminal's working verdict may be a running program reading stdin,
so null-agent panes keep waiting for quiet before the pointer is typed.
* Remove killed-worker exit receipts from orchestration v3
The launch-bound receipt added a visible printf to every agent launch line. Owner decision: ship v3
without killed-worker detection (behaves as main does today) and revisit it later, e.g. by watching the
agent's hook-reported process.
This reverts merge b9a30b6e74.
* Stop re-arming a delivery recheck once the quiet window has passed
A refusal that outlives the quiet window (an unrecognized terminal still reading as working) is not
time-bound, so a 50 ms recheck spun forever. The next output, title or mail edge rechecks it.
* Keep retrying deliverable mail past the quiet window; gate mid-turn delivery on terminal agent identity
A refusal outliving the quiet window can wait on a hook final-frame deadline or a late foreground
recognition, neither of which emits a delivery edge, so poll slowly while that terminal still has
deliverable mail and stop once none is pending. Mid-turn delivery now asks whether the terminal agent
is recognized at all, not whether it has readiness rules, so a recognized reusable agent keeps it.
* Keep structured-agent-session.ts within the 300-line cap
* fix(orchestration): arm delivery rechecks only for actionable delivery work
The recheck predicate now counts persisted pointer reservations awaiting
recovery as well as selectable new mail, and gates every recheck (quiet
window, post-quiet, and holds) on it, using the canonical output clock.
* Check the served orchestration guide by a heading the v3 guide keeps
* test(e2e): launch the mail-pane fake under its agent CLI's name
v3 types mid-turn mail only into a recognized terminal agent, and a title alone no longer
recognizes one, so the fake runs as `node …/codex` (or cursor-agent) like an npm shim.
The hold-while-working case now models the unrecognized program that contract still holds for.
* test(e2e): align idle mail delivery spec with v3 auto-ack, mid-turn Enter and multi-Run coordinators
A consuming check now marks its batch handled (8fbb395a32), so the live
waiter's mail is pulled once returned and the held-batch case is seeded
as an older Orca leaves it. Agents queue mid-turn input (e0cb9a68d2), so
the held reminder's Enter is no longer withheld. A coordinator keeps its
earlier Run (#35274), so Run A direct mail is pointed with --run A.
* Wake a Run's coordinator through its pane when the Run's stored terminal handle belongs to the pane's previous PTY
* Make check --ack acknowledge only, so it never takes new mail
A check carrying --ack acknowledged that Delivery and then took (and,
since checks now acknowledge what they show, consumed) the next batch.
A caller that discarded the output lost that mail. --ack now returns
after acknowledging; newer mail stays unread, so the wake path still
fires and the next plain check shows it. The receipt says --ack is not
needed. Removes the ack-then-take receipts this made dead.
* Print every message body and payload in a plain orchestration check, since current hosts acknowledge the batch on read
* Keep acknowledge-then-take for check --ack --wait, and reject --ack on direct mail
A waiting caller reads what the wait takes, so --ack --wait acknowledges
and then waits for and takes the next batch, as before; --ack alone
stays acknowledge-only. Direct mail has no Delivery, so --ack there now
fails as a foreign delivery instead of consuming the mail.
* Keep a user-kept worker terminal kept when a new Dispatch reuses it, since its on-screen pane reports only once
* Tell a coordinator to check a remote worker itself when its host cannot report turn stops
* Find a Run's pane terminal for mail without re-issuing its handle mid-reload
* Keep the original ack-then-take path for check --ack --wait
Composing an ack with a second check lost the acknowledged consumer
generation and persisted subcall receipts. --ack --wait now runs the
original single-generation path unchanged; only --ack without --wait
returns after acknowledging, and direct mail still rejects --ack.
* Settle the e2e agent idle before newer mail so the mid-turn pointer cannot race the idle title
* Record a user's view of a worker terminal as user_seen so only it, not a coordinator's retain, survives reuse by a new Dispatch
* Let a worker ask, end its turn, and be woken with the answer
* Drop casts from the ask tests and the pending-question query
* Tell agents to run a plain check after acknowledging a held Delivery
--ack without --wait no longer takes newer mail, so the held-delivery
pointer now names the follow-up check for the new messages.
* Deliver Run and Dispatch mail to the pane's current PTY, issuing its handle only when none exists
* Wait for a PTY's exported handle before mail, and wake it when that handle is adopted
* Keep a cancelled ask from taking its answer, scope the asked-question stop mute to the asking turn, and end a waiting ask when its Dispatch settles
* Order the asked-question stop mute by message sequence, not same-second timestamps
* Wake a PTY's deferred mail whenever it gets a handle, by any path
* Make the headless Dispatch adoption test hold in both layout modes
* Mock the finished-worker strip states with neutral pane and chat notice fixtures
* Mock the temporary-worker strip with the owner's copy and the Allow auto-close tab menu item
* Mock chat workers with a goal-style composer strip instead of the composer notice
* Keep a worker open only by Keep open; hold its countdown while its agent works again
* Remove viewing and typing as implicit keeps on desktop and mobile
* Update the routing specs to acknowledge a held Delivery, then take with a plain check
* Show the temporary-worker strip with Keep open and its countdown, and Allow Auto-Close in tab menus
* Share the worker auto-close poll and key its read to the subject
* Re-read kept workers often so Allow Auto-Close shows its countdown promptly
* Hold auto-close through every turn, refuse stopping kept workers before anything changes, and read worker state only for known workers
* Keep a claimed close final, check the agent before claiming, refuse remote stops without a Keep open answer, and keep re-reading known workers
* Classify workerChatTouch caller fields and drop a test-only cast
* feat(cli): open a browser tab in a split pane with `tab create --split`
`orca tab create` could only add a tab to an existing pane, so an agent
had no way to put a page beside its terminal. `--split <right|left|down|up>`
creates a new pane next to the calling terminal (ORCA_TAB_ID), falling back
to the active pane, and opens the page there without taking focus.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UNtbMA9iVj9T4rBUjn5u6W
* refactor(browser): share one type for the tab-create IPC payload
The preload listener, its callback, the preload API contract and main's
sender each declared the payload separately, and the listener copy had
already drifted from the new split fields.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix(browser): open the CLI split pane and its tab in one step
Creating an empty group and then filling it fails when main owns the
layout, because the window's group doesn't exist until main's frame
lands. createBrowserTab's split option carries both to whichever owner
draws them, so the rollback for a half-made pane goes away.
SSH hosts already cannot choose a new tab's group, so their CLI's split
is stripped like targetGroupId.
* fix(browser): split in the caller's workspace and refuse splits that can't happen
A CLI run outside its workspace's directory sends no workspace, so the
renderer fell back to the active one and missed the caller's terminal.
The caller's tab now picks the workspace when none was named.
An SSH host's split and an empty --split= both turned into a plain tab
reported as success; both are refused instead.
---------
Co-authored-by: Kalvin Mizzi <kalvin@mizzi.com>
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* feat(browser): list restored tabs in tab list and load them on demand
After a restart Orca restores browser tabs lazily: a tab gets a page only once
the user opens it. tab list only reported tabs with a live page, so an agent in
a worktree with 26 restored tabs saw one and concluded there were none.
tab list now reads the tab bar from the session snapshot the renderer already
publishes on every tab change, and reports every tab in tab-bar order. Tabs
without a page carry loaded: false. tab switch and tab close --index resolve
indexes against the same list, and switching to an unloaded tab loads it in
the background first. Waking a page now also waits for its first load to
finish, so the next command does not read a blank page.
Headless serve keeps every page live, so it lists as before.
* fix(browser): list the tab bar even when Orca has no window open
With the window closed the app keeps running and its restored tabs still exist,
so tab list should report them. Headless snapshots are built from live pages
only, and the merge dedupes those, so dropping the window check lists nothing
extra there.
* fix(browser): list an id held by a live page and a client page once
* fix(browser): wait for the first load of a tab headless serve wakes
Headless serve starts a restored page and returned at once, so the next
command could read a blank page mid-load. It now waits for the first load,
as the window path already did.
* refactor(browser): keep the tab listing beside the browser tab catalog
Main moved the runtime browser commands into runtime/browser/ since this was
written. Also drops a window lookup the catalog no longer uses, and corrects the
headless note: those snapshots list saved pages that have not started yet.
* fix(browser): keep paired-server mirrors out of tab list and close indexed rows like --page
A window also publishes the browser tabs it mirrors from paired runtimes,
which this host can never load, so the tab bar is read only for workspaces
this host owns. tab close --index now closes the listed row exactly as
--page does, keeping its worktree, so an unstarted headless tab is retired
instead of reported closed and left saved. With nothing active, the first
live page is marked current again, matching where a pageless command goes.
* fix(browser): wait for first load only on tab switch, and show tab indexes from the listing
Every --page command wakes an unloaded page, including the tab show a
remote browser pane awaits before streaming, so waiting up to 10 s for the
first load there held the stream back. Only tab switch waits now. tab show
reports a tab's index from the same listing tab list and close use.
* fix(browser): list restored tabs in an SSH host's bridged workspace, and reject fractional close indexes
An SSH host's workspace can have no repo row on the desktop, yet its pages
render in the desktop window, so the bridge's scoped workspace counts as
this host's own. A non-integer --index no longer falls through to closing
the active tab.
* test(browser): give the restored-tabs e2e's timeout and lease wait their reasons
* test(browser): read restored-tabs RPC results through the shared e2e reader
Reuses the browser e2e rpc helper instead of a local Reflect.get copy, and
types the listing test's snapshot rows.
* fix(browser): index tab show in the caller's scope, as tab list does
* fix(browser): report an out-of-range close index as browser_tab_not_found
Matches tab switch, so agents can recover by re-listing. The restored-tabs
e2e now asserts the raw loaded value instead of coercing a missing one.
---------
Co-authored-by: fanzzzd <fanzzzd@outlook.com>
* feat(browser): upload through picker buttons in any frame
* fix(browser): catch pickers the page opens for a frame button and click SVG controls
* docs(cli): note server-hosted pages need the file input ref for upload
* test(browser): assert both picker interceptions are released
* refactor(browser): flatten picker upload and arm frame sessions in parallel
* test(browser): emit picker events through a real emitter instead of Reflect.apply
* feat(browser): let agents drive popup windows like OAuth sign-in as pages
window.open popups that keep their opener stay native windows, but the
agent bridge now lists each one in tab list as popup-<n> with its opener,
so --page, tab switch and tab close reach it. When a popup the agent
switched into closes, its next command lands on the opener.
* fix(browser): reach popups over SSH, through the Electron sidecar, and by implicit tab close
* fix(browser): keep sidecar popups ordered after tabs and handing back to their opener
* fix(browser): skip the tab wake-up wait for popups and keep the agent's claim when a popup hands back
* fix(browser): refresh the opener's claim on hand-back and settle tab close after the popup is gone
* refactor(browser): share routing retarget and idle-window helpers for popup hand-back
* refactor(browser): move popup routing helpers into bridge state to keep tabs under its line cap
* test(browser): expect the popup's url and title in its snapshot result
* feat(browser): typed snapshot flags and screenshots saved as files for agents
orca snapshot takes --interactive, --compact, --depth, --selector, --urls,
--delta and --full, passed to agent-browser on every route. The header
now shows the page title and URL. orca screenshot and full-screenshot save
the image where the CLI runs and print its path, in CSS pixels, with
--if-changed and --annotate. Flag help for exec, wait and download is
written for those commands, and the orca-cli guide sends web pages to
Orca's browser unless the user picked another tool.
* fix(browser): scale screenshots by the scrollbar-free axis and keep snapshot metadata behind SSH admission
* fix(browser): upscale low-DPR screenshots and wrap a torn-down tab's screenshot error
* fix(browser): give each screenshot its own file and keep typed screenshot errors
* refactor(browser): share the agent-browser screenshot reader between Electron and orcad
* refactor(browser): move snapshot and screenshot params under the line cap
* Keep CLI-removed worktree branches unless requested
* Bind branch policy checks to removal connections
* Remove redundant local default removal test row
* Negotiate worktree branch policy on the mutation connection
* Fix removal integration compiler boundaries and type imports
* Use checked annotations in paired removal fixtures
* Reset CLI integration exit status across test runtimes
* fix(browser): let agents and users answer page alert, confirm and prompt dialogs on their page
* fix(browser): watch a replacement guest for dialogs and ignore the opening keypress
* fix(browser): ignore a repeated Enter in a guarded prompt field
* fix(browser): fill, select, upload and type act on the agent's element or fail
* refactor(browser): move agent key commands into their own bridge layer; fix test sender call
Orca's will-download handler picks every guest download's save path, so
agent-browser's own download (CDP download dir plus guid rename) never saw
the file: it landed in ~/Downloads and the command failed with a GUID error,
or after 30s when nothing downloaded. The bridge now claims the page's next
download for the requested path, clicks through agent-browser, and reports
the saved path, a 10s no-download error, or a failed download.
* fix(computer-use): replace the macOS permission status gate with one 5s launch floor (#34390)
Follows up #36028. The earlier gate grew background/explicit flags, epochs,
backoff and a setup pgrep path that reviewers could not make correct.
- Status: one probe at a time and one 5s launch floor shared by every reader, so
every path stays at <=12 helper launches/min. Readers inside the floor join the
running probe or ride one trailing probe that fires only if someone waits.
Only grants are cached (until the floor expires); denials and errors are never
served, so a grant shows within one floor locally and on web. No app epochs:
without a denial cache they bought nothing. Off macOS the gate is skipped.
- Setup: one launch per 5s across every permission, claimed synchronously; a
request inside the window is queued (latest wins) and reported as
launchQueued. Kill-and-relaunch stays so a click always re-shows the helper.
Setup reuses the gate's in-flight/cached/last result instead of probing.
- Reset checks helper availability from the bundle and invalidates after any
tccutil attempt, including partial failures.
- Remove the background flag from preload/IPC/renderer/web, the app-activity
binding, and the sidecar permission_denied invalidation.
* fix(computer-use): close the remaining gaps in the permission launch floor (#34390)
- Clear the trailing timer whenever any probe launches and re-check the floor
when it fires, so a late timer can never launch inside the floor.
- Setup reuses a denial only until the floor expires.
- A reader that joins a probe older than 300ms and gets a denial rides the next
probe, so a grant shows within about one floor even after a stale web/RPC probe.
- Setup requests are numbered on arrival, including ones that coalesce, so the
latest request wins (A, B, A launches A); a queued launch already covered by a
newer launch is dropped. Reset and will-quit cancel any queued launch.
- The settings pane says "Opening…" and the CLI says queued for queued launches.
* fix(computer-use): measure permission launch floors from real spawns and cancel setup on every host (#34390)
- Both 5s floors use performance.now, so a wall-clock step cannot stretch or skip them.
- The status floor counts from the later of claim and the actual `open` spawn, and
the setup window from after its spawn, so a slow mkdtemp or pkill can't allow a
13th spawn in a 60s window.
- Setup cancellation registers through AppEnvironment quit handlers (desktop,
headless Electron serve, orcad) and orcad's shutdown trigger; reset and
shutdown bump a generation so an Open still waiting on status never launches.
- Reset cancels queued setup before its first await.
- A setup request leaves the coalescing map when it launches, so a later request
for the same permission queues and wins (latest-wins across microtasks).
- A failed probe clears the remembered denial.
* fix(computer-use): drop setup coalescing and gate setup on a host-wide shutdown flag (#34390)
- Remove the per-permission setupInFlight map. Every Open goes through the 5s
window and seq-ordered queue; a queued request with the same args that arrived
before the last spawn was already shown by it, so concurrent same-permission
Opens still spawn once. This fixes stale entries after reset turning the next
Open into a no-op or a cancelled one.
- A cancelled Open (reset or shutdown) rejects with an error instead of returning
launchedHelper: false, which every client rendered as "setup complete".
- Replace the per-host cancel calls with src/main/host-shutdown-state.ts, set
synchronously by Electron will-quit and orcad's shutdown admission; setup
checks it before every spawn, including the queued timer.
- Track the status cache's expiry from the probe that produced it, so starting a
new probe cannot revive an expired grant.
- The queued setup timer re-checks its deadline and re-arms when early, and both
timers round delays up; a throwing spawn there is logged, not uncaught.
* fix(computer-use): keep setup latest-wins after slow probes and surface cancelled setups (#34390)
- Record the launching request's seq; an older request that resumes or is queued
after a newer one spawned is dropped, so latest-wins holds when requests
resume out of order behind a probe.
- orcad sets the host shutdown flag on every cleanup entry, including failed
startup.
- The web facade only falls back for hosts without computer.permissions; other
failures, such as a cancelled Open, reject so the pane and onboarding show them.
- The cancellation check runs before an untargeted Open can report everything granted.
- Opens that arrive mid-reset wait for it, so reset's helper cleanup cannot kill
what they open.
- Queued wording now says a newer request or a reset may replace it.
* fix(computer-use): wait out a reset before an Open reads permission status (#34390)
* feat(computer): send tree diffs after actions and add get-app-state --query
Action results now carry only the accessibility-tree lines that changed since
the caller's last view of the same window (~ changed, + added, - removed as
index ranges, or an explicit no-change line), plus the focused element. The
runtime sidecar keeps the last tree per session/worktree and app, so all three
providers get it. The CLI opts in with treeDiff; older runtimes strip the
param and keep returning the full tree, and --full-tree opts out.
The macOS helper now keeps an element's index across snapshots of a window:
AX identity first, then the next unclaimed index with the same signature for
views that rebuild their AX objects, and never reuses a removed index.
get-app-state --query prints matching elements with their ancestors and
--max-elements caps the output, both in the CLI over the rendered tree.
Custom action names with raw newlines no longer split an element over lines.
* fix(computer): preserve parent changes in snapshot diffs
* fix(computer): refuse stale index reuse for lookalike controls
* fix(computer): print full trees in action replies
* fix(computer): keep controls located in snapshot replies
* fix(computer): fail set-value when its read-back shows a different value
A value_mismatch came back as ok with exit 0, so callers that check only
the exit status took an ignored or misplaced write as success. The runtime
now turns it into a verification_failed error at the sidecar boundary,
which covers every provider and every caller of the RPC.
Part of #33511
* fix(computer): pair macOS AX windows with their CGWindowID
AppKit and WebKit windows don't answer AXWindowNumber, so matching a
capture to its accessibility window fell back to frames. Two windows with
the same frame then paired the screenshot of one with the tree and title
of whichever AX listed first, under the first one's id. Read the id with
_AXUIElementGetWindow, as yabai and Hammerspoon do, and keep AXWindowNumber
as the fallback.
Fixes#27252
* fix(computer): fail fast when a macOS app stops answering accessibility
Every request runs behind one helper lock, and a hung app cost a timeout
per AX read, so one get-app-state on it held every agent for up to the 60 s
RPC timeout. Pin the AX messaging timeout at 1.5 s, refuse an app that
doesn't answer a root probe, and stop a tree walk at the first read that
waits out the timeout, each with an action_timeout error.
A press or write that the app received but didn't answer now fails the
same way, saying it may have taken effect. Before, the click fell through
to AXConfirm and then a synthetic click, so a button whose handler blocked
ran twice, and type-text typed the text again as keys.
* fix(computer): report macOS accessibility actions that changed nothing
AXPress and other accessibility actions came back as plain unasserted
success even when the app ignored them, as Chromium does for a role=button
whose handler sits on a child. After such an action the helper now compares
the target's tree, frame and on-screen windows with the snapshot it took
just before. If they still match after re-reading for about a second, the
result says unverified/suspected_noop; if they change late, the result
carries the settled state instead.
The new reason is additive; older CLIs print it like any other reason.
Refs #31758
* fix(computer): propagate late macOS observation failures
* fix(computer): select existing text before replacement
* fix(computer): share native macOS window identity
* feat(computer): drive macOS apps in the background by default
Clicks no longer activate and raise the target first. Pointer and key
input go to the target window's pid through a new BackgroundInputTransport:
mouse and scroll events carry the window id in field 51 and a window-local
location, keys run inside a focus-without-raise key-window scope, and
chords carry no Unicode string so menu key equivalents fire. Scroll and
drag now land (#27306); typed text no longer doubles in Electron (#17942).
The HID tap and focus fence stay for --restore-window only. Results
report action.delivery, the handshake reports supports.input.background,
and a missing private symbol or a popup click fails with
background_unavailable instead of falling back to the foreground.
* test(computer): read typed key strings back instead of diffing live-state events
* fix(computer): keep Unicode characters in one key event
* fix(computer): preserve active macOS key windows
Refuse key-window changes in the active app and surface failed
focus records, including cleanup after partially delivered input.
* fix(computer): guard macOS click routes before delivery
* fix(computer): let paste events read the clipboard
* fix(computer): classify clicks in the requested macOS window
* fix(computer): fence macOS scroll and drag recipients
The agent-browser bridge cast agent-browser's {messages} and {requests} output to Orca's {entries, truncated} contract and dropped --limit, so text mode crashed and --json returned the raw shape. Map the output once at the bridge, keep the newest --limit entries, and make the contract fields agent-browser never reports optional.
The host answers a worktree delete as soon as it accepts it and lets Git
delete the checkout in the background. Clients that show a "removing"
marker ask it to wait for Git, but the CLI could not, so it printed
`removed: true` before anything was deleted, and a delete Git then refused
(for example a checkout with submodules) failed only in the host's log.
Scripts saw success, and every retry repeated the same silent failure.
`worktree.rm` takes an optional `waitForBackgroundRemoval` flag, and the CLI
sets it, so the command exits with Git's real result or error. It waits as
long as the desktop and web clients do and, if it stops waiting first, says
the delete may still be running and how to check. A reply sent on
acceptance now says `removed: false` alongside `removing: true`, so callers
that still get the early answer are not told the checkout is gone. Older
hosts ignore the flag, and the CLI then says the delete is still running.
Fixes#35135
* Nest chat-UI orchestration workers under the agent that started them
Main's lineage projection only walked terminal panes, so workers running
in the chat UI never got a parent link and listed flat in the sidebar.
It now also projects chat workers, keyed by their visible chat row, and
resolves a chat creator or coordinator to that chat's visible row
instead of its handle or private mailbox pane key.
* Fix public worker lineage across assignment and row identities
* Complete terminal lineage provenance and bound active session selection
* Repair lineage test runtime boundaries and SQLite counters
* Batch public lineage verification after exact recency selection
* Use checked runtime values in lineage integration tests
* Document the trusted Dispatch SQL row boundary
* Keep lineage integration imports within their test programs
* Load native lineage fixtures before test execution
* test: complete lineage inputs in runtime and sidebar fixtures
* test: seed benchmark facts from active dispatches
* test: replace partial orchestration DB casts with typed fixtures
* test: complete stale-leaf mailbox fixture session input
* fix(test): render worker lineage fixture with production list
Explain the worker-stop receipt's processAction values in the recovery
guide and command notes: closed_agent_terminal means Orca already issued
the close (no follow-up terminal close), and stop_unknown exits 1 while
possibly still reporting closed_agent_terminal.
Fixes#13197
Co-authored-by: Neil <4138956+nwparker@users.noreply.github.com>
Neil
Jinwoo Hong
Brennan Benson
OrcaWinandOrcaWin
BingZandNeil