* fix(native-chat): send other agents' mail as a pointer and let the person approve a denied action
Another agent's orchestration message reached a structured chat's agent as
ordinary user input, so Codex's automatic reviewer counted a coordinator's
words as the user's authorization. The chat card still shows the whole
message, labeled with its sender; the agent is now sent Orca's existing
pointer at `check`, so the content arrives as tool output. Mail stays unread
until `check` takes it, and a new coordinator is pointed at mail the old one
never read.
Codex automatic-review denials now show as a chat row with the reviewer's
reason and an "Approve once" button, which only this computer's own Orca
window may press; it uses Codex's thread/approveGuardianDeniedAction and
records the approval in the chat.
Tracked in STA-15406.
* fix(orchestration): wake any new mailbox owner after re-pointing stale mail
* fix(native-chat): settle check:changed for pointer mail and denial approval
Move the Codex approval and mobile review copy into their own modules, reuse the shared record guard, and update the tests that encoded whole-mail consumption to pointer delivery with mail read at check.
* style: format review notice copy
* fix(native-chat): hold accepted mail while custody is unreadable and show the whole denied action
* fix(orchestration): hold in-doubt mail while custody is unreadable and wake the new owner after a send-time handoff
* test(orchestration): keep crew reads off a chat host another test file left installed
The tray read the chat's MCP servers once when it opened. Opened while the agent was at rest, it said "Connect when you send your next message" and kept saying it after the agent started, and running /mcp again on the open tray did nothing. The tray now re-reads when the host reports the agent starting or stopping and each time /mcp runs, on desktop and mobile. A read asked for while one is in flight now runs after it instead of being dropped.
Expo Router decodes query params twice, so a WSL runtime host id such as
runtime:wsl%3Aubuntu-22.04 reached screens as runtime:wsl:ubuntu-22.04 and
never matched the desktop host catalog, leaving the workspace on the
offline screen. Read the route executionHost through a shared
canonicalExecutionHostId that re-encodes runtime and SSH targets, and use
it in the workspace route, notification viewing state, and web page
location readers.
Fixes#43160
Co-authored-by: Neil <neil@stably.ai>
* Give new agents plain UUID IDs
New Orca session IDs (chats, host-launched chats, terminal agent IDs) are
plain random UUIDs minted by createOrcaSessionId; the agent stays on the
record. Remove the two readers of the agent prefix: the agent.launch
sessionId refinement and the automation Open run guard. Hosts advertise
agent.launch.plain-session-id.v1; the phone reserves a plain ID only for
hosts that advertise it and keeps the legacy spelling otherwise. A replay
an older replacement host refuses as invalid params is now uncertain, not
a definite failure. Old IDs stay valid; nothing is migrated.
* Repair plain agent ID recordings and compatibility checks
* refactor: place shared settings profiles and host contracts with owners
* fix: retire stale cleanup validation contacts
* refactor: consolidate imports from concrete owners
* refactor: bind new card fixture to profile defaults owner
* style: format rebased concrete host import
* refactor: consolidate project header color owner imports
* fix: load released phone readers after folder moves
* fix: preserve released chat readers and current owner imports
* feat(jira): reorder the Tasks board lanes by dragging their headers
Jira's board configuration decided the lane order and there was no way to change it in Orca. Column headers are now drag handles, with ArrowLeft/ArrowRight as the keyboard equivalent, and the resulting order is saved per board on the device. Jira's Agile API exposes board column order read-only, so this is an Orca view preference and never edits the Jira board.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix(jira): make the saved lane order survive Jira column inserts and filtered lanes
Review follow-up. Board column keys were derived from the column index, so inserting a column in Jira orphaned every saved lane position; they now come from the column's status ids, which Jira keeps stable across config edits. Saving a reorder also replaced the stored order with only the lanes currently on screen, dropping the saved position of any lane a filter had hidden; the new order is merged into the saved one instead. A keyboard move now restores focus to the lane it moved, and the rendered probe asserts two arrow presses in a row land.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix(jira): tell screen readers a lane's issue count and its arrow-key move
Review follow-up. The lane header's aria-label replaced the visible header text, so assistive technology no longer heard how many issues the lane held, and nothing said the header moves with the Left and Right arrow keys. Both now ride on aria-description, translated in every catalog including the newly added Portuguese one, which also gains the existing reorder label.
Also registers the lane-order storage module in the WSL-move localStorage inventory, as the sibling view-mode change did, and follows the jira-types move on main.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(jira): keep the saved lane order across a runtime reconnect
Review follow-up. The lane order was stored under the status-order cache key, which ends in the provider runtime session generation. That counter restarts at zero on every launch and moves on every runtime focus change and remote session start, so a reconnect or a relaunch read the order back under a different key and silently fell back to Jira's order.
The storage key is now built from the task source, the owner's identity without the generation, and the Jira project. The generation-free identity is split out of getEnvironmentRuntimeContextKey rather than duplicated, and the status-order cache keeps its generation.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Neil <neil@stably.ai>
* feat(notifications): mute notifications per worktree
Add a per-worktree notification mute, toggled from the worktree context
menu. Muting silences the interruptions for that worktree (OS banner,
notification sound, mobile push, tray attention dot) while keeping the
passive unread indicators, and shows a small bell-off icon on the card.
The flag is stored in PersistedUIState as notificationsMutedByWorktree
(opt-in entries only), riding the same rails as showDotfilesByWorktree:
debounced writer baseline, hydration sanitizer, paired-client UiUpdate
schema, worktree delete cleanup, folder-rename re-keying, repo removal
pruning, and profile transfer.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* docs(notifications): document the touched per-worktree flag helpers
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* fix(notifications): adapt the mute gate to the attention-sink and WSL-move ledgers
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: Neil <neil@stably.ai>
* perf(mac): reuse verified terminal names across process-table captures
Each full macOS process-table capture ran one lstat per terminal on the
machine. On busy Macs that is millions of libuv pool jobs a day in the
terminal daemon, which is the load that wedges macOS's pool and makes
createOrAttach time out (#31926, #42958). Verified ttys names now last 60s;
misses and /dev scan aliases are still read live.
* perf(mac): keep verified terminal names for five minutes
Closed ptys stop reporting their device, so the TTL is only a safety
margin; a longer one removes the largest remaining pool-job source.
* fix(chat): keep replies before a mid-turn message visible in folded turns
A person's message is a boundary that keeps the reply before it, and
back-to-back replies stay visible, matching the common pattern for
completed turns. Tracked in #41393.
* fix(chat): fold a reply followed by its own tool work, judged within its turn
Tool-only rows merge into the reply before them, so a reply row that
draws tools is followed by work, not by the next reply. Adjacency is
judged within each turn, and orphaned tool results are not a person's
boundary.
* fix(chat): keep generated-image operations out of back-to-back replies
A generated-image row stripped of its preview still carries its
operation label; it is work, not a spoken reply.
* fix(chat): fold Codex image views and image status lines as work in finished turns
Codex's "Viewed image" rows and image-status lines ("Image generation failed", "preview unavailable") were stored as plain assistant text, so a finished turn counted them as replies and kept them, plus the sentence before them, visible. The Codex producer now marks them as image operations when it writes them, the same way it already marks generated images, and the fold treats them as work.
Tracked in STA-14968.
* fix(chat): keep response actions on the reply, not an image operation; tighten interleaved-turn fold test
* fix(browser): free hidden pages based on the current page only
Earlier back/forward entries no longer keep a hidden browser page alive. Edits,
child frames, audio, picture-in-picture, PDF, capture and file/document URLs on
the current page still protect it; freed pages restore their history as before.
* fix(browser): keep a hidden page whose current document is a POST result
The freed record keeps only URLs, so reopening a POST result would load a
different page by GET.
* fix(browser): restore scroll and form contents when reopening a freed page
Keep Chromium pageState in the in-memory freed-page record so reopen and
Back restore scroll position and form contents. It is never persisted,
logged or sent over IPC, and is dropped when the page closes or restores.
* fix(browser): drop a closed page's freed-page record immediately
* fix(browser): reset background-activity protection when a new document commits
* fix(browser): keep the favicon baseline across commits
* fix(browser): keep title and favicon baselines across commits
* perf(orchestration): prune settled chat output copies and reclaim orchestration.db space
Background maintenance rewrites chat workers' saved output copies of Runs settled over a day ago
to the reference later releases store, every six hours at a tenth of the thread, and returns
free pages in bounded steps once the file uses incremental auto_vacuum. New databases start
that way; Settings > Agent orchestration can restart Orca to rewrite an existing one.
* fix(orchestration): prune only copies whose chat is readable here, in bounded pages
Pages now examine a fixed window of archive rows and check each Run once, so a large Run
cannot make one slice quadratic. A copy whose chat this host cannot read stays. The restart
rewrite keeps its temporary copy on disk and records a failure for Settings to show.
* fix(orchestration): check chat readability without re-registering released workers
The readability probe builds the identity from the durable row instead of rehydrating it into
the live registry. Free-space checks use SQLite's own temp folder; a page's Run verdicts are
shared across a pass; a failed failure record no longer hides the VACUUM error.
* chore(orchestration): annotate prune casts, follow Button spacing, sync the runtime catalog
* chore(i18n): resync the runtime English catalog after rebase
* fix(orchestration): share Run verdicts across a prune pass; check the temp drive SQLite uses on Windows
* perf(orchestration): compact legacy storage during update shutdown
* test(orchestration): mock filesystem space checks through ESM factory
* Align update maintenance checks with shutdown-only work
* Drop the one-time update VACUUM; keep prune and incremental reclaim
Existing non-incremental orchestration databases stop growing because freed
pages are reused; nothing shrinks them automatically.
* Launch provider CLIs without a per-chat runtime supervisor
* Initialize process-owner fixtures with an isolated app environment
* Retire provider output transports and failed ownership drafts
* Finish provider stops when the session group empties
* Complete native cleanup from verified watcher exit and cancel held launches
* Let native watcher finish one-shot provider exits
* Retire late ownership records after canceled provider launches settle
* Reap each provider subtree in an isolated native parent
* Preserve provider outcomes and compatibility with native parents
* Publish actual provider identities and retire native parent observers
* Retire numeric writer PIDs when their group is proven absent
* Retire provider transports and accept proven group absence
* Fence retired process identities across asynchronous cleanup
* Use native timer types and readonly process fixtures
* Reuse bounded timeout for compatibility output drain
* Release launch scopes held by late transport error handlers
* Keep processless launch failures out of watcher waits
* Align lifecycle validation with final ownership contracts
* Remove duplicate helper preparation from the dev launcher
* Keep legacy fallback in place and simplify native ownership handoff
* Defer background provider maintenance until the first window
* Release startup hook maintenance for terminal launches
* Use relocated artifact module in native prebuild scripts
* Preserve agent failure outcomes and clean tools before ownership is lost
* Budget ownership capture for its bounded identity reads
* Keep lifecycle regressions at their behavior-owning seam
* Explain the fake-clock process-read fixture
* Capture tool ownership before restart recovery removes the CLI
* Skip descendant inventories for absent provider roots
* Make final output drain regression test deterministic
* Keep output drain fixture assertions type-safe with IPC
* Use existing provider fixtures across Node and Bun
* Prepare native provider helper for Codex contract CI
* Verify provider ownership using its recorded start precision
* Preserve exact provider ownership through reader failures
* Retire exhausted recovery records without blocking watcher cleanup
* Distinguish exited descendants from unreaped zombies
* Preserve group retirement without trusting an exited root
* Keep CLI input owned through native parent loss
* Keep watcher cleanup proof through lost-parent retirement
* Guard retirement against late watcher cleanup proof
* Contain provider launches that fail before stdio setup
* fix(claude): preserve startup diagnostics after input pipe failures
* fix(provider): capture lost outcomes before native completion cleanup
* fix(provider): retire speculative captures after a valid outcome
* fix(provider): share spawn absence classification through its existing boundary
* fix(sidebar): keep delete dialog height stable and show full ignored-files list
* Replace delete dialog file popovers with inline collapsible sections
* 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
* feat(languages): discover and switch community language packs
Show community translations where people choose a language: in the
Settings language dropdown (with a link to the translations catalog), a
single-list language picker that pins the device-matching translation,
a Language button in onboarding, and a one-time quiet suggestion toast.
Switching back to the previous language is always available in English.
* style: format language browser imports
* fix(languages): keep the offer action hook compilable by React Compiler
* test(e2e): drive language catalog retry through the new picker
* fix(native-chat): make Skip and agent messages agree with the async question card
Skip on a Codex async question card now saves the skipped row on the chat's host
record (agentSession.skipAsyncQuestions, modelled on cancelUsageLimitContinue), so
the status, the desktop card and the phone card all honour it. The host status read
no longer ends at another agent's message, matching the card's rule from #35758;
two partial indexes, created without a schema version bump, keep that read bounded.
* fix(native-chat): gate phone Skip on relay support; roll back only its own hide
* Share Codex account history through folder links into ~/.codex
Each Codex account home keeps its login; its history folders become folder
links (junctions on Windows) into the user's ~/.codex, and Codex's databases
follow through a sqlite_home line in the account's own config. Migration is
automatic before the next launch in each home; the store's copy wins a name
conflict and the account's copy is kept beside it. The per-file history bridge,
its link pass and the WSL bridge are removed. Claude's merge-then-link moves to
a shared async module both providers use.
* Make account history moves safe under concurrency and keep the DB with the folders
Files move by link-then-unlink so a move never replaces an existing name, host
passes run one at a time per store, index markers are written before a move,
account-only folders are shared, lock folders are moved rather than deleted,
and sqlite_home is written only once a home's sessions are linked.
* Let the history pass own sqlite_home, link locks first, and index per store
The pass that links a home's folders now writes and removes its sqlite_home
line; the config mirror only carries it forward. thread-writer-locks is linked
before any history, index markers are kept once per store (hard-linked
duplicates included), WSL links the launched home before Codex starts, passes
queue per home in request order, and re-sharing after off then on works with
earlier conflicts still kept.
* Never overwrite on move, gate indexing on moves, and read the shared DB for backfill
Files move by link or exclusive copy; repeat conflicts get their own pending folder; secrets and
sandbox setup stay per home; the sqlite_home write retries against a concurrent mirror; indexing
waits until no move is running; backfill checks read the DB where sqlite_home puts it.
* Keep live writers' files, require both history links, and keep unmoved history on removal
Files move only by a new name for their inode; a home is shared only when sessions and
archived_sessions both link; reverted-thread rollouts get index markers; settled homes skip
repeat passes in either mode; account removal keeps a real history folder.
* Give resume test runtime-home mocks the account history step
* Keep unmoved WSL history on removal, prepare the launched home, and retry incomplete work
WSL account removal keeps real sessions/archived_sessions; a launch prepares the account it
returns even if the selection changed meanwhile; an incomplete unshare and a failed WSL index
pass stay eligible for a later launch; the guest helper rechecks the distro before each step.
* Keep pinned resumes reachable, finish interrupted unshares, and keep index work from racing moves
A pinned resume only shares; a launch re-prepares when the selection or setting changed; Orca's
sqlite_home line is read only at the config root; a writer-lock link elsewhere keeps the home
private; an unshare finishes its database move on retry; indexing keeps markers a newer move
recorded, retries an incomplete run on a later launch, and merges WSL marker lists.
* Move account history into a store one pass at a time and retry incomplete moves
Two homes merging into one store at once raced on its folders and stranded the second home's
history in its merge folder. Passes now run one at a time per store (host) and per distro (WSL),
a folder that appears mid-move is merged into, and a share with failed moves is not settled.
* Keep one rollout form in ~/.codex, record what sharing left behind, and guard Windows homes from older builds
- A rollout present as .jsonl and .jsonl.zst lands in the store in one form only; the other form moves to the home's .orca-set-aside-rollouts, never deleted.
- Each account home gets a versioned cleanup manifest: set-aside databases, left-behind rollouts with a background content check against the store, store twin pairs, and the shared streak.
- Native Windows homes get a renamed ownership marker before their first junction, so older builds refuse to use or delete them.
- Account removal keeps the set-aside rollouts and the manifest.
* Set a rollout form aside only beside its twin in the store, inventory leftovers off the launch path, and keep account databases on removal
- The .zst moves first and a form is kept out only when the store already holds its twin, so a failed move never leaves the store with neither form.
- The rollout inventory and store twin walk run in the detached check, not the awaited pass; manifest writes are serialized per home and a check applies only to unchanged files; checkpoints are time-spaced.
- A WSL check that runs out of budget resumes on a later launch instead of looping.
- The ownership check reads either marker in one step and the marker rename retries on Windows.
- Account removal keeps the account's Codex databases for the later cleanup release.
* Read the cleanup manifest through a type guard
* Read the cleanup manifest through a type guard over unknown
* Settle only a check's own request, skip queued WSL passes after quit, and validate manifest entries
- A pass finishing during a check keeps its new check request on host and WSL.
- A WSL pass queued before quit no longer starts guest work.
- Manifest rollouts must carry a path, size and mtime to be read.
- The store twin scan reuses the twin module's folder walk.
* Walk the store outside the manifest write and keep databases on removal only for shared homes
- The inventory writes only its own fields onto a freshly read manifest, so it never undoes a streak reset from another process and a launch never waits behind the walk.
- Account removal keeps the home's Codex databases only when the cleanup manifest shows the home was shared.
* Lock the cleanup manifest across processes and validate every field later passes read
- Manifest writes take a file lock, so a WSL check helper can't publish over another helper's streak reset.
- The guard also checks storePath, the content check's store facts, database entries and sharedPasses; anything else is rebuilt from disk.
* fix(mobile): run chat report scripts in an isolated shell frame
* fix(mobile): theme chat visuals at handoff and pin the iOS frame to Android's
* test(mobile): probe the page origin by absolute URL from the visual
* fix(source-control): stop offering Amp and Muse for non-naming AI text
Amp and Muse can't take the read-only text task policy, so the policy refuses
them for everything but chat naming. The picker and the operation resolver
still offered them, and the refusal surfaced as "could not be started".
Keep the naming-only fact in the shared agent spec module and use it in the
resolver, every agent list for these actions, and the policy backstop.
* fix(source-control): keep recipe args before the prompt terminator
Muse ends its argv with `-- <prompt>`, so recipe args such as --model were
inserted after `--` and became prompt text.
Co-authored-by: intelmib <intelmib@gmail.com>
---------
Co-authored-by: intelmib <intelmib@gmail.com>
* fix(plugins): show only what an update adds in its review
The update review compared Before and After columns that mostly repeated what the user had already
approved, and labelled new custom editors, hooks, settings pages and status bar items with the
vague "Features that act for you". It now lists just the additions, naming each one (a new editor
names the file types it opens), and says so plainly when Orca couldn't compare the versions,
opening the full access list.
* fix(plugins): keep a failed comparison and every grant visible in the update review
- Says Orca couldn't compare whenever main sent no comparison, even when the source also moved, and
opens the full access list then.
- Lists every new grant main asks about, not only the ones this plugin type can use.
- Names editor growth per editor id: new file types, files it now opens by default, else a generic
line; waits for the installed manifest so the line doesn't change under the reader.
- "Adds panels" and "Reacts to more Orca events" replace "Panels" and "More events".
* feat(plugins): approve held updates from the toast, open the review anywhere, group approvals
- The review and the toast name each plugin's publisher ("Official · stablyai", "Community · …").
- The held-update toast lists each plugin with what it adds and the not-official warning when one
applies, and approves in place when every update was compared and can install; otherwise, or
for more than three plugins, "Details" opens the review.
- The review opens over the app instead of sending the user to Settings → Plugins.
- Several updates that need approval are one grouped review with a checkbox each and one
"Approve & update", instead of a separate Review per plugin.
* fix(plugins): offer approval only once every addition is shown, keep late notices
- The toast and the review read the installed manifest with the preview, so "Approve & update"
exists only once every line it approves is on screen; the toast also needs the installed entry.
- A notice that arrives while the toast installs stays on screen; a newer version of a plugin
reloads its details instead of showing the old ones.
- Retrying in the toast skips the updates that already landed; an update whose bytes changed
after review says it waits in Settings → Plugins instead of reporting success.
- In "Update all…", approvals beside plain updates start unticked; the not-official warning sits
under its plugin's name and names the catalog owner.
- The toast e2e covers Details and approving in place.
* fix(plugins): a compact community badge and a history link in the update review
- "Community plugin · owner" with the warning icon replaces the not-official banner in the review
and the toast; the trust advice shows on hover or focus.
- The version text links to the plugin's history on GitHub at the reviewed commit, and a moved
repository is one short line instead of two URLs.
* refactor(plugins): share update loading and installing, keep the toast out of the store
- One loadUpdate and one installUpdates serve the review and the toast; both now say when an
update's bytes changed after review.
- The notice store holds data only; PluginUpdateReviewHost renders the toast and the dialog.
- The update lines users approve are protected copy; the version link sits outside the checkbox
label; a community plugin that runs no code gets the same "Community plugin" label, unmarked.
- Tests for notice merging and for approving only the reviewed fingerprint.
* fix(plugins): a warning Badge variant for the community badge; tests without casts
The wait-for-setup gate printed a bare "Setup failed; skipping agent
startup." with no reason, so users could not tell a failed setup step
from an Orca defect. Both the POSIX and Windows PowerShell waiters now
print the setup exit code and point at the Setup terminal, where the
failing output lives. Exit codes and agent gating are unchanged.
Refs #38473
* feat(tab-bar): customizable icon row for the + menu's create actions (#40359)
The + menu's New Terminal/Browser/Markdown/Open Markdown/Mobile Emulator rows become one
row of icons. A gear at its end opens a customizer to reorder (drag or Alt+Up/Down), hide,
and assign shortcuts to each item; the icon strip scrolls sideways when plugin file types
overfill it. A turned-off Mobile Emulator shows under Hidden and can be turned back on from
there, and the intro callout's Hide now only removes it from the menu (with Undo).
Shortcut validation and saving move into useKeybindingActionEditor, shared with the
Settings shortcuts pane.
* fix(tab-bar): address review on the + menu icon row
- Move Reset Order and All Keyboard Shortcuts into a ⋮ menu in the customizer header.
- Give the floating panel its own layout and no emulator Off item (newTabMenuSurface).
- Escape closes the menu while an icon tooltip is shown; recording ends once focus leaves it.
- Row is labelled as a whole with aria-activedescendant on the chosen icon; e2e selectors
target the icon buttons.
- Don't persist a turned-off emulator as hidden; normalize layouts on settings load.
- Reuse tab-strip resize/wheel helpers, share the recorder-focus hook, split the icon strip,
use ShortcutKeyCombo in tooltips and an allowed elevation for dragged rows.
* fix(tab-bar): keep the create row React Compiler-clean and stop swallowing wheel when it fits
* fix(tab-bar): address CodeRabbit review on the + menu icon row
- Return both layouts in the paired-client settings projection.
- Keep unavailable items at their saved slot when re-saving a layout.
- Ignore shortcut saves that finish after a newer recording session started.
- Make the customizer scrollable; announce the chosen icon via a live region.
- Confirm the intro's Hide only after the write succeeds.
- Render compact recorder chips with ShortcutKeyCombo.
Older WebKit (iOS < 16.4) throws a SyntaxError when parsing regex
lookbehind, which breaks the paired mobile web bundle at load time.
Replace the two lookbehinds in shared code that ships to that bundle
with capture-group equivalents:
- jcode terminal title: (^|\S) anchors each run of status segments and
is restored via $1, keeping long space runs linear.
- dictation near-miss sound key: capture the preceding vowel instead of
asserting it.
Co-authored-by: Neil <4138956+nwparker@users.noreply.github.com>
* feat(accounts): show each saved Claude and Codex account's observed plan
Settings > Accounts rows now show the plan Orca already observed for that
exact account ("Max 20x", "Pro", "Team"); unknown stays blank. The usage
roster's plan slot no longer shows "Unknown".
- Claude: read subscriptionType/rateLimitTier from the credential candidate
already chosen, tolerantly; the tier only refines Max.
- Codex: keep the plan the app-server already returns with usage.
- Each successful Claude/Codex reading names the saved account and runtime
slot it was read for; rows match that, never the roster's selection, so a
switch in another window cannot paint one account's plan on another.
Older hosts send no stamp and their rows stay blank.
- Remote rows use only the owner's account stream.
- A Codex workspace label that may itself name a plan is kept and gets no
second plan.
* fix(accounts): keep plan attribution through Codex resets and spend-capped supplements
- Stamp the usage read that follows a reset-credit redemption with the
redeemed home's account, so the row keeps its plan.
- Keep the backend plan when the HTTP supplement adds only a monthly window.
- Keep the Claude plan spelling Claude Code wrote.
- Remote scope ignores this desktop's usage pushes.
* fix(accounts): name the account on the reset reply and skip plans for hidden sections
- The reset reply replaces the renderer's usage state, so stamp it the same
way as the published reading.
- A provider section hidden by Settings search builds no plan index.
* fix(native-chat): keep the reply before a background task hand-back in terminal chats
Claude's task-notification record opens a new turn, but the chat transcript
decoder dropped it, so the hand-back reply joined the prompt's turn and the
turn fold hid the reply before it. Chat reads now keep a wordless turn marker
there, and journal-less turn grouping and timing start a turn at it.
* fix(native-chat): keep tool results a task notification delivers mid-turn
* fix(native-chat): draw only the bar for the turn marker on mobile, not every empty system row