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>
* 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
* 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
* 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
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.
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>
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
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>
* 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.
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
* feat(cli): list and read agents by their Orca session ID with orca agent list/show/read
Live terminal and chat agents are listed, shown and read by Orca session ID on the selected host; sleeping native agents can be shown and read by ID. Chat reads walk the chat's own bounded history pages back to the latest /clear.
* fix(cli): agent show names a live agent and its last reply as agent list does; help says sleeping terminal agents aren't listed yet
* Bound agent reads and scoped workspace inventories
* fix(cli): agent read carries the conversation's state, so a running chat turn reads as working
agent read now reports the same state agent list/show report, from the same status
rows, in text (a leading state line) and --json (state). A turn still running no
longer reads like a finished chat with no reply.
* Fix agent conversation read consistency and limits
* fix(cli): agent read derives its state from the history it returns
agent read no longer samples live status. A chat's state comes from the
journal snapshot that produced its entries: an open turn or an accepted
send with no turn yet reads working; done needs an explicitly successful
latest turn whose reply is the newest entry shown. A terminal agent's
state comes from the provider turn markers in the same transcript bytes:
a prompt with no end after it reads working, done needs an explicit end
(Claude stop_reason, Codex task_complete) with the reply as the newest
entry. Anything else omits state. The journal lane wait added for the
live state is removed.
* Tighten agent read snapshot evidence
* Keep agent read done for finished turns
A dead owner now only voids working. Codex completion is proved by the turn's own
decoded reply rather than row adjacency, and Claude's by its end row's own reply,
without needing the prompt inside the read window.
* Adapt agent commands to reorganized shared contracts
* Warn on incomplete agent lists, read sleeping transcript paths, and retry unanswered provider id lookups
* Follow main's moved shared modules
* Bound live transcript recovery to conversation panes
* Show sleeping terminal agents where agent list lists them
agent list lists a finished terminal agent while its pane sleeps, since main keeps
that status row. agent show now counts the same sleeping place, and the help says
which sleeping agents are listed. Messaging still ignores sleeping panes.
* Clarify sleeping agent discovery and messaging help
* Say sleeping terminal agents can't be messaged and note the WSL read exception
* Follow the moved CLI argument boundary after rebasing
* Show plain Orca session IDs in agent command help
* Expect plain UUID Orca session IDs in the transcript source test
* Follow main's moved shared modules after rebasing
* Name Orca session IDs <id> in agent help, since older IDs keep their agent prefix
* Follow main's moved agent-session modules after rebasing
* feat(workspace-cleanup): delete chat history of deleted workspaces
Adds an off-by-default host setting. When on, each cleanup run deletes agent
transcripts whose Orca workspace folder no longer exists, through AI Vault's
validated delete, and reports the count and space in the run's activity.
* fix(workspace-cleanup): keep chat history of folders Orca never made a workspace
Skip workspace parents that are or hold a project checkout, protect folders
holding a still-listed workspace in any spelling, re-check each folder right
before deleting, batch scope paths, count companion bytes, sweep chats at most
every 6 hours on hourly runs, and refresh the report when the switch changes.
* fix(workspace-cleanup): treat only nested Orca workspace folders as deletable
Look for deleted workspaces only in <root>/<repo> of nested layouts, protect
renamed workspaces' earlier paths, folder workspaces and case variants, use the
recorded cwd only, re-check the parent and the setting before each deletion.
* fix(workspace-cleanup): protect flat workspaces and per-host rows from the chat sweep
Drop parents inside a still-listed workspace, also read this host's own
worktree rows, record a run only when a rule or a due chat sweep has work,
and cache per-folder protection with precomputed matchers.
* fix(workspace-cleanup): find deleted workspace folders by filesystem identity
Walk up from the recorded cwd to the deepest existing folder and require it to
be, by device and inode, an Orca <root>/<repo> folder without .git; key
protected paths the same way, so symlinks, case and Unicode spellings are the
OS's call. A failed history scan no longer fails the run, and an open session
history list refreshes after chats are deleted.
* fix(workspace-cleanup): close the remaining chat sweep gaps
Walk physical ancestors of a symlinked parent, skip a gone folder with a
lookalike sibling (parsers trim cwd), re-read listed paths after the scan,
never touch WSL paths, use bigint file identity, and report the next run
that actually sweeps when only chat history is on.
* fix(workspace-cleanup): keep chats resumed elsewhere and follow dangling listed links
Before deleting, re-read each transcript: skip it if it was written in the last
hour or its last recorded cwd is outside the gone folder (a chat resumed at a
live workspace's root). Listed symlinks protect their targets, and parents are
re-checked against the listed paths read after the scan.
* fix(workspace-cleanup): sweep only Claude chats, whose every message records its cwd
Keep a transcript unless its latest recorded cwd, read back past large blobs,
is still in the gone folder; agents that record cwd once can't prove a chat
wasn't resumed elsewhere. Follow symlinks along listed paths, dangling ones too.
* fix(workspace-cleanup): read only a record's own cwd and check each chat right before removal
Parse whole JSONL records backwards and use their top-level cwd, not tool
arguments; run the setting, folder, idle and last-cwd checks right before each
transcript's removal; resolve relative listed links from their real folder.
* fix(workspace-cleanup): protect subagent transcripts and re-read listed rows per folder
Check a chat's companion transcripts with the same idle and last-cwd rules,
read Orca's listed rows right before each gone folder's deletion, keep '..'
in listed link targets for the OS to resolve, and say Claude Code in the copy.
* fix(workspace-cleanup): fold names fully, keep POSIX repo names, re-stat rows only on change
Fold case with upper then lower (final sigma), take the repo name with this
host's basename, re-read listed rows per folder only when the catalog changed,
and sweep chats even when rule evaluation fails.
* fix(workspace-cleanup): re-check the chat itself after walking its companions
A chat resumed while its subagent transcripts were being checked has a new size
or mtime, so it is kept.
* chore(workspace-cleanup): sync localization catalogs and drop a cast in the cwd reader
* fix(workspace-cleanup): re-check every subagent transcript after the companion walk
Record each companion's version and require the same set, unchanged, before
approving deletion; skip the symlink-based sweep test on Windows.
* fix(workspace-cleanup): protect chats by what listed paths pass through, checked per chat
Each listed path claims the (existing folder, name) pairs along it, so a gone
folder holding one stays protected whether that path exists right now or not;
claims are re-read before every removal, and an unfollowable symlink chain
stops the sweep.
* fix(workspace-cleanup): an unreadable folder or a non-directory leaves the sweep fail-closed or ignored
A stat error other than absence while reading listed paths marks the snapshot
incomplete; ENOTDIR counts as absence instead of stopping every sweep.
* fix(workspace-cleanup): check row protection last before each removal and allow exactly eight links
Run the slow transcript checks first so the folder and listed-row checks are
the freshest before the rm, and resolve the eighth link instead of treating
it as an unfollowable chain.
* chore(workspace-cleanup): follow the shared settings and execution-host module moves
* chore(workspace-cleanup): mark an unreadable identity as undefined, not a string literal
* fix(workspace-cleanup): re-read protection when a listed symlink is retargeted
Listed paths that go through a symlink record where they led; a different
target before a removal re-reads every claim.
README, its translations and the mobile docs now send Android readers to the Play
listing first and keep orca.dev/download/android as the APK fallback. The
Simplified Chinese README keeps the APK link only, since Play is unreachable in
mainland China.
Co-authored-by: Claude <noreply@anthropic.com>
With "open links in Orca" on and an SSH host's browsing set to "This
device", links from SSH and managed-SSH workspaces (terminal, native chat,
markdown, dashboard preview, app links) skipped Orca's browser and went to
the system browser, even though New Browser Tab already opened a desktop
tab in that workspace.
canOpenRemoteLinkInWorkspaceBrowser now owns the remote-link rule in
lib/browser and passes allowSshDeviceBrowser (only while links open in
Orca) to the SSH route predicates, and executeHttpLink forwards the same
flag to openWorkspaceBrowserTab. Ports, links-in-Orca off, modifier
escapes, paired runtimes, WSL and local links are unchanged. The managed
SSH egress indicator now shows "Browsing from this device".
Fixes#41586
Co-authored-by: Neil <neil@stably.ai>
* feat(uninstall): add the uninstall cleanup contract shared by main and the settings UI
* feat(uninstall): remove Orca's OpenCode and Pi plugin files, also from the Windows uninstaller
Only files carrying Orca's marker are removed; OpenCode 1.x's TUI registration entry goes with them.
* feat(uninstall): main-process plan, steps and finish actions for Uninstall Orca
getPlan lists agent hooks, the orca command, orca serve units, ~/.orca/agent-hooks and SSH hosts
without changing anything; runStep removes one part and returns the updated plan.
* feat(cli): add orca uninstall, sharing the app's cleanup
* feat(uninstall): add the Uninstall Orca section to Settings → Advanced
* fix(uninstall): narrow plan agent ids with isTuiAgent instead of a cast
* fix(uninstall): show home-relative paths in the uninstall plan
* fix(uninstall): bound the SSH host sub-list with useBoundedHostRows
* fix(uninstall): async fs on the main thread and no type assertions in the cleanup
* fix(cli): bundle the uninstall cleanup modules the orca uninstall command loads
* fix(packaging): unpack the uninstall cleanup entries the packaged CLI loads
* fix(uninstall): call the orca command row the CLI on your PATH
* fix(uninstall): show hook scripts under the agents' hooks row
* fix(uninstall): remove hook scripts after the last agent retry and never show kept items as done
* fix(cli): give orca uninstall and agent hooks an app environment, and exit 1 on unfinished entries
Claude's remover resolves profile homes through it; without one the CLI reported Claude failed.
* fix(uninstall): drop Muse's Orca env-var allowlist and Claude's agent-view marker
Muse keeps names the user added. The agent-view marker only remembers opt-outs for a re-enable.
* fix(cli): bundle and unpack the node service environment orca uninstall loads
* fix(uninstall): settle the agent-view disable before deleting its marker, and report ok:false on unfinished --json runs
The docs layout mounts two SearchTriggers (sidebar and mobile nav), each
with its own window keydown listener, so Ctrl/Cmd+K opened two
SearchDialogs. Their body scroll locks restored out of order, leaving
body overflow stuck at 'hidden' after closing. Route the hotkey to the
first visible trigger so only one dialog mounts.
Fixes#42903
Co-authored-by: Claude <noreply@anthropic.com>
* fix(computer): click macOS windows that refuse focus with --restore-window
A raised window that never becomes the focused window (Archicad's CEF start window) failed every --restore-window click with window_not_focused, because the click fence required the target to be focused as well as topmost at the point. A real click reaches the topmost window whether it is focused or not, so when the target stays unfocused the click now goes ahead while the target is topmost at the point, and is refused before anything is sent when another window covers it. Afterwards the app the user had in front comes back if the raise or the click left the target app in front without the target window.
* fix(computer): restore the front app only after a click on a window that refused focus
* fix(computer): keep the target app in front when an unfocused-window click opened something
* fix(computer): count small popups and re-read the front app last before restoring it
* feat(computer): add opt-in flags for smaller computer-use screenshots
Every observe and action screenshot came back as a full-resolution PNG, so a Retina window cost about four times the pixels it needed. --screenshot-scale caps pixels per window point, --screenshot-max-edge caps the longer side, and --screenshot-format jpeg re-encodes it, on macOS, Windows and Linux. Defaults are unchanged.
* fix(computer): treat requested screenshot sizes as ceilings and skip repeat encodes
* feat(computer): list macOS apps without a Dock icon while they show a window
list-apps on macOS only listed regular apps, so menu bar and other accessory apps could not be found or targeted by name. Accessory apps are now listed while they own an on-screen window between the normal and status bar levels, which keeps the dozens of windowless system agents out, and each listed app says whether it is an accessory app.
* fix(computer): list only normal-level accessory windows and resolve hidden accessory apps
* fix(computer): prefer a same-named regular app when resolving, not in the list order
Align the Windows update harness docs and CLI help with the implemented
cold-restore/survival profiles, document the daemon-log reader, drop
links to unavailable plan/postmortem docs, and fix relocated script and
source paths in freeze-repro, process-host, and crash-survival docs.
Remove stale French Windows RC claims in favor of the stable latest asset.
Fixes#42765
Co-authored-by: Neil <4138956+nwparker@users.noreply.github.com>
* refactor: group process and platform modules by ownership
* refactor: preserve moved module workflow routing
* refactor: preserve native loader and embedded bundle origins
The appearance methods first shipped in v1.4.251 and editor.readTypography
in v1.4.257, so a plugin requiring the old floors installed on Orca that
lacks them.
* feat(plugins): check host API calls against released Orca at validation
orca plugin validate and pnpm validate:plugin now read the literal host
method names a plugin's worker, panel and editor code calls, and report
methods this Orca does not have, proposed methods, wrong-surface calls,
and methods newer than engines.orca (unless guarded by orca.host.has).
Deprecated methods warn with a stable 'deprecated host method <name>'
prefix. Adds the Host API minor to first-Orca-release table.
* fix(plugins): avoid host-call validation false positives
Guarded proposed and wrong-surface calls warn instead of failing, and an orca.api.minor comparison counts as a floor guard. Only host.call/has receivers count, comments are stripped, files are stat-capped and read through their real path inside the plugin, root-relative script sources resolve, and each file is read once.
* fix(plugins): keep has-guarded host calls as errors before orca.host.has existed
* fix(plugins): fail only certain host-call problems and bound the scan
Floor and wrong-surface findings are warnings, since guards and per-surface reachability are not visible to a text scan; unknown and proposed methods without a literal has guard stay errors. Read attempts, references per file and queued files are capped, has?.() counts as a guard, and HTML script and comment scanning is linear.
* fix(plugins): treat any orca.host.has call as feature detection for unknown methods
* build(cli): ship the host-call validation module with the packaged CLI
* feat(plugins): list any workspace's agents with agents.list({ workspaceId })
* feat(plugins): version agents.list workspaceId as host API 1.10
An added param is new surface a plugin must be able to require, so specs
gain paramsSince and api.minor counts it. Regenerates the declarative
typings the first commit missed.
* fix(plugins): report runtime failure codes for agents.list workspaceId
The param is 1.10, after the runtime failure codes, so a call naming a
workspace reports unavailable for a disconnected host; calls without it
keep action_failed.
---------
Co-authored-by: Neil <neil@stably.ai>
The Default profile's trash button was disabled whenever the profile had
no import record (`disabled={!profile.source}`). Clearing the jar resets
`source` to null, so the button locked itself after one use, and users
who signed in directly in Orca could never clear the default partition.
The button is now always enabled, labeled ("Clear default cookies"
tooltip and aria-label), and asks for destructive confirmation before
wiping the default partition. Strings are added to every locale.
Co-authored-by: Neil <neil@stably.ai>
* fix(computer-use): put the macOS pointer back after --restore-window clicks, scrolls and drags
HID gestures left the user's pointer at the target. Save it first, and after a
200 ms settle warp it back unless it no longer sits where the last posted event
left it, which means the user moved it. The HID idle counter can't tell: posting
to the HID tap resets it too.
* fix(computer-use): keep the pointer where the user moved it during a macOS HID gesture
* fix(computer-use): save the macOS pointer right before the first HID event
* Use theme colors for active workspace selections
* Check dedicated upstream selection token overrides
* fix(theme): keep active sidebar accents legible
* fix(sidebar): preserve selected title contrast in card templates
* test(sidebar): require both active tool layouts in contrast fixture
* fix(theme): keep built-in sidebar colors and mark active tools with the tab indicator token
- Active right-sidebar tools keep the foreground icon; their top/side line uses
--tab-active-indicator, so plugin theme accents show while built-in themes
paint exactly as before.
- Restore main's tinted sidebar resolver: 0% tint is the app background again.
Themes that want their own sidebar colors use the Default appearance.
- Drop the resolver tests (main removed this file as low value) and keep the
fixture presentational.
* fix(theme): gate the active tool line on the sidebar and fall back to the foreground
- Check --tab-active-indicator against --sidebar too, since the same line now
marks the active right sidebar tool.
- The tool line falls back to --foreground (never --tab-active-foreground), so
themes without an indicator paint exactly as before.
- Mark the active tool with aria-current like the overflow menu; it selects a
view rather than toggling one.
* fix(fixtures): follow the activity bar move in the theme selection fixture
* docs(plugins): note the tool line's own fallback for the tab indicator token
---------
Co-authored-by: Neil <neil@stably.ai>
* feat(chat): tidy native chat text typography
Default chat text is 13px in the system UI font on 20px lines, with
paragraphs and list items sharing one line height, bold set by weight in
the body color, and the CI and opened pull request card headers at body
size. Labels, icons and spacing keep their earlier sizes.
* docs(chat): update the chat type scale; trim default-only typography tests
Pi's launch catalog now opts into launch-time model/effort preferences, so
`orca agent launch --agent pi` and `orca orchestration worker-start --agent pi`
accept `--model <provider/id>` and `--effort <level>` instead of refusing.
Pi models without a provider/id shape are refused up front, before a
worktree or worker is created. A new host capability,
`agent.launch.pi-model.v1`, lets the CLI refuse a Pi model/effort on older
execution hosts that would otherwise start Pi on its default model.
Co-authored-by: Neil <neil@stably.ai>
macOS Local Network caches one executable UUID per bundle id, and the terminal host shares the app's bundle id. With a UUID of its own the cache flips between the two, which blocked some connections and prompted again after an update. Give the host exactly the main executable's UUID per CPU type, and check that in packaging and after notarization.
Orca terminals run under the signed helper, whose executable was stock Node,
sharing its LC_UUID with every install of that Node build. macOS Local Network
privacy maps a responsible process to an app by that UUID, so terminals could be
attributed to another program and blocked from the LAN while Orca showed allowed.
Rewrite the helper executable's UUID during assembly (same scheme as #41676),
and fail packaging and the release check if it drifts.
Fixes#21988
* fix(computer): press, set and scroll Windows native controls without activating the window
Measured on Windows CI: UI Automation's Invoke, Toggle, ValuePattern and
ScrollPattern focus a background WinForms control first, which activates its
window. Native controls now go through their own messages instead, each
owner-checked: BM_CLICK for buttons, check boxes and radio buttons, select-all
plus EM_REPLACESEL for set-value on edits, CB_SETCURSEL with CBN_SELCHANGE for
combo boxes (exact-text match, read back after the app's handler runs) and
LB_SETTOPINDEX for list box pages.
* fix(computer): refuse read-only Windows documents before typing keys, document the caret fallback
* fix(computer): keep Windows native routes to measured controls and refuse partial writes
BM_CLICK only for WinForms buttons, multi-column lists stay on ScrollPattern, a
list already at its end reports success, edits refuse text past their limit,
the combo's owner is checked right before the selection, a cleared selection
reads as a mismatch and a disabled control is element_not_enabled.
* fix(computer): hold Windows edit limits without a readback, require a complete combo search
* fix(computer): read a long Windows edit's length from the field for its limit check
* test(computer): share the Windows fixture action helpers
* feat(computer): add launch-app to start apps without taking the foreground
* fix(computer): leave running apps alone and keep the launch env clean
* fix(computer): recheck aliases, keep focused launches visible, refine launch hints
* chore(computer): document the launch result casts
* test(computer): check launch-app reports where the app ended up on Windows CI
* docs(computer): point app_not_found at launch-app
* test(computer): format the merged Windows background e2e
* fix(computer): match launch paths to the running file and word background launch as an attempt
* fix(computer): type into Windows text fields without raising the window
Adds type-text --element-index on Windows through EM_REPLACESEL for user32,
RichEdit and WinForms edits (owner-checked, read back with WM_GETTEXT), or a
ValuePattern write merged with the TextPattern selection. Keyboard verbs on a
background window now refuse with background_unavailable before sending
anything and point at type-text --element-index. Foreground typing uses one
SendInput KEYEVENTF_UNICODE batch instead of WM_CHAR posted to the top-level
window, and get-app-state shows multiline edit text again.
* fix(computer): refuse typing into Windows list items, keep the caret on a confirmed prefix