* fix(wsl): restoring or switching to a WSL host workspace never boots its stopped distro
A launch booted the last focused WSL host's distro from an early-wake list,
and the window's focus report (sent for a launch restore as well as a click)
connected the host with boot allowed. Both started a distro the user had
stopped, and the stopped card never appeared. Focus now re-checks and
connects only a running distro; a stopped one is published stopped, so the
panes show Start. Start and New Terminal still boot it. The early wake is
gone, and a launch deletes the list an older build left.
* fix(wsl-host): a stale stopped read never overwrites a newer connect
A focus re-check that read the running list while the distro was stopped
could finish after a user Start or New Terminal had connected, then publish
distro-stopped with terminals exited over the live host. Every ready publish
now bumps a per-host generation; a runtime call whose read a newer ready
overtook re-checks instead of parking.
* Change Plugins shortcut defaults by platform
* Test Plugins shortcut matching on all platforms
* Test current Plugins default in browser shortcut forwarding
* fix(github): start explicit Checks refreshes after the action
* fix(github): give explicit Checks refreshes fresh checks and comments
The same Refresh or Link click that now reads PR metadata after the
action also reads checks and comments after it: an explicit request no
longer joins or waits on a read begun before the click, in the renderer
or (for checks) the host coalescer. A superseded read's callers show the
owner's answer, so a late pre-click reply cannot repaint the panel, and
comments posted during either read are kept.
A lost IPC/RPC reply is reported only to the click that asked; polls stay
silent as before, and a later answer clears a failure older than itself.
The manual hook takes its verdict from its own lookup, the link flow's
card-read failure no longer skips checks, and the web shim forwards the
intent.
* fix(github): land the older Checks reply when a newer explicit read fails
When a click's checks or comments read fails while the read it replaced
succeeds, the click's read now lands that older reply through its owner
path instead of leaving the cache behind it. Post-write comments
refreshes (mutation events, bulk resolve) carry the explicit intent so
they cannot be answered by a read begun before the write.
* test(github): drop type assertions from the explicit-refresh tests
The RPC tests call the handlers with a real runtime service and spies,
and the panel test passes typed fixtures straight to the hooks.
* test(github): type the Checks panel fixtures for the renderer project
The renderer tests build their PR fixture locally instead of importing a
main-process harness, and the panel setter mocks take the hooks'
SetStateAction form.
* Advertise mid-turn queueing as queued-messages.v2
Released clients read the v1 name with an unfinished queue UI; they never
see v2 and keep sending immediately.
* Let each desktop send choose queue or steer while the agent works
The follow-up choice is now a Queue / Steer setting saved under
nativeChatFollowUpBehavior, Steer by default; the old
nativeChatQueueFollowUps switch, which every install saved as true
while queueing was dark, is retired on load. Every reader goes through
native-chat-follow-up-behavior.
While the agent works, Enter follows the setting and Cmd/Ctrl+Enter
sends the draft the other way; the alternate flips the setting before
the queue's own rules (a waiting command still queues, prompts no one
here can answer still send now) and never applies while Stopping.
Cmd/Ctrl+Shift+Enter steers the head card only and leaves the draft.
An idle agent's card reads Send, and the card menu no longer offers
"Turn off queueing".
* Hold Send on the phone to queue or steer a message mid-turn
While the agent works on a host that queues, holding Send opens a
Queue / Steer sheet; a choice other than the host's setting sends the
alternate, resolved against the chat as it is when it lands, by the
desktop's rule. Release and dismiss send nothing. The phone reads the
host's new follow-up setting (absent reads as Steer), and an idle
agent's card reads Send.
* Read the follow-up default from one place on desktop and phone
* Keep phone follow-up choices aligned with live host state
* Update stream and wire fixtures for live follow-up preferences
* Document minimal runtime test fixture assertions
* Keep mobile preference tests in the mobile compiler project
* Preserve queued input order through handover and recovery
* Consolidate input selection type imports
* Keep queue request capability types in the shared compiler graph
* Preserve reopen admission context and bound queue projection work
* feat(native-chat): queue follow-ups by default with a toggle
* fix(tests): preserve projection contracts in the node compiler
* fix(native-chat): retain receipt lookup after journal replacement
* test(mobile): assert shared preference renders on real changes
* Remove obsolete follow-up option translations
* Preserve input places across journal recovery without predecessor snapshots
* Keep recovered card placement tied to the exact handoff
* Preserve replay source types and correct verification fixtures
* Complete indexed queue selection and recovery ordering
* Preserve queued input order across recovery and source replay
* Fix legacy queue recovery fixture types
* Use a specific name for queue pause inputs
* Preserve fallback queue identity across journal recovery
* Place nested storage negative directive on its constrained call
* Constrain journal draft property type parameter
* Remove journal input order import cycle
* Preserve lazy journal counter reads within line limit
* test: preserve legacy conversion and display work contracts
* test: align journal refusal and restore accounting contracts
* Turn Stop into Send while the agent works and a draft has text
While the agent works, the desktop composer's Stop button becomes the
ordinary Send button once the draft holds text or images, and returns to
Stop when the draft is empty. It sends like Enter, so it follows the queue
setting; Esc still stops. Its tooltip names what Cmd/Ctrl+Enter does
instead (steer when queueing is on, queue when it is off), read from the
same resolver the send uses, so it is absent wherever the shortcut would
send no differently.
The Send/Stop decision moves into native-chat-composer-send-state so the
pane stays within its size limit.
* Tie alternate delivery hints to the composer submission
* Combine duplicate composer test imports
* Return snapshot results from composer option fixture
* fix(native-chat): show the account's model list while a new folder's own listing runs
A new Claude or Codex chat in a folder with no saved model list showed only its remembered model (or nothing) until that folder's model probe finished, then the full list appeared 1-2 s later. Every new worktree and every chat after a restart hit this, because these agents keep one list per folder and the account-level list reads already fall back to was never written.
The account's own listing (prewarm names no folder) now also saves that list, and a read whose folder isn't listed yet answers from it, including before its scope resolves. The stand-in names no default as the folder's; the folder's own listing still replaces it.
* fix(native-chat): preserve account catalog publication ownership
* fix(native-chat): retain scoped account inventory under binding pressure
* test: make passive catalog deadline coverage deterministic
* test: consolidate catalog fixture type imports
* test: repair catalog fixture types and integration placement
* fix: retain accepted model catalog authority during refresh
* Allow workers to continue their own finished helpers
* Own helpers follow takeovers and who holds the agent; refusals after closing a leftover shell say so
- A worker's own-helper check now walks back from the caller through follow-ups and through exact pane takeovers recorded in the terminal's ordered owner history, same Run at every hop, so the documented reopen-on-the-same-agent recovery keeps the worker's helpers while a stop in another Run does not.
- The helper's owner is the creator of the Dispatch that last took custody of its agent, so a coordinator attempt that never got an agent no longer takes the helper away; a real coordinator takeover still does. With no custody at all the follow-up is refused.
- The refusal names the Dispatch the sender addressed (and its latest work when that differs) and says what to do instead.
- Follow-ups check nesting depth before placement can close a leftover shell; if a later check refuses after that close was requested, the error keeps its code and cause but says the close was requested instead of claiming no effects.
* Cover takeover ancestry, custody ownership and post-release refusals in the helper follow-up CLI test
Recovery-flow takeover (live, closed, unreadable history), takeover plus fresh follow-up composition, a stop in another Run, failed coordinator attempts, a real coordinator takeover, depth before and after release, refusals after a leftover-shell close, held-mail follow-through from own and foreign senders, and the ancestry read bound now counting custody-history reads. Error data is asserted, not only text.
* A helper that never got an agent stays its requester's
When no Dispatch in a helper's lineage ever took custody of an agent, its owner is the creator of the first Dispatch in its follow-up chain (every link read, same Run, no cycles), checked through the same caller continuation as before. A worker can again continue its own helper whose start failed before an agent came up, including after coordinator attempts that also never got one; a real coordinator takeover still blocks it. The round-1 denial for this case is gone. The post-release refusal rewrite names the message convention it relies on.
Tests: terminal-create and native setup-gate failures, failed coordinator attempts before a continued worker's retry through both addresses, takeover then an unplaced attempt, coordinator/foreign/missing/cyclic/cross-Run origins, and held mail on a failed coordinator attempt. The CLI fixture moves to a shared test-support file and ownership cases to their own file, which keeps each under the line limits.
* A worker reopened on the user's own terminal keeps its helpers
The own-helper ancestry also follows an external pane's previous holder. Each check reads the pane's complete assignment history once, from dispatch_contexts through a new full-history index on pane leaf and host (created on every open, so existing databases get it too), reading the exact-host and unknown-host cohorts and joining each holder's own custody row. Custody rows are inserted at acquisition, so original-acquisition rowids order the holders; timestamps and acceptance order are never used. The immediate predecessor is fixed before any check: if any holder lacks its own orderable row (a direct dispatch to the same agent, a backfilled, transferred or unreadable row, an unknown host), no edge is derived. The predecessor must then be the same process, same host and settled, and the walk keeps same-Run-per-hop and its seen set. The derived order lives only for that check. External rows stay external and gain no cleanup.
Tests: live and closed recovery on the user's terminal with equal timestamps, composition with a follow-up in a new pane and a takeover, another Run's assignment accepted after but acquired before the recovery, a real direct dispatch in between, replaced process, other host, backfilled and unreadable rows, held mail, a restart with the index rebuilt on an existing database, and read/plan contracts for unrelated history, one long pane chain and two panes joined by a follow-up at N and 10N. Ownership and core test files consolidated.
* Find a worker's former custody through its process identity, once per check
The own-helper walk no longer scans every custody row's owner history for each ancestor. It reads the Dispatch's own row by owner first; for a former holder it reads the custody rows of that Dispatch's exact process and host through the identity index, keeps the one whose ordered owners name it, and takes the owner right before it. Each identity cohort, decoded owner history and pane order is read at most once per check and dropped when the check returns. The shared former-owner reader and target routing are unchanged.
Tests: the call-count contract is replaced by read contracts over the actual SQL: a four-recovery chain reads one identity range visiting one row whether 40 or 400 unrelated Dispatch and custody rows sit beside it, with indexed plans and no former-owner scan; a 3- and 30-step follow-up chain reads one identity range and decodes the same number of histories.
* A direct dispatch before a worker no longer cuts it off from its helpers
A direct dispatch claims the user's pane in the Dispatch row it inserts, with no worker row and no custody row, so its insertion order bounds where it can sit. The pane history now reads each holder's Dispatch insertion order and whether it has a worker row, treats only that claim shape as a direct claim, and keeps the latest claim's insertion as a floor: an earlier holder is reachable only when it was inserted after every direct claim on the pane. Insertion order is never compared with custody order. Every other holder whose place is unproven still blocks the whole pane, and the floor is computed once per pane per check.
Tests: live and closed recovery after a direct dispatch before the worker (also from another Run), the claim between a worker and its recovery blocking only that edge while the next recovery keeps the reopened worker's own helper, a supervised Dispatch without its own custody row still blocking, and the history read contracts extended with old claims and the worker-row probe.
* Tighten the helper follow-up CLI tests
Drop the coordinator row from the refuse-after-release cases, which takes the same follow-up path as the worker's, and give the three-caller zero-effects case the refusal each caller gets.
* Count the former-owner scan's visited rows in the caller read trace
* Continue a worker's helpers only through recorded custody, finding each former holder once per check
A worker re-placed on a terminal it never held in saved custody no longer
inherits helpers from an earlier start there: the pane-history derivation
and its index are gone. Former custody is found by exact process through
one membership map per identity, so the walk is linear in ancestors and
rows.
* Pin the narrowed custody walk: one refusal for the user's terminal, linear identity and probe contracts
The external recovery tests and their pane-history contracts go. One case
pins that a worker re-placed on the user's own terminal is refused its
earlier helper with no effects while the coordinator still continues it.
The follow-up chain contract now grows both ancestors and same-process
rows and bounds field reads and Dispatch probes; the never-placed matrix
bounds the walk to the first request.
* Use a fixed observation time in the reopened-helper test
The provider session's observation time is never read on this path, so
the wall clock added nothing but a flaky-test gate failure.
* Drive the helper follow-up CLI tests through the runtime's own RPC server
The CLI now reaches the test runtime as it reaches the app: through the
metadata the real RPC server publishes, its socket, dispatcher and error
mapping, instead of module mocks of the runtime client and printer.
Recorded SQL rows are parsed into a named row type before their reads
are counted.
* Type the helper follow-up test traces without assertions
The SQL trace spies on each statement method through its own typed
signature and reads plan rows as the rows they are; the Dispatch probe
trace spies on each read separately; the never-placed matrix picks its
requester and corruption by origin.
* Type the CLI output spy as a console.log mock instance
An instantiation expression over spyOn's overloads named its type, and
this vitest's typings reject it; MockInstance names the spy directly.
* fix(runtime-host): Explorer and Source Control load again once a runtime host answers
After a relaunch with a WSL-host workspace active, both panels read before the host connected:
Explorer kept "the Orca server … isn't answering" until Retry, and Source Control kept a clean
status until a reload. The runtime status stays verified across the relaunch, so the existing
contact-regained signal never fired when the WSL host's connection came up.
- subscribeRuntimeHostContactRegained also fires when the environment's WSL host turns ready.
- Explorer reloads a failed root on that signal (gated: never boots a stopped distro), as it
already does for SSH providers.
- Git status polling reads again on that signal.
Co-Authored-By: Claude <noreply@anthropic.com>
* fix(runtime-host): keep the Explorer's contact retry current from an effect, not render
React Doctor flags a ref mutated during render.
Co-Authored-By: Claude <noreply@anthropic.com>
---------
Co-authored-by: Claude <noreply@anthropic.com>
At every startup, managed WSL CLI registration reconciliation ran a guest
command in every running distro it hadn't inspected recently, including the
user's own unrelated distros. That's EDR-noisy and touches environments Orca
never set up. It now repairs distros carrying Orca's own registration record,
and inspects only distros Orca deployed a WSL host into.
* fix(native-chat): an open chat moves to the account you switch to before its next message
A running chat's agent read its account only when it started, and nothing compared it with the
account a start would use now, so open chats kept answering on the old account after a switch.
The agent a chat runs now records the account its launch used, and the host's replace-before-the-
next-send check replaces an idle one whose account is no longer what a start would use. A chat
mid-reply finishes on the old account first. Claude chats follow; agents whose chats keep the
account they were created on are never compared.
A chat's model-list reads and saves now use the account it runs on, so a moved chat no longer
writes its new account's list under its first account (STA-11281).
Tracked in STA-11211.
* fix(native-chat): declare the launch-account read for the runtime layer that wires the host
* fix(claude): find custom chat history before managed-account resume
* test(claude): assign the complete custom account home
* Preserve unknown account model facts and legacy option replay
* Clarify terminal account-switch feedback in translated locales
* Keep option mutation plans checked against their contract
* Cover unknown model choices across chat consumers
* Keep consumer fixtures aligned with canonical types
* Match the mobile picker label in its consumer test
* fix: clarify terminal scope in translated Claude account settings
* Update integration tests for current session and remote client contracts
* Keep native worker replies on their receiving account
* Preserve receiving accounts across cold starts and nested reports
* Preserve the delivery receiver when reading chat commands
* Clarify native reply matching and consolidate imports
* Resolve catalog scope without re-entering conversation queues
Give owned option mutations and delivery settlement a resolved catalog input while external reads acquire scope once. Preserve account routing, catalog lifetime and current response obligations.
* Align catalog and mobile test fixtures with current contracts
Explain the existing timeout budgets and provide the idle turn identity and truthful model-only picker label in the mobile fixture.
* Align receiving-account readers and fixtures with typed contracts
* Repair account-switch fixtures and measure receiving work
* Use the checked account-home path in catalog tests
* Restore executed-option recorder context
* Control receiving catalog deadline test clock
* Align unknown-model consumer fixtures with send capture
* Consolidate session host type imports
* Align cross-version catalog fixtures with host read contracts
* test(native-chat): bind Runs through the current start authority in receiving fixtures
Main now resolves a worker start lazily through bindRun with objective and task references, and creating a Run no longer unbinds a coordinator's earlier Runs; run-use does. The receiving fixtures follow the same production owners so every original scenario, input and bound is exercised unchanged. The receiving runtime subclass moves verbatim into its own support module.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* fix(native-chat): follow the selected account before its folder exists
A live Claude chat compared its account against the selected one only after that account's folder passed an availability check, so an account still being set up (or whose setup failed) left the chat silently answering on the previous account, and a resting chat refused its start before preparation could run. The retirement comparison and the start pre-read now ask the router for the selected route as identity, through the existing resolver purposes; catalog, create and probe reads keep checking availability. Preparation, typed launch failure and parking are unchanged.
Session History details show the account a chat was last launched under when the host recorded one, else its founding home.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* test(ai-vault): build the stale acquisition receipt without a type assertion
The History account case now reads the fixture receipt through the typed acquisition reader instead of spreading the record field through a cast; the three assertions and their inputs are unchanged.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* test(native-chat): narrow the rig acquisition link before relinking it
The account-setup cases spread an optional link, which typed its id as possibly undefined; the rig always links a handle, so a guard that cannot fire narrows it. No assertion or input changes.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* test(native-chat): follow main's chat admission in fixtures and bound the History account projection
Chat admission no longer reads an experimental host setting, so the continuation-context test drops the spy main dropped in its own fixtures. The two History consumers that install a minimal chat host give their fake store the record accessor and host id the real store has, since the projection now reads the acquisition receipt. An operation-count contract holds the production History projection to one roster read and one record lookup per owned row at 10 and 100 rows.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* test(native-chat): give the declared-effort catalog fake its capture port
The declared-effort fixture builds a catalog service without the capture member the options reader asks every catalog for, which failed its desktop, catalog and phone consumers; it now supplies the inert test operation like the other fakes. The History projection contract also drops an unused map parameter.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* Consume main's outcome change feed in the receiving-account index
Main's keyed journal records deliver each change after an epoch's frozen prefix as an
outcome sequence naming touched keys instead of typed rows. The receiving-account index
now re-reads those keys at their current values: queue cards by id, a deleted submission
retires its exact notice, and a deleted item drives the existing recovery rebuild, with
Stop marks still excluded. The in-process read row exposes the already-persisted
queue.cards keys and per-key deletion facts; itemIds and submissionIds keep listing every
touched key. The mobile unknown-consumer test mocks MobileSwitch as main's picker test does.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
* 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
* fix(test): keep unit-test tooling inside the repo root in nested checkouts
Vitest's oxc tsconfig auto-discovery walks past the repo for files no
in-repo tsconfig owns, so a worktree nested in another checkout loaded
the enclosing checkout's tsconfig. Pin the transform tsconfig to an
explicit solution file listing the same projects auto-discovery finds.
The local module cache policy hash failed on esbuild warnings from an
ancestor package.json; only warnings located inside the root now fail.
* fix(test): guard the pinned transform tsconfig against project drift
Drop docs/site (no unit test transforms it) so its tsconfig cannot break
every transform, and fail when a project tsconfig is added or removed
without updating the pinned solution.
* fix(windows): stop each WSL host's server on uninstall so its distro can stop
Uninstall released the holders but left orcad and any live terminals
running, which kept the distro (and its VM) up indefinitely. The existing
--orca-uninstall-release-wsl-holders preflight now also runs Remove host's
teardown for every recorded host whose distro is confirmed running, driven
through orcad's own CLI inside the distro: close terminals, count, then the
instance-checked decommission that retires an idle daemon. Stopped distros
are skipped, each stop is bounded at 15 s, and nothing changes the exit
code. NSIS now also launches the preflight when WSL host records exist.
Grok removal also cleans the rolling .bak of Orca's hook file.
* fix(windows): list up to 1000 terminals when uninstall stops a WSL host
* fix(windows): leave WSL host servers running while another Orca install remains
The HKCU/HKLM twin shares this userData, its WSL host records and each
distro's server. NSIS now adds --orca-uninstall-stop-wsl-servers only when
ORCA_OTHER_INSTALL_STATE is none, as the agent-hooks removal already does;
the preflight stops servers only with that flag. Holder release is unchanged.
* fix(grok): clean the hook backup without sync fs on the quit path
* Advertise mid-turn queueing as queued-messages.v2
Released clients read the v1 name with an unfinished queue UI; they never
see v2 and keep sending immediately.
(cherry picked from commit f39382e090)
* Let each desktop send choose queue or steer while the agent works
The follow-up choice is now a Queue / Steer setting saved under
nativeChatFollowUpBehavior, Steer by default; the old
nativeChatQueueFollowUps switch, which every install saved as true
while queueing was dark, is retired on load. Every reader goes through
native-chat-follow-up-behavior.
While the agent works, Enter follows the setting and Cmd/Ctrl+Enter
sends the draft the other way; the alternate flips the setting before
the queue's own rules (a waiting command still queues, prompts no one
here can answer still send now) and never applies while Stopping.
Cmd/Ctrl+Shift+Enter steers the head card only and leaves the draft.
An idle agent's card reads Send, and the card menu no longer offers
"Turn off queueing".
(cherry picked from commit 55b48694e7)
* Hold Send on the phone to queue or steer a message mid-turn
While the agent works on a host that queues, holding Send opens a
Queue / Steer sheet; a choice other than the host's setting sends the
alternate, resolved against the chat as it is when it lands, by the
desktop's rule. Release and dismiss send nothing. The phone reads the
host's new follow-up setting (absent reads as Steer), and an idle
agent's card reads Send.
(cherry picked from commit db87cf51ea)
* Read the follow-up default from one place on desktop and phone
(cherry picked from commit 8e1438bfb6)
* Keep phone follow-up choices aligned with live host state
(cherry picked from commit dc9215be3d)
* Update stream and wire fixtures for live follow-up preferences
(cherry picked from commit e4d038cf0b)
* Document minimal runtime test fixture assertions
(cherry picked from commit 254f751ef3)
* Keep mobile preference tests in the mobile compiler project
(cherry picked from commit ae2aa8910e)
* feat(native-chat): queue follow-ups by default with a toggle
(cherry picked from commit 70969d6a43)
* test(mobile): assert shared preference renders on real changes
(cherry picked from commit 3f50de9b2a)
* Remove obsolete follow-up option translations
(cherry picked from commit b87b360cf3)
* Describe Cmd/Ctrl+Enter relative to the Queue follow-ups switch
The Settings description said Cmd/Ctrl+Enter sends into the running
turn, which is wrong while the switch is off. Describe it as doing the
opposite for one message, in every language.
* Show what a mid-turn phone Send does, and offer the other way only when it differs
While the agent works, the phone's Send button now shows Queue or Steer.
Holding it lists that action first with a check and the other second,
each with a one-line description, and appears only when both choices
would actually lead to different sends. A waiting command or prompts
nobody here can answer make a hold behave like a tap.
* Steer the head card once while its shortcut is held
Holding Cmd/Ctrl+Shift+Enter auto-repeats the key, which steered each
card that became the head in turn. Ignore the repeats.
* Show beside Stop what Enter does while the agent works
While a turn runs and the draft has something to send, a send control
now sits beside Stop. Its icon and label say whether Enter queues the
message or steers it into the running turn, and its tooltip names Enter
and, when it would send differently, Cmd/Ctrl+Enter. Clicking it sends
as Enter does. Stop keeps its place and nothing changes while Stopping,
with an empty draft, or before the host says it queues.
The phone and desktop now read what a send does from one shared helper
over the send's own resolver.
* Test the send keys and Queue follow-ups search against real wiring
One desktop test drives Enter and Cmd+Enter through the real composer,
transport and session to the outgoing send and checks its delivery with
queueing on and off. Settings search is checked against the capability
list this build's host advertises.
* Move the composer's send-hold check into its own helper
The pane had grown past the file length limit after the main merge.
* Disable the mid-turn Queue/Steer button whenever Send would be disabled
While an image is still loading, another device holds the input, or a send is blocked for a stated reason, the button beside Stop is now disabled and says why, the same way the idle Send button does. Before, it stayed clickable and a click did nothing.
* Hide the mid-turn Queue/Steer button in goal mode
In goal mode Enter sets the goal, so a button promising to queue or steer the message was wrong. It is now hidden there, as it already is while editing a queued message.
* Fix the Russian queue hint to say the message runs after this turn
It read as queueing until the end of this turn.
* Stub window.api without a type assertion in the Queue follow-ups settings search test
* Pass sendHeld to the composer field in tests and drop an unknown setting from the German Queue test
* Let Cmd-click (Ctrl-click elsewhere) on the mid-turn Queue/Steer button send the other way, like Cmd/Ctrl+Enter
The button shows the other action while the modifier is held, and its tooltip names the click. Only when the other way would send differently; otherwise a modified click is a plain send.
* Merge the duplicate composer-types import and give the composer's round buttons a Button size instead of restyling them
The focused code-quality check rejects importing one module twice, and the design-system check rejects rounded-full on a <Button>, which the new Queue/Steer button copied from Send. Both composer buttons now use a round icon size on the Button primitive and render as before.
* Share one window key listener across every chat's Queue/Steer button, and count Cmd/Ctrl as held only from its own key press
Each mounted chat with a mid-turn draft used to add its own window key listeners, so every keystroke did work per chat, hidden tabs included. One shared listener set now serves them all and wakes a button only when the held state really changes.
Other keys can now only clear the held state, so a dictation paste that leaves the Cmd flag on later key events no longer flips the button with Cmd up. Also tests the Ctrl-click on Windows and Linux.
* Remove the desktop Queue/Steer button shown beside Stop while the agent works
While the agent works, the desktop composer goes back to its usual
controls: Stop, with Enter and the send shortcuts doing what they did.
Enter still follows the queue setting, Cmd/Ctrl+Enter still sends one
message the other way, and Cmd/Ctrl+Shift+Enter still steers the first
queued card.
This also removes what only that button used: its Cmd/Ctrl-click
alternate, the shared Cmd/Ctrl key listener, the extra round Button
size, the send-preview value the desktop session passed to the
composer, and the button's text in every language. The phone is
unchanged.
* Put the composer's send-hold checks back inline in the pane
The separate send-hold helper only existed because the removed mid-turn
Queue/Steer button pushed the pane over the file-length limit. Without the
button the pane fits again, so it goes back to main's inline code.
* Share chat option writes across desktop and phone
* Restore main's failure notice scope for chat option picks
Held launch refusals toast again while the transport is still closed, desktop
notices follow only the chat's presentation scope so a fence or status change
on the same chat still reports, and the phone banner no longer depends on the
read record.
Adds the README link (#36527) and 'Show all N plugins' strings, plus every
other plugin UI string still falling back to English, to de, es, fr, ja,
ko, pt, ru, tr, zh and zh-Hant.
Co-authored-by: Claude <noreply@anthropic.com>
Drop the hand-written per-language samples. Try it now opens an empty
untitled<first extension> through the existing untitled-file flow, so the
grammar highlights what the user types. Custom editors with newFiles keep
their template-seeded new file.