Missing, empty, or locked ffmpeg.dll beside Orca.exe (as an interrupted
update leaves it) makes every renderer die at child init with 0x80000003
and the window crash-loops. Gate the packaged Windows desktop launch on
it after the single-instance preflight and show the standard startup
failure dialog instead.
Rebased onto main keeping the WSL holder and agent-hooks uninstall
preflights ahead of the gate. Message no longer claims the installer
relaunches Orca, and tests cover the gate's skip paths.
Co-authored-by: m4air <m4air@Mac.localdomain>
* fix(window): ride out Windows renderer launch refusals instead of prompting after 1s
Windows renderer launch-failed exit 18 is Chromium SBOX_ERROR_CREATE_PROCESS:
CreateProcessAsUser for the sandboxed renderer was refused. Field reports show
the refusal clears within seconds to minutes and the same webContents reloads
fine afterwards, but Windows was kept on the 750ms crash breaker, so three
reloads burned in ~1s and a blank window waited on a Try Again prompt.
Use the same ~2 minute launch-failure backoff on Windows as on POSIX.
* test(window): pin bounded prompt for persistent Windows exit-18 refusal
---------
Co-authored-by: m4air <m4air@Mac.localdomain>
Co-authored-by: Neil <neil@stably.ai>
A phone send writes text raw and presses Enter after the ingest delay only.
Windows Codex reads the text one key event at a time and keeps an Enter that
lands mid-burst as a newline, so the message stays in the desktop composer.
Add the key-event burst (3 ms/char) to the wait, capped at 20 s total so the
send still answers inside the phone's 30 s terminal.send timeout.
Co-authored-by: m4air <m4air@Mac.localdomain>
The image viewer chunk is lazy. Its first load suspended to the editor panel's
boundary, which hid the whole virtualized combined diff. Hidden, the list
dropped the overscan image row, stopped suspending and re-showed; shown, it
rendered the row again and re-suspended. Each flip re-attached ref callbacks
(the toolbar's 'Show file tree' tooltip trigger first), so the synchronous
commits ran past React's nested-update limit (or tore down Monaco mid-mount).
A row-local Suspense keeps the chunk load inside the image section.
Co-authored-by: m4air <m4air@Mac.localdomain>
Chromium loads the bundled 'Orca Nerd Font Symbols' face lazily, so the
first PUA glyphs rasterized into xterm's WebGL atlas fell back to tofu
boxes and stayed cached after the face landed. On first WebGL attach,
watch document.fonts for that face's loadingdone and reset/refresh all
terminal atlases once, also clearing hidden managers' atlases (without
painting) since light reveal only re-presents retained canvases.
Fixes#37627
Co-authored-by: Claude <noreply@anthropic.com>
On Windows, relaunching Orca while the previous process was still quitting
delivered a second-instance activation to the exiting process, which opened a
new main window bound to services already being torn down; the window never
appeared and the exit hung.
focusExistingWindow's canOpenWindow now also returns false once the quit
teardown start gate has fired, and delayed reopen retries re-check
canOpenWindow before constructing a window so a retry scheduled before quit
can't slip through afterwards.
Fixes#37625
Co-authored-by: Claude <noreply@anthropic.com>
* Make new-tab agent setup feel like a native submenu
* Separate the agent submenu chevron into its own segment
* Restrict agent submenu hover to the chevron segment
* Highlight agent menu sections independently and focus setup search
* Restore agent row highlighting and empty-search back navigation
* Keep the agent chevron filled for hover and keyboard selection
* Match agent launch buttons and add the alternate launch shortcut
* Preserve submenu pointer grace and update launch button selectors
Retain the original OMP prompt across explicit typed busy refusals, keep queued follow-ups ordered, and cancel recovery on Stop or close.
Fixes#34807
Co-authored-by: Manan Chataut <mananchataut@gmail.com>
* feat(sidebar): draw workspace cards from a template (card plugins phase 1)
Today's card becomes the built-in card template: a JSON template of
layout primitives and Orca's own card parts, compiled once and evaluated
per card over a documented workspace fact model. Markup parity with the
original composition is tested for 34 states in all three card styles.
* fix(sidebar): card template typecheck
* fix(sidebar): bound card template def expansion and tighten expressions
- Cap expanded elements (maxExpandedNodes 2000), expanded depth (maxDepth)
and def nesting (maxDefDepth 8) at compile time, so reused defs cannot
multiply into millions of elements.
- A def reference now keeps the frame's root attributes, rejects props and
children, and is looked up with hasOwn.
- Chained ternaries count toward the expression depth cap; len(x,) is rejected.
- Parts are documented as hook-free.
- Drop the unread CompiledCardTemplate.roots; schema now reads
WORKSPACE_CARD_FACTS_VERSION. maxBytes stays for phase 2.
* chore(sidebar): baseline the card template's moved focus read and allowlist non-UI strings
* Agent message cards keep their sender's agent icon when the agent can't be found
A card names its sender by a snapshot written with the message, but drew the
icon only from a live lookup, so a sender the lookup missed (a worker on
another host, a terminal after restart, a closed agent) showed "?". Every
writer (worker start, mail, task, federated start) now saves the sender's
agent kind beside its name, and the card draws it when no live row names
the agent. Live rows stay the source of icon and status whenever they match.
* Preserve known worker agents on federated cards and mail
* Resolve agent message senders through shared host identity
* Retain acquired worker launch identity for later sender snapshots
* Prune repeated worker sender contract checks
* Combine worker command contract projection imports
* Keep sender identity bounded and scoped per worktree
- A worktree removal frame drops only its own scope; a host stays
publishing once any frame carried the field.
- Identity history rebuilds follow writes to the facts it reads
(connection-local triggers), not heartbeats, read marks or receipts;
new mail is read incrementally.
- One principal per paired peer replaces every federated route ever made.
- Unchanged worktrees keep their scope object; a refresh republishes only
worktrees whose scope changed. Chat records key on the store's state
generation instead of serialising every record.
- The publication rides client frames only, and phone frames drop it.
- A failed history read keeps the last good publication and is not
marked indexed; malformed rows are skipped; opening the database for
display never throws.
- A located chat keeps its tab's agent icon for cards saved without one.
* Save each agent card's sender identity and open the pane it names
Orca now records who sent each agent message and created each task when it accepts them, and the chat card resolves that saved identity against what each host says runs now. The avatar dot, label and click all read that one answer: a located terminal opens through the sidebar's own activation path, a closed chat reopens through its lineage, and a sender no host can prove shows its saved icon and says it is no longer available instead of opening whichever agent now holds the old pane.
Publication now has the host's pairing key from the RPC server, so it no longer fails on every build.
* Resolve agent card senders by the terminal handle every card saves
A card's sender is now the terminal its saved handle names, the worker lineage its Dispatch continued into, or its chat session. That survives a normal restart, works with hooks off, from a plain shell and for replies, and needs no newly saved sender data, so the hook-conversation records, their table and the saved identity key are gone.
The avatar, link and click read one answer. A terminal that now runs a different kind of agent than the card saved, or a sender two places claim, shows the saved icon as a plain name. A terminal that exited or was respawned keeps the host's own lookup on click without a status dot, behind one switch.
Chat senders rebuild only when a chat appears, moves, clears or closes, and each live pane's worker reads go through the existing partial indexes.
* Send sender identity once per revision and judge every host by one rule
The host's sender publication now carries an in-memory epoch and content revision that move only when what clients read changes. A window's graph sync sends the revision it applied and gets "unchanged" instead of the rows; each session-tab stream sends a worktree's scope once per revision. The window keeps the whole-host publication as its baseline and a newer worktree scope over it, by revision, so a delayed reply never undoes a newer scope and repeated deliveries cost nothing.
An older paired host's cards now go through the same resolution as everyone else's: a terminal that runs a known different agent shows the saved icon as a plain name, and what the host's lookup returns is judged by the same row. Pi and OMP, and Claude and its teams wrapper, count as one agent. Failure text names the agent and says what to do.
WSL chats are published, closed chat history no longer counts as open before the tab table exists, and paired principals are read again only after a pairing changes.
* CI: keep the sender delivery contract test out of the web project and fix its types
The cross-process delivery test moves to tests/e2e, where tests that span main and renderer live, so the web typecheck no longer pulls main files in. It now drives the stream encoder main uses. The worker lineage walk takes a reader type without a this binding, the stream delta composes with the proof delta's own frame type, alias buckets accept terminal and chat tab arrays, and the publication test builds fully typed fixtures.
* CI: share the dispatch-address link rule and align the merged view test with saved-kind icons
The base's worker command contract test reads the shared rule that a
dispatch: address is never a link; the card's link check now calls that
shared rule instead of repeating it. The base's sender view test expected a
different agent's live row to replace the saved icon; this branch shows the
saved kind without that row's status, so the test asserts that.
* Use the sender snapshot resolver in main's new receiving-account tests
* Read a saved "unknown" agent kind as no kind for the card's icon and its replaced check
A hooks-off agent whose last status came from a terminal report without an app id saves the kind
"unknown". That kind proved nothing, yet it vetoed the live agent in its own terminal: the card
showed "?" with no dot as a plain name, and a raced click said another agent was running there.
One shared read now treats it as no saved kind for the veto and the icon, on every path.
* Apply a frame's sender scopes when the window receives it, ordered by each scope's own revision
A stream counts a sender scope as sent once a frame carries it, but the window applied it only
inside the tab apply, behind the tab version, resume census, receipt recovery and frames-draw
checks. A frame those checks dropped could hold the only copy, so a paired host's cards stayed
on stale rows (no dot while the sidebar showed the agent) until that worktree's senders changed
again. Each receipt path now folds the frame's sender scopes in right after its connection,
pairing and runtime checks; the tab apply keeps only a worktree's removal.
A scope now also yields to that scope's own newer delivery, not only to a newer whole-host
baseline, so a delayed list reply can't put back older rows. Every publishing host stamps a
revision, so the content-comparison path for unrevisioned publications is gone.
* Read chat senders from open chats and their /clear predecessors, not every saved chat
Each chat tab opened or closed, chat created or moved, or /clear committed rebuilt the chat
senders by listing every saved chat (42 ms at 10,000 on the main thread) only to keep the open
ones. The record store now keeps an in-memory reverse of the saved /clear pointer, built at
load and updated for the rows each commit writes; nothing new is saved. The sender read starts
from the open chats and follows that index to their predecessors, so its work no longer grows
with closed history.
* Walk live terminals once per session-tab inventory or broadcast, not once per worktree
A one-shot inventory or a broadcast built every worktree's frame through its own sender
refresh, and each refresh walks every live terminal: 20,000 visits for 1,000 terminals over 20
worktrees. Both passes now build their frames from one refresh. The publisher counts its leaf
and terminal visits, and a test drives the real inventory and broadcast methods at 100 and
1,000 terminals.
* Re-read a tab bucket's sender aliases only when a host it read changes
The window's sender aliases were recomputed for every open tab whenever any workspace-owner input
changed, such as switching workspaces or writing a setting, though a bucket reads those inputs
only through one host per worktree. Each bucket now keeps the host values it read and, when
owner inputs move, checks just those before reusing its aliases. The delivery contract test
counts alias work through workspace switches, settings writes and a title-only change.
* CI: restore the single-frame builder declaration and compare sender content without its revision
R4 swapped the inventory's abstract single-frame declaration for the batch one, but the
headless browser-tab emit and the runtime-owned terminal create still build one worktree's
frame through it; both keep the per-frame sender scope. The publisher's content comparison now
takes publications without their revision stamp, which R4 made required.
* CI: give the sender no-op test's heartbeat a fixed timestamp instead of the wall clock
The heartbeat only has to be a write that changes no sender identity, so a fixed time keeps the
assertion and satisfies the flaky-test gate.
* CI: assert one terminal walk per orchestration RPC and no identity reads in the sender refresh test
R4 added leaf and terminal visit counts to the publisher's work counters, and each orchestration
RPC's refresh walks the live terminals once, so the whole-counter comparison failed. The test now
compares history, chat and lineage reads, unchanged, and asserts exactly one walk per RPC.
* CI: reach the sender pass methods through a typed view of their prototypes
The test read the runtime's protected inventory and broadcast methods with Reflect.get and an
object-typed owner. It now names the three methods it drives in narrow types over their real
prototypes and calls them on the same stand-in; the assertions are unchanged.
* CI: list every sender target kind in the link switch and merge the duplicate sender-type import
The link check's switch now names the ambiguous and replaced kinds, which return false as the
default did; the publisher imports its sender types from one statement.
* Skip a paired host's floating-terminal sender scope at receipt, as the tab apply does
Applying sender data on receipt took a paired host's floating-terminal scope that the window
never mirrors, so its sender drew as a link whose click activated a pane this window lacks and
did nothing. The receipt now uses the tab apply's own floating rule for paired hosts: that sender
opens by asking its host, as before. This machine's own floating terminal still publishes.
* Read /clear predecessors through the record store's existing successor index
The sender's chat read reached each open chat's /clear predecessors through an in-memory reverse
index the record store built at load and kept per commit. The store already has an indexed query
for that link, which its lineage read uses; the sender now shares that query and checks each
candidate on its conversation, so branching, unreadable and cyclic predecessors resolve as
before, and the second index and its commit bookkeeping are gone.
* Keep live workers' sender history between builds and re-read only what a write reaches
Any write to a Dispatch, worker terminal or remote attachment re-read the history of every live
terminal (three queries and the lineage reads per pane) on the main process: about 20 ms at 100
live workers and 150 ms at 1,000, for a write none of them read. The connection's triggers now
also record the panes and Dispatch ids a write's old and new rows name. The history keeps each
live pane's reads and each Dispatch's verdict with every key it read, lookups that found nothing
included, so a write re-reads only the panes and lineages it reaches. Federated Dispatches move
their own counter, so worker writes no longer re-read paired principals. A commit from another
connection, which no trigger sees, still rebuilds everything.
* CI: build each sender trigger from a typed event list so its SQL parts are plain strings
* CI: give startup runtime fakes the sender peer-key setter and drop new test type assertions for typed fixtures
* Ask the host to reveal a located sender this window holds no tab for, as the lookup did before
* Keep no worker history read inside an open transaction, and forget workers and keys no live pane reaches
* Test that sender names render only when what they show changes
* CI: pass the sender target's dispatch id explicitly and write a real sidebar body in the delivery test
* Read terminals' existing handles for sender rows instead of issuing them
The sender publication walked every live terminal through the runtime's handle-issuing functions,
so each display build could mint, adopt or rebind terminal handles. During a renderer reload or a
split close that changed which handle a terminal held and what retirement frames published. Sender
rows now read only the handles terminals already hold; a terminal with no issued handle has no row,
and no card can name it.
* Open a located sender's own pane through its host when this window has no tab for it
When a card's sender was found in a pane this window had not loaded yet, the click asked the host
about the card's saved terminal instead. For a worker reopened by a follow-up, that opened its first
terminal, or said the pane was gone, while the card showed the reopened worker running. The click
now opens that same pane: by the handle its status row holds on that host, else by asking the host
for that pane in the host's own coordinates. It checks the card again after the host answers, and a
closed pane says the agent is no longer running. The saved-address lookup stays only for senders no
host has located.
* Read a terminal's start-time handle for its sender row while no window graph exists
When the window graph went away, the host cleared its handle records but kept each terminal's
start-time handle, which its agent's mail cards save as the sender. The read-only handle lookup
required a record, so the running terminal lost its sender row and its cards showed no dot until a
window came back. It now returns the handle issuing would reuse, record or not, and still changes
nothing.
* CI: type the open helper's target as any runtime target so the paired-host case typechecks
* Lease the sidebar rows a sender name's link check reads, as its avatar does
A sender name drawn without an avatar (queued mail, a card's later senders) checked for a different
agent through a source nothing leased, so every store write rebuilt that worktree's sidebar rows.
The name's link now holds the same lease the avatar does, and a card with no saved agent kind
skips the row read entirely.
* Index a build's terminal handle records once instead of scanning them per terminal
The read-only handle lookup fell back to a scan of every handle record for each leafless terminal
holding no handle, on every sender build. A build now gets one reader that indexes the records on
its first miss and answers each terminal from that index, with the same handles issuing reuses.
* Lease a replaced card's sidebar rows from where its sender runs before the kind check
A card whose terminal now runs a different agent resolved no location, so it leased no row
source and rebuilt its worktree's rows on every store write. Both the avatar and the link now
lease from the candidate location the kind check reads; their answers are unchanged.
* Show a paired host's worker status dot on its card when this window mirrors the whole tab
A paired host names a pane <tab>:<leaf>; this window mirrors that tab whole as web-terminal-<tab>
with the leaf ids kept, and its status rows use that key. The alias projection mapped only
per-pane mirrors, so the card located the host's key and found no row to draw a dot from. The
terminal bucket now also maps a whole-tab mirror's host tab, and a host pane takes this window's
name from either form; two names for one pane still locate neither.
* Publish a chat sender change even when the terminal read in the same refresh fails
The chat rows and their key were stored before the terminal read; when that read threw, nothing
was published, and the next build saw both keys as handled, so the chat change waited for an
unrelated identity change. The refresh now publishes whatever changed beside the last good
terminal rows, and the read's error still reaches the build's warning.
* Bound sender projection work to current consumers and lineage facts
* Update runtime call assertions for sender demand options
* Preserve mobile sender navigation availability
Terminal link detection treated the closing `]` of a bracketed IPv6 host
(e.g. http://[::1]:5173) as trailing punctuation and dropped it, producing
unopenable links. Match an optional bracketed IPv6 authority after the
scheme, and never trim trailing punctuation back past that authority.
Avoids regex lookbehind so the mobile terminal WebView can still parse it.
Co-authored-by: Neil <neil@stably.ai>
Replace literal mistranslations with the wording ko.json already uses for the
same English words elsewhere:
- Host: 주인 -> 호스트 (workspace cleanup column and sort)
- Idle: 게으른 -> 유휴 상태 (workspace cleanup agent state)
- Actions: 행위 -> 작업 (artifact list header, terminal link actions search keyword)
- Source: 원천 -> 소스 코드 (branch line total chip)
Pin the values in the Korean key overrides so catalog regeneration keeps them.
Native chat code blocks always used terminalFontFamily, even with "Match
terminal interface" disabled. Use the editor font stack for code blocks
unless matching is on, and include editorFontFamily in the memoized
appearance settings so changes re-render.
Co-authored-by: phatloi0010 <phatloi0010@users.noreply.github.com>
Co-authored-by: Neil <4138956+nwparker@users.noreply.github.com>
A plugin with a worker and status bar items is now started when enabled and kept warm,
like a plugin with hooks, through one shared resident-worker predicate and warmer.
* Open large pasted text and attached text in structured chats
* Read pending pasted text before its host route resolves
* Pass structured attachment eligibility from the owning chat
* Preserve composer and Markdown state when inspecting text attachments
* fix: preserve attachment identity and cancel deferred reads
* test: consolidate phone attachment rendering contracts
* Scope attachment previews to visible chats and share route indexes
* test: consolidate duplicate attachment preview coverage
* perf: share remaining workspace catalog derivations
* feat(chat): open text attachments from structured goal objectives
* fix(chat): reuse preview owner and bind app hooks
* refactor(chat): trim duplicate tests and unused capability initialization
* test(chat): share routing scope mount fixture
* Fix routing performance attribution and folder row imports
* Share attachment capability through its domain module
* Align attachment fixtures and warm routing contracts with current gates
* Preserve relay connection timeout default for ordinary requests
* Share image classification ownership and repair integration fixtures
* Repair real attachment integration fixture boundaries
* Expose e2e compiler diagnostics and prune stale read allowance
* Type the recall fixture row ref as a div
* Keep text attachment capability in its existing capability owner
* Keep image MIME bindings in the media type owner
* Own private bridge response completion at the request boundary
* Complete bridge fixture return and retention types
* Localize native chat text attachment preview controls
* Complete attachment preview localization at presentation boundaries
* Preserve legacy preview locale identity and complete localization controls
* Fix typed mobile host witness lookup
* Commit attachment page edits and reset mobile page scroll
* test(chat): remove duplicate preview localization coverage
* fix(mobile): apply page input font and footer safe area
* fix(chat): commit edited page before admitted navigation
* fix(chat): retain field readiness on pending commit
* fix: preserve attachment field focus until control activation
* fix: restore attachment preview styles and canonical close
* Bind mobile input font role to the central theme
* Type font source fixture cases as tuples
* Attribute inherited owner filter work and qualify folder fixtures
* Keep owner filter fixture input types source-derived
* test: retain attachment capability assertion import
* test: focus attachment coverage on important regressions
* Replace text attachment paging with bounded scrolling and trim tests
* Preserve literal phone attachment whitespace and trim unused test meter
* Keep scroll view refs and measurements out of render
* Keep preview collection independent of native clipboard initialization
* Give the phone scroll fixture coherent measured DOM geometry
* Commit attachment scroll extent before restoring its anchor
* Preserve text viewport geometry across bounded reads
* Unify bounded text scrolling around the viewport
* Preserve the live text anchor across viewport resizing
* Measure committed text viewport bounds from the host
* Preserve live attachment position across native client extent changes
* Use the actual first source block in the resize regression fixture
* Reuse subscription handle type
* Keep attachment effects keyed to their existing triggers
* Keep attachment rows within the committed track
* Allow the full attachment renderer contract to settle
* Open text attachment previews in a large modal
* Preserve attachment modal header layout with primitive-owned styles
* refactor: group workspace creation and preparation owners
* refactor: coalesce concrete owner type imports
* test: preserve IPC default-ref mock at its concrete owner
* feat(browser): guard page commands with an expected URL
* fix(browser): refuse an empty --expect-url and check it on dialogs and the forwarding desktop
* fix(browser): recheck the expected URL right before keys go out
* refactor(browser): drop duplicate session type, dialog alias and per-capability sidecar fields
* chore(browser): satisfy the changed-code gates for the expected URL guard
* fix(chat): name the attachment that expired when a send is refused
The claim step knew which uploads were gone but threw a bare error, so the
refusal could only say "This attachment expired". It now carries each expired
upload's id and file name: every client names them, and desktop marks those
image chips. Older hosts and clients keep today's generic words.
* test(chat): read expired-attachment details through the wire reader
* fix(agents): stop agent rows showing pasted data as their name
Fixes#29842
* fix(agents): keep the board card's task as the raw prompt
The card only shows task when no "You" line exists, so the label never rendered.
* refactor(agents): route activity titles and mobile rows through the row label owner