Holding Cmd/Ctrl swapped the round Send/Stop button for a wide labeled pill,
pushing the model picker, context ring and mic left. The preview now keeps
Send's round button and only swaps its icon (CornerDownRight for steer,
ListEnd for queue); the label stays as the aria-label. With Steer queued,
the head queued card's Steer button also fills as the primary.
The phone composer had the same pill and now follows the same rule.
The site now lives at orca.dev; the old onorca.dev and www.onorca.dev hosts
redirect there. Linking to orca.dev directly skips that redirect.
Only page links change. Service hosts, sign-in and relay endpoints stay as they are.
The Agents list titled a thread with the tab's generated title, the first
prompt that tab saw. After `claude --resume` in a new tab, that is the
message sent after the resume, so the list kept a status note as the
thread's name while the tab and the agent row showed the session's own
name. Rank a named provider title of the pane's own session above the
generated title, as resolveTabNameSource does, and share the session
ownership check with the agent row.
GitLab showed in the new-workspace source tabs on some opens and not others. Its availability required the app-wide preflight status to match the current host/workspace context, and opening the composer for another context invalidated it until the async glab probe returned. Remember the last known glab answer per preflight context while a fresh probe runs, and keep a chosen GitLab tab during the re-check, as Linear already does.
* feat(cmd-j): extra sources can lead the empty list and draw in the workspace row box
A source sets emptyQueryPlacement 'first' to sit above Recent Chats & Terminals; the default
selection stays on the first row below it. Extra rows use the workspace row box with the line
inline after the title. Public registers no sources, so nothing changes in public builds.
* refactor(cmd-j): palette rows share one row-box variant; extra rows reuse the tab title line
* fix(cmd-j): the empty query's default row follows recent tabs that arrive after mount
The deferred-query reset committed the first render's list head, before the recent-tab
snapshot existed, so Enter landed on the first workspace instead of the latest tab.
* test(cmd-j): pin the empty query's Enter default to the latest recent tab under StrictMode
Real cmdk, StrictMode render: the re-run deferred-query effect committed the first render's
head (a workspace) before the recent-tab snapshot existed. Dev builds only; production does
not re-run mount effects.
* feat(orchestration): let coordinators approve worker permission prompts when the user turns it on
One setting on the orchestration page, off by default. When on, the
escalation offers orchestration approve and deny, both with a reason, and
the user still sees Allow/Deny: the first answer wins. A prompt the
worker's agent lets only a person approve is refused and stays with the
user. The machine running the worker enforces its own setting.
* fix(native-chat): a worker approval's receipt shows the command, not its tool input as JSON
* test(orchestration): list every worker-side case in the coordinator approval table
* chore(i18n): ship the coordinator approval setting's search keywords in the runtime catalog
* fix(orchestration): a reasonless allow keeps the person's refusal, and terminal checks no hook may approve are person-only
* fix(orchestration): address review on coordinator approvals
- A person-only chat prompt answered meanwhile reports as closed.
- A terminal allow reads Claude's warning from the screen it checks, so a
late-painted person-only warning still refuses before the hook is used.
- The receipt keeps a chat worker's whole command.
- orchestration approve prints the reason it sent.
* fix(native-chat): read the receipt's command through a parsed shape, not Reflect
* docs(skills): drop worker permission prompt guidance; the escalation carries it
* fix(orchestration): label follow-up worker cards, gate remote-owned start cards on ready
A send that continues a finished or closed worker starts a follow-up Dispatch,
and the coordinator's chat showed it as "Started worker". The agent-start item
now carries the Dispatch it followed and whether the conversation reopened, and
the card reads "Reopened worker" or "Sent follow-up to worker".
worker-start --on a server that owns its workers wrote the card for any parsed
answer, with no agent kind. It now passes the started agent and writes the
card only once the server readied the worker, as local and attached starts do.
* test(native-chat): assert follow-up heading kind, not its copy
* fix(native-chat): keep branch hover beside its label
Let composer branch controls use their content width and shrink long labels within the footer.
Co-authored-by: Wooseong Kim <innocarpe@gmail.com>
* Keep composer branch hit targets compact under width pressure
Co-authored-by: Wooseong Kim <innocarpe@gmail.com>
* Exercise full composer context at large text sizes
* Seed complete settings in the composer fixture
---------
Co-authored-by: Wooseong Kim <innocarpe@gmail.com>
* feat(settings): move Remove project to a confirmed row at the bottom of Project Settings
* chore(i18n): sync protected copy keys for the remove-project dialog
* fix(settings): use primitive variants in the remove-project disclosure and dialog
* fix(settings): keep remove-project row off the per-write store path
The terminal count now lives in a dialog-only component, and the VM-recipe check is
memoized on worktree/runtime identity. Checkouts are grouped by host id, SSH labels
resolve through the setup's runtime owner, and a runtime missing from the catalog
shows as Unknown host instead of its raw id.
* fix(settings): select only the removed repos' worktree lists
Selecting the whole worktreesByRepo map re-rendered the remove-project row on every
other repo's worktree write. Also drop the orphaned terminalCount catalog keys.
* fix(settings): count remove-project terminals once on open; hide raw SSH ids
The dialog's terminal warning reads the count when Remove… is clicked instead of
subscribing, so no store write walks tabs. An SSH host with no label now shows as
Unknown host like an unlisted runtime, since generated target ids mean nothing to users.
* fix(settings): re-check terminal count before removing a project
A terminal opened from another client while the confirm dialog is up would close
without warning. Confirm now re-reads the count and, if it grew, updates the warning
and waits for a second confirm.
* test(settings): build remove-project fixture setups without a type assertion
* test(settings): cover the remove-project confirm holding for new terminals
* test(settings): drop the copy assertion from the remove-project confirm test
Agent reload treated did-fail-load as success, so it returned ok while the page showed a network error page; it now reports the page's load error like goto. A restored page stopped before its first commit holds only Chromium's initial empty entry, so native reload did nothing: the Reload button now navigates to the saved URL, and agent reload fails fast instead of waiting 10s and claiming success.
* fix(wsl): show Connecting instead of a stale read error while a WSL host starts
After Start, a WSL host can take tens of seconds to boot and update its server. The editor,
file tree and source control dropped the stopped notice as soon as the host left 'stopped'
and showed the error from the read that failed while it was down, telling the user to go to
Settings. They now keep the notice up as 'Connecting to <distro>…', and the editor's retry
waits for the WSL host and reloads the file when it answers, as it already did for SSH.
* fix(wsl): skip the post-Start reload when the WSL retry already loaded the file
Review follow-up: once the editor's retry reloads a file when its WSL host turns ready, Start's
own reload would clear and re-read it, flashing a spinner. Start now reloads only a file that is
still failed.
* fix(wsl): reduced-motion spinner for Connecting; SSH targets keep their own retry signal
Review follow-up: the Connecting notice uses LoadingSpinner at size-4 per the style guide, and
the editor reads WSL host status only for a workspace with no SSH target.
* test(editor): cover a Start reload of a still-failed file; share reload option constants
* fix(wsl): reduced-motion spinner on the Start button too
* fix(native-chat): refresh skills when reopening the picker
* fix(native-chat): show the last skill list while the reopened picker rechecks
Clearing the renderer snapshot on close made every / or $ open start in a
loading state. Keep the last answer per pane, show it at once on reopen, and
ask the host once per open.
* fix(native-chat): keep a late skill scan as the next open's fallback
* test(native-chat): feed skill picker tests fixed host answers
Importing the main-process scanner pulled src/main into the web typecheck
project.
---------
Co-authored-by: Kelvin Amoaba <97001695+AmoabaKelvin@users.noreply.github.com>
ProseMirror resolves a click on the right half of an inline atom to the
position after it, so the rich editor's modifier-click router read the
following node. Wikilinks and superscript citation links did nothing when
clicked there. Resolve the atom the click landed on instead.
Co-authored-by: Wooseong Kim <innocarpe@gmail.com>
* revert: worker permission approvals (#40756)
This reverts commit 818055fcbb.
The feature misbehaves in real use: an Allow on a worker's approval card
was recorded as closed without an answer, and closed approval cards render
at the bottom of the coordinator chat, below newer messages.
Removed: the Claude PermissionRequest hook hold and its 130 s timeout,
the approval card in the coordinator chat, `orchestration deny`, the
approval payload on stop escalations, and the held-delivery lines on send
receipts. Escalation text goes back to its pre-#40756 wording.
Kept from later commits:
- #40983 (lost-worker alerts): its `lost` reason, cause/leftover/settled
fields, turnStartedAt and the rejected-report check stay; only the
approval branches around them are removed.
- #41158 (owner moves) and the test cleanups (#41151, #41175, #41177)
only touched approval code that is now deleted.
* feat(orchestration): answer workers' permission prompts from the coordinator (re-land of #40756)
* fix(orchestration): credit an approval from Claude's own decision record and place each worker card at its time
- An Allow that Claude took is answered by the person even when the command then fails or is still running; a failed command's PostToolUseFailure counts as ran.
- Expired means the agent's own timeout only; a close Orca can't name is not an expiry, and reasonDelivered is true only with a reason.
- Escalations wait for the dialog to paint and read Claude's warning even when a long command hides the top of its box.
- Worker cards and receipts render after the message they followed in time, not after the whole conversation; the toast says what happened.
* fix(native-chat): place timed rows without a memo the compiler skips
* perf(orchestration): feed chat approvals from their own stream, pin open cards, close cards whose worker ended
Native chats no longer subscribe to the crew stream for worker approvals. A
narrow orchestration.workerApprovalsSubscribe stream per chat party wakes only
on that party's own mail and on Run/Dispatch changes, never on agent status,
and reads the crew only when the approval list itself changes. The pane no
longer redraws for approvals: the transcript receipts and the pinned stack
each hold the feed themselves.
Open worker prompts are pinned above the composer (above the chat's own
prompt), oldest first, in a bounded scrolling stack; the transcript keeps only
receipts, at the time the worker asked. The countdown ticks only for open
cards in a visible pane.
An approval whose Dispatch is no longer running reads as closed ("No longer
open · worker ended"); a hook that hangs up after its worker is gone closes as
worker-ended rather than "answer it in the terminal"; and a click that finds
the prompt or Dispatch already gone turns the card into its receipt at once.
Also carries over: a stop owes a closing line only to an approval whose
escalation went out.
* fix(native-chat): no toast when a worker approval answer lands; the card's receipt says it
* fix(native-chat): a worker approval card answers on click, as the chat's own prompt does
The card turns into 'Allowed by you' at once and Claude's confirmation runs behind it; only an answer
Claude did not take changes it to the real outcome, and a failure reopens the card.
* fix(orchestration): keep main's stop-report index for the open-approval sweep after the re-land
* fix(orchestration): final-review fixes for chat worker approvals
- A click that gets approval_not_open no longer hides the card: the host's list decides, so a
prompt the host still holds stays answerable. Only dispatch_inactive closes it locally.
- The approvals stream watches only the orchestration database's own changes (Runs, Dispatches,
mail), not terminal identity notices, so agent status and title changes cost it nothing in main.
- Receipts are the chat's history: no 30-minute window, bounded by 100 rows with still-open
prompts kept first.
- The pinned stack is capped against the pane and gives way first, so the chat's own prompt keeps
its room; a prompt that closes while shown stays pinned as its receipt for 4 s, and one only the
worker's terminal can answer stays pinned.
- A close no one named, after the worker's Dispatch ended, reads as worker-ended, and an
unanswered close of an ended worker sends the coordinator no second notice.
- The transcript's receipts keep one array until a receipt changes.
* refactor(native-chat): a worker approval card waits on the host after a click instead of answering ahead of it
Both buttons turn off and the clicked one shows a spinner until the answer returns; the host's list
then turns the card into its receipt. Drops the client-side close and its reconciliation.
* fix(native-chat): let the compiler memoize the worker approval answer handler
* feat(project-admission): open menu-first Add project flow with synced host header
* fix(project-admission): keep pending remote default hosts and settle partial folder batches
* refactor(project-admission): dedupe Add project menu items and surface picker failures
- Render Browse/Clone/Create from one action table with a shared submenu-close handler
- Toast native folder-picker rejections instead of leaving an unhandled promise
- Fall back to the plain combobox Add project row whenever the cascade menu is unavailable
- Memoize the host index in useAddRepoHostSelection and drop stable setters from deps
* fix(project-admission): keep state setters in host-selection deps for React Compiler
* Tidy the Settings → Agents installed list
Rows line up on one line, the default agent gets a Default pill, and
Set as default moves into each row's ⋯ menu. Chat/CLI stays in place,
grayed out, when an agent is off. Click a row to expand its settings.
* Keep a saved default clearable when its agent isn't installed
The ⋯ checkbox follows the saved default, not the badge, so a saved
agent that isn't detected still shows Default and can go back to Auto.
Row hover uses the list-row accent token.
* Use plain items in the agent row's ⋯ menu
No checkmark column: Set as default, or Clear default agent on the saved
default, then Docs/Install aligned to the menu edge.
* Move local usage services into a supervised backend process
* Own usage recovery and worker retirement lifetimes
* Preserve answered usage data during background refresh
* Run independent usage scans concurrently in the backend
* Limit backend startup paths to the delegated usage service
* Show usage failures through backend recovery
* Include usage failure strings in the English catalog
* Keep usage update details beside refresh failures
* Resolve usage freshness failure from the final producer snapshot
* Retain the forced refresh completion requirement
* Keep managed backend failures out of application crash reports
* Preserve usage recovery boundaries across backend reconnects
* Match the backend RPC cancellation signal in the usage seam proof
* Avoid serializing backend requests before port delivery
* Keep receiving request validation in the boundary schemas
* test: align usage transport coverage with renderer project
* fix: preserve unknown usage state and renderer retirement
* fix(usage): revalidate tracking before scan admission
* fix(usage): retry failed backend startup on demand
* test(usage): isolate stale backend ownership checks
* fix(pr-page): let the Start workspace button grow to fit its label
The pull request header pinned that button to 180px with nowrap, so longer
translations overflowed both edges and the arrow slid under the chevron.
A minimum width keeps the stable size for short labels.
tracked in STA-14595
Co-authored-by: 정의현 <rabbitdy0101@lemong.ai>
* fix(pr-page): wrap the header when the workspace button no longer fits
A long Start or Resume label grew past a narrow pull request page, the title
collapsed, and the chevron was clipped. The title now keeps a floor so the
actions wrap under it, and the label wraps only when that row is still too
narrow.
tracked in STA-14595
Co-authored-by: 정의현 <rabbitdy0101@lemong.ai>
---------
Co-authored-by: 정의현 <rabbitdy0101@lemong.ai>
* fix(native-chat): hold an automatic continue until the chat's account has usage again
The automatic continue after a usage limit sent at the cut's reported reset
without looking at the account, so it could send into a still-spent weekly
window. Each sweep pass now attributes the chat's launch account (the host's
launchAccountHome) to Orca's polled reading taken in that same home, and holds
the send until the latest spent window's reset (+15 s). The hold is derived
each pass, never saved, only grows for one cut and account, and waits up to two
minutes for a reading taken since that reset before falling back to the reset
it has. A spent window with no known reset stops the automatic continue for that
cut; on System Default, where Orca can't tell which login a reading saw, a fresh
reading with room releases both. Rows on desktop and phone show the held time
through an optional continueAt; older clients keep the cut's time.
* fix(native-chat): attribute usage holds once per account and retire them with their scope
- C1/X7: launch home resolved once per provider and reading once per (provider, home) per pass; narrow usageReading accessor replaces getState().
- X8: forget() drops the hold; hidden-chat caches are pruned while the setting is off; readState stores nothing for an unattributed chat.
- X3/C3: launch and reading homes compared in canonical form (~, dot segments, async realpath, bounded cache).
- X4/C2: a hold belongs to its scope (canonical home + billing kind) and retires when it changes.
- X2: a launch whose provider has no reading yet asks once and waits within the two-minute window.
- X5: attribution runs before the overdue check, so a restart keeps the account's later reset.
- X6: the launch account is re-attributed right before each send; beforeRun refuses a changed attribution.
- C5: cold chats publish when their continue time moves.
- X1/C4: WSL launches keep the cut's own reset (no hold).
* fix(native-chat): gate held continues on an account scope token and stop reviving stale cuts
- C6: a hold extends only with a spent window that had begun by the cut's reset.
- X6-R2, X10, P1-1: a synchronous account scope token (selection, launch env, reading home and
provenance) is captured at attribution; send() re-resolves only when it moved, memoized per
token, and beforeRun compares live and captured tokens. Opening a chat drops only cold-cut caches.
- X11: production tick() test at N=300 and 10N=3000 counts resolver and reader calls.
- X2-R2: the bootstrap wait starts when a pass first sees the due send without a reading.
- X9: canonical homes are resolved once per account per pass; the unbounded-lifetime cache is gone.
- C5-R2: unloaded chats have no status push path, so the cold continueAt publication is removed.
* fix(native-chat): separate continue eligibility from current spending and bind sends to their attribution's sources
- X12: a cut's eligible anchor (its reset, an established hold, or a covering window) takes the
24 h overdue test; once eligible, every currently spent window holds the send.
- X13/P1-2, X6-R3: the account owner returns attributions with a synchronous source witness
(settings snapshot identity, cached login-shell capture revision, reading-source identity);
Claude billing comes from the launch's own env composition. A result whose sources moved while
it resolved is discarded; send() and beforeRun bind to the attribution's own witness and
supersede without spending an attempt.
- CI-1: the scope-token type assertion is gone with the token.
* fix(native-chat): keep a covering hold beside spent windows of unknown reset
- X12-R4 / C7: rebuilding the covering anchor skips spent windows whose reset, and so start, is
unknown; the eligible branch still refuses on them.
- E1-R4: the preparation-change and suspended-attribution race tests run on a Claude chat
through the real host send, mutation and accepted settlement.
* refactor(native-chat): move the usage-limit continue status into its own wire module
The merge with main put agent-session-wire.ts one line over the 300-line limit.
* fix(native-chat): read the shell capture revision lazily so module mocks without it still load
Tests that main added mock login-shell-environment without the revision accessor, so binding it at module load failed.
* fix(native-chat): release a usage hold on fresh room for any account without stranding the cut
- QA-1: room in a fresh attributed reading newer than the last spent evidence (spentSeenAt)
releases the hold and clears an unknown reset for every account; the System Default-only
branch and identityKnown are gone.
- QA-1b: the release pulls heldUntil down to that reading instead of clearing it, and an
unknown-reset hold anchors on its last evidence, so a release over a day after the cut sends.
* fix(native-chat): release an expired usage hold from its room reading and ask for readings while a reset is unknown
- R6-1 / QA-1b-R6: a release sets heldUntil to the room reading itself, so an expired finite
hold followed by an unknown reset no longer strands the cut.
- R6-2: the usage poller idles while Orca is unfocused with no viewer, so an unknown reset asks
for a non-forced reading at most every 10 minutes through the existing refresh.
* fix(native-chat): bound unknown-reset readings per account and honor the failure backoff
- R7-1 / X-R7-1: the rate-limit service owns the automatic-read cadence: a read waits while the
provider's last reading or admitted automatic read is within the asked interval, so held chats
on one account cause at most one unknown-reset read per 10 minutes.
- R7-2: automatic reads wait out the poller's failure backoff (shared failureRetryDue) and start
its clock; forced refreshes are unchanged.
* fix(rate-limits): scope automatic usage-read admission to the selected account
- R8-1 / X-R8-1: an admitted automatic read counts toward the cadence only for the account whose
reading source the service held then, so a switch never lets one account's read delay another's.
- Prunes the flaky-test-pattern baseline: service-refresh-orchestration no longer reads the wall clock.
* fix(native-chat): keep a usage-reading request retryable until the service starts it, and show the last known reset while one is unknown
* fix(native-chat): show no automatic continue while a chat waits on an unknown reset, since fresh room still releases it
* fix(native-chat): publish no continue time for a cancelled or stopped cut while its account's reset is unknown
* fix(native-chat): refuse a stale startup-dialog card choice and add a card for the multi-server MCP dialog
* fix(native-chat): drop casts from the startup-dialog guard
* fix(native-chat): refuse a startup card choice until the screen model has applied all received output
* fix(native-chat): refuse a clipped MCP server list and guard restored startup cards
* fix(native-chat): allow one startup card choice per screen so a second client's keys can't hit the next dialog
Keep typed &, <, and > literal in prose text nodes when encoding them as HTML entities cannot change how the Markdown parses, while leaving entity-like sequences, HTML/autolink/blockquote-ambiguous tokens, and code spans intact.
Refs #16469
Refs #20177
Co-authored-by: Frederic Barthelemy <git@fbartho.com>
Structured image sends replace inline composer chips with `[Image #N]` tokens
for the provider prompt, which left sent `[Image #N]` markers visible in user
message bubbles, copied text, rail/outline previews, and row height estimates.
Strip in-range `[Image #1..imageCount]` markers across user message display,
copy text, row height estimation, and rail/outline previews while preserving
literal markers past `imageCount`, in quoted file references, or inside inline
backticks and fenced code blocks.
Fixes#32727
Co-authored-by: lurunzi <lurunzi@gmail.com>
A chat Stop wrote Escape directly to the runtime PTY, bypassing xterm onData so agents that emit no interrupt hook stayed Working in the sidebar. Send Stop's Escape via sendRawVerified and observe plain-escape against the pre-Escape status baseline only after write settlement.
Fixes#31786
Co-authored-by: Zetao Qi <256975935+QZTnb@users.noreply.github.com>
Reuse the indexed original-pane target on VaultSessionRow so terminal Session History rows display their open tab's customTitle when getKnownExecutionHostIdForWorktree matches the session host, without defaulting unhydrated or unknown worktrees to local.
Fixes#33661
Co-authored-by: David Garcia <davidgarciab@gmail.com>
Escape or an item that skips refocus unmounts the focused menu onto <body>;
refocus the menu pane then, but leave focus where an outside click put it.
Fixes#21015
Co-authored-by: ckdwns9121 <40492343+ckdwns9121@users.noreply.github.com>