* feat(browser): move extensions out of Experimental into Settings › Browser, on by default
The old experimentalBrowserExtensions key is retired on load so profiles that saved the old false default start with extensions on.
* test(startup): mock extension startup in the ready-phase identity test
Extensions now default on, so ready-phase startup installs extension support, which this browser-identity fixture's Electron and store fakes don't cover.
* feat(mobile): pick the PR glyph from PR state
Workspace rows always drew the open-PR glyph and only changed its color,
and the PR tab's state badge had no glyph. Both now show merged, closed and
draft glyphs, from one prStateIcon mapping that the details sheet and task
rows also use.
* feat(mobile): show the PR state on the session header's source-control button
The button always drew a branch glyph. When the worktree's catalog row has a
linked PR it now draws that PR's state glyph in its state colour, read from
the host list's worktree.ps query in its own component.
* fix(mobile): read the header's PR state from the catalog cache only
Opening a session must not request worktree.ps before its first paint, so the
source-control button reads what the host list last loaded instead of
fetching it.
Codex's skip key (Ctrl+]) drops an async question only in its TUI: no hook,
no transcript line. Orca kept the question open and the row waiting until
the turn ended. The renderer now forwards the skip keystroke as a codexSkip
question inference; main drops one question from the tracker and restates
the row, returning it to working once none remain.
* fix(agent-status): stop Orca's spinner title fighting Cursor's own title
cursor-agent now paints its own '<chat> - ⏳ Working' title, animated every
200 ms. Orca still reasserted '⠋ Cursor Agent' on every Cursor hook and every
80 ms, so the tab and sidebar flipped between the two. Leave the working title
to Cursor, as for Codex; Orca still writes the ready and action-required titles.
* fix(agent-status): read cursor-agent's own status titles
With Orca no longer writing working titles over cursor-agent, every title
reader saw Cursor's '<chat> - ⏳ Working' titles as no status, so a Cursor
worker stopped taking orchestration mail mid-turn. Parse cursor-agent's exact
emoji + label pairs in the shared title classifier; review, loading, cloud and
reconnect screens are not a running turn and stay unclassified.
* fix(agent-status): keep the Cursor title parser ASCII for orcad bundles
esbuild leaves regex literals as written, and orcad rejects a non-ASCII
server bundle; escape the emoji instead.
The launcher's Pi panel now shows Pi's thinking levels on the terminal
surface, narrowed to what the picked model supports, and a pick starts
Pi with `--thinking <level>`. Untouched, Pi keeps its own default.
Co-authored-by: lucas-wu-wakakak <8309814+lucas-wu-wakakak@users.noreply.github.com>
Pi had no launch catalog, so a picked model compiled to no arguments.
A launch-only catalog maps it to `pi --model <provider/id>`. A --model
in Pi's Arguments stays literal: Pi's CLI fuzzy-matches it, while Pi
chats need an exact provider/id.
Co-authored-by: lucas-wu-wakakak <8309814+lucas-wu-wakakak@users.noreply.github.com>
* fix(agent-status): prevent shared-service OpenCode OSC 7501 from marking idle tabs working (#39619)
* fix(agent-status): scope OpenCode shared-folder OSC 7501 to the pane's hook
OpenCode 2 keys its OSC 7501 records by root sessions and never by
child sessions, so drop the parent/child id exception. Keep OpenCode's
all-idle report able to settle a hook-silent pane, and move the
precedence test to the server layer.
* fix(agent-status): keep another OpenCode session's status off a hooked pane
OpenCode's OSC 7501 root summarizes every session sharing the folder's
tabs, so its block or title on an OpenCode hook row belongs to another
pane. The pane's own prompts already come from Orca's plugin.
* refactor(agent-status): decide OpenCode peer records from the root app
---------
Co-authored-by: Eng. Mahmoud Bek ElNemer <tt21913@gmail.com>
* fix(orchestration): a worker whose terminal died with Orca can be reopened again
When Orca dies while a terminal worker's follow-up is reopening, restart
recovery proves the worker's terminal exited and retires it, but left the
pane's restored hook row naming the conversation. Agents that report no
process to probe (Grok) then refused every later follow-up as held
elsewhere. Recovery now ends that pane's agent status, as the PTY's own
exit would have.
* fix(orchestration): leave a hook row a newer terminal in the pane owns
Restoring orchestration at startup reconciled terminal workers but not chat
workers' sessions. On a headless server (and orcad) nothing else did, so a
chat worker killed with Orca kept its old lease and read as unverifiable:
its open Dispatch could not be stopped, and mail to it was only filed.
Restoring orchestration now reconciles chat restart leases first, as the
desktop window already does at startup, so the worker reads as exited and
behaves as one whose process died while Orca ran.
* fix(orchestration): say the pairing is gone when a worker's server was removed
worker-show, stop and release on a Dispatch from an earlier pairing failed
with the environment store's raw "Unknown environment: <id>". Resolving the
server a worker is pinned to now answers peer_changed with a message that
the saved environment was removed or re-paired, as it already does when the
same environment names a different server.
* fix(orchestration): map only a missing environment to peer_changed
* fix(codex): keep the reset time when a usage limit rejects before the report reaches 100%
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(codex): read the usage-limit error code from the renamed error info
* fix(codex): skip windows that already reset when blaming a nearly spent one
---------
Co-authored-by: moncha3 <moncha3@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Claude records a prompt it absorbs mid-turn only as a queued_command
attachment whose images are inline base64 with no path. The decoder
dropped those images, so an image-only send had no transcript row to
match and its pending bubble stayed at the bottom of the chat.
Decode queued inline images as data URLs. Pathless image-only rows
cannot name their send, so each retires one delivered image-only send
after its boundary, oldest first, and pruning hands the claimed row to
the remaining sends so none reuses it. Failed or uncertain writes never
claim one. Keep inline image bytes out of handoff and worker text.
Co-authored-by: Xulin Wu <wuxulin@bytedance.com>
* feat(appearance): let app chrome follow the terminal theme
Add an "App Chrome Appearance" setting (Default / Match Terminal) next to
Left Sidebar Appearance. In match-terminal mode the terminal theme's
background/foreground are written as document-root CSS variables
(--bg-titlebar, --background/--card/--popover/..., both sidebar token
families), so the tab strip, status bar, side panels, full-page views and
popovers all follow the terminal instead of the app theme. Left-sidebar
modes still win because they scope their own variables below the root.
The terminal color pair and token derivation move into
terminal-surface-colors.ts and are shared with the sidebar resolver.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* feat(status-bar): configurable usage format template
Add Settings → Appearance → Status Bar → "Usage format": a template that
replaces the built-in per-provider usage text when non-empty. Placeholders
cover {provider}, {plan}, the 5h/7d/fable/30d windows as percentages
(following Used/Remaining), {x.reset} countdowns, {x.resetAt} clock times
and Gemini {buckets}; "[...]" groups drop out when a placeholder inside is
empty so one template works across providers with different windows.
Whitespace is rendered as authored (whitespace-pre).
Persisted as PersistedUIState.statusBarUsageFormat with a byProvider
override map reserved for later; the RPC UI-update schema gains the
optional field.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* chore(appearance): document touched functions; surface usage format in search
Add one-line JSDoc to every function this branch adds or edits so the
review docstring gate passes. Include the usage-format entry in the
Status Bar section's search match so searching "template" or
"placeholder" no longer hides the parent row, and mention popovers in
the App Chrome Appearance descriptions since the setting styles them.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* feat(appearance): let file editors follow the terminal theme in match-terminal mode
With App Chrome Appearance = Match Terminal, the tab strip, status bar and
side panels took the terminal palette but every file pane kept the stock app
theme: Monaco (code, plain text, diffs, notebooks, markdown source) was
hard-wired to `vs`/`vs-dark`, and the markdown preview / rich editor painted
the fixed `--editor-surface` with GitHub-colored hljs tokens.
- `terminal-editor-palette.ts` derives an editor palette from the active
terminal theme (background/foreground/cursor/selection + syntax roles mapped
onto the ANSI slots) and builds a Monaco theme (`orca-terminal`) from it;
light/dark is rated by the terminal background, so a light terminal theme
under a dark OS setting still gets light styling.
- match-terminal chrome variables now include `--editor-surface` and
`--syntax-*`; the hljs stylesheets read those ahead of their defaults.
- `useEditorSurfaceAppearance` / `useMonacoEditorTheme` replace the inline
`isDark ? 'vs-dark' : 'vs'` computations; the diff-section chain passes the
Monaco theme name instead of a dark flag.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VbWbChctXeMvaR2zdbFY99
(cherry picked from commit dc85fadee0a2664adbf55a49dd3c97c9b10fc111)
* fix(status-bar): honor the usage template in compact usage mode
ProviderSegment only rendered a user template on the verbose branch, so
switching usage mode to compact silently fell back to the built-in
tightest-window label. A non-empty template now replaces the built-in
text in both modes; the mini bar stays verbose-only.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VbWbChctXeMvaR2zdbFY99
* docs(appearance): document remaining functions touched by the diff
Adds one-line JSDoc to the editor surfaces, diff viewers, palette helpers
and UI-slice entry points this branch modifies so the diff's docstring
coverage clears the pre-merge threshold.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VbWbChctXeMvaR2zdbFY99
* fix(editor): keep Monaco theme registration and preview clock out of render
The upgraded oxlint React rules flag reassigning a module variable during
render and calling Date.now() inside useMemo. Move the terminal Monaco
theme's signature cache into ensureTerminalMonacoTheme() and pin the
usage-format preview clock with a lazy useState initializer.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VbWbChctXeMvaR2zdbFY99
* localization: complete Brazilian Portuguese catalogs
* fix(i18n): localize remaining hard-coded UI copy and complete Simplified Chinese coverage
Route the English literals and shared English labels that ignored the UI
language through the existing catalog: host labels, plugin cards and consent,
CLI and SSH errors, the checks pill, browser profile labels, shortcut groups,
app and context menus, and the macOS computer-use permission window. Shared
labels are translated where they render, so src/shared stays English for
mobile, CLI and older paired hosts.
- en.json gains 314 keys bootstrapped from inline fallbacks; four duplicate
"Unassigned" keys collapse into translateUnassignedLabel()
- zh gains 337 entries and refreshes existing ones; the other nine locales get
the newly extracted keys
- joinSentences ends a CJK sentence that has no final stop with 。 before the
next one
- the desktop caller passes the computer-use helper its locale; orcad and the
CLI stay Electron-free
- three files the copy pushed past max-lines each shed a focused module
* test: expect labeled roles in the editable context menu
The edit menu now passes explicit Cut, Copy and Select All labels so the roles render in the UI language; the upstream template assertion still expected bare roles.
* fix(i18n): key translated memos on the UI language without bare void reads
Upstream's React Compiler ratchet rejects `void language;`, which the compiler drops, and treats a react-hooks lint suppression as a bailout. The two host-label hooks now pass the language through readUiLanguageMemoInput so it stays a real memo input. ContextualTourOverlay drops its language key: getContextualTour is a static lookup, and step copy is localized at render.
* fix(i18n): translate editor theme settings
* Fix reactive localization and catalog extraction
* Fix combined localization validation
* Localize nested import failures and refine catalogs
* Handle older nested import responses
* Fix localized merge prompts and quota windows
* Address localization and runtime review feedback
* Keep host search and configuration examples usable
* Preserve configured names in add-project host selector
* Preserve host label origins across views
* Use localized fallback for missing local host
* Preserve custom names and refresh localized host labels
* Refresh task host labels without repeating searches
* Preserve Portuguese mobile tab translations
* Address localization review feedback
* fix(status-bar): import window visibility interval from its new path (#40951)
---------
Co-authored-by: lisi <lisi.see@bytedance.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: marlico77 <marlonssoficial@gmail.com>
Co-authored-by: x-Ai <5061489+x-Ai@users.noreply.github.com>
Co-authored-by: Kelvin Amoaba <97001695+AmoabaKelvin@users.noreply.github.com>
* test(ephemeral-vm): make VM runtime store suites pass on Windows
Drop the process.platform=linux stubs (they made secure writes fsync a
read-only handle, EPERM on Windows, and spawned recipes POSIX-style) and
remove temp dirs through one allSettled removeTree helper so Windows ACL
work cannot fail teardown with EBUSY.
* test: restore the rmSync import dropped by the merge from main
* fix(recipes): warn which credentials recipe scripts inherit, add opt-in passEnv allowlist
Recipe lifecycle scripts run locally with Orca's full environment. Keep that
default (provider CLIs and git auth rely on it) but name the credential-like
variables in Settings and let a recipe opt into passEnv so only listed
variables plus a safe base set reach its scripts.
* fix(recipes): fail closed on a malformed passEnv instead of dropping the recipe
Dropping the recipe let a stored snapshot or a same-id plugin recipe run with
the full environment. Keep it with an empty allowlist and a diagnostic, match
base variable names exactly outside Windows, and make the warning copy apply
to any recipe source.
* fix(recipes): import user-agent-platform from its new app-shell location
* fix(activity): keep stale monitoring panes visible
* fix(activity): prioritize stale state over old previews
* fix(activity): share the card's row state so any stale live-PTY pane stays listed
The monitoring-only fallback missed stale foreground working panes, which also
vanished from Activity while the card showed No recent update. Activity and the
card now resolve state through one resolveAgentRowState.
* fix(activity): keep stale blocked panes as attention and unverifiable rows out of running work
---------
Co-authored-by: QiongyinZhang <53255639+qioyaz@users.noreply.github.com>
* fix(automations): don't start or time out runs across system sleep
- Agent startup ceiling now measures on an awake clock that excludes
suspend->resume intervals, so a Mac that sleeps mid-start no longer
expires the start (outcome "ceiling") the moment it wakes.
- Scheduled runs (incl. missed-run catch-up) wait until the system is not
suspended and has been awake 2 min since its last wake, so a macOS dark
wake no longer starts a run that the next sleep cuts off. A wall-clock
jump the monotonic clock did not see also counts as a wake.
- Chat automation runs whose prompt was rejected because the agent never
started now say so instead of "could not confirm this run's prompt".
* fix(automations): detect sleep without trusting the monotonic counter
- The awake clock no longer assumes performance.now stops in sleep: on
macOS (mach_continuous_time) and Windows (QPC) Node's counter counts it.
It now samples itself on a 20s one-shot heartbeat while in use and treats
a 60s+ gap between samples (counter or wall) as a stretch the process did
not run, so orcad, which has no power events, still sees dark wakes, and
a late resume can't clear a suspension early.
- The settle window and startup ceiling measure monotonic elapsed time, so
a backward wall-clock correction no longer extends them.
- An occurrence the wake gate holds while still inside its grace stays
eligible on the settled tick, so the gate's own delay can't turn a run
into skipped_missed (e.g. zero-grace 09:00 run, wake at 09:00:01).
- Tests cover both counter models, run a scheduler tick inside the dark
wake, and drive the startup ceiling through the production default clock.
* fix(automations): revoke wake holds on edits and idle the clock when unused
- A wake-gate hold is now bound to the definition it was granted under
(updatedAt plus schedule, grace, enabled and missed-run policy), so a
grace change, or a pause and re-enable while the gate is closed, falls
back to the current definition's grace instead of dispatching an
occurrence the user no longer allows. An unchanged occurrence still
stays eligible across repeated short wakes.
- The scheduler no longer reads the awake clock while no automation is
enabled, so the clock's heartbeat idles out instead of firing three
times a minute for the life of the process; the next tick after one is
enabled restarts it.
* fix(automations): bind wake holds to eligibility, not run bookkeeping
- A wake-gate hold no longer includes the automation's updatedAt, which
run completion, usage and terminal-retention writes move on an
unchanged definition. A zero-grace occurrence held at 09:01:01 now
still dispatches when an earlier run completes during the hold,
instead of becoming skipped_missed.
- The hold is bound to the fields that decide eligibility (schedule,
timezone, grace, missed-run policy, enabled) plus an in-memory count
of pause/re-enable transitions kept by the store, so a pause and
re-enable still revokes it, even one in the same millisecond that
restores every field. A rename keeps the hold.
* test(automations): align startup-clock tests with the awake clock
- The Codex start-deadline test now fakes performance alongside Date
and gives each test its own awake clock. The ceiling runs on the
awake clock, which read real performance and, as a process-wide
singleton, lost its fake heartbeat at useRealTimers, so the second
test's ten-minute jump read as a sleep and never expired the start.
- The coordinator-mail observation clock gives each fake-time window
its own production awake clock and counts that clock's heartbeat, so
the closed-database drain still requires every other timer to end
instead of failing on the heartbeat, depending on which test created
the shared clock first.
* test(automations): express wake-settle times in local time so CI's UTC passes
The scheduler reads BYHOUR in process-local time; the Pacific offsets only
matched on a Pacific machine.
New profiles default artifactSharingEnabled to true. Existing users are
unchanged: stored settings win over defaults on load, and a stored profile
saved before the key existed loads as false instead of inheriting the new
default. The gate still requires an explicit true, sign-in is still
required, and web clients still mirror the host (their local fallback no
longer inherits the desktop default). showArtifactsButton is unchanged.
* fix(github): show Actions jobs as checks when a token cannot read check runs
A fine-grained personal access token cannot be granted the Checks
permission, so GitHub refuses every check-run read and the checks panel
failed with 'Resource not accessible by personal access token'. When the
REST check-run read is refused that way, the fallback now lists the head
commit's GitHub Actions jobs (Actions: read) in their place; a job's id is
its check run's id, so job logs keep working.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(github): read Actions jobs in the shared REST check pages
Moves the fine-grained token fallback into readRestPRCheckRuns and
readRestPRCheckSuites so it reuses the existing pagination and also
covers the CI summary and PR watch reads. Check details skip the
refused check-run read and still load the workflow jobs and logs.
* fix(github): read refused check details from the Actions job
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Kelvin Amoaba <97001695+AmoabaKelvin@users.noreply.github.com>
* fix(settings): list the host's models in agent settings
Settings read the built-in model list, so new Codex models never appeared.
It now reads agentSession.modelCatalog when an agent's row is open.
Fixes#38643
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(settings): mark the built-in model list and keep new-chat defaults out
Say when Settings shows the built-in list because the host gave none.
Read the host's answer through the snapshot, which drops a listed default
that a workspace's own config could replace.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(settings): show Codex's account models and don't trust an old list
A Codex account answer is scoped by workspace, so reading it through the
new-chat snapshot brought back the built-in list. Use the answer directly.
A failed read now shows the marked built-in list, not an older answer.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(settings): build the older model list without a type assertion
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(settings): read the model list again when the agent command or account changes
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(settings): build the changed settings without a type assertion
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(settings): assert the shown models instead of the read count
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(settings): restore the store settings after each model list test
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(settings): refresh the model list when a host drops its lists
A paired host can change account on reconnect with no setting changing here,
so an open row kept the old list until it was reopened.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(settings): follow the moved native-chat runtime modules
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(settings): show the built-in list note only when there is a built-in list
* fix(settings): keep the Settings model list current while a host is still listing
Wait again when a host listing outlasts one wait, re-read when a paired host's launch
settings change, and stop writing the account answer into the new-chat snapshot, where
it dropped newer workspace answers.
* fix(settings): ask paired hosts to wait only after they report a running listing
Older hosts refuse waitForListing, so the first read is plain, the same order the new-chat
picker uses. A paired host's settings change re-reads without hiding the list shown.
* refactor(settings): read the host catalog without a hooks-rule suppression
---------
Co-authored-by: temp_final_v5 <>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Kelvin Amoaba <97001695+AmoabaKelvin@users.noreply.github.com>