* fix(claude): preserve profile-owned state during configuration refresh
* test(claude): bound profile state publications at workspace scale
* fix(claude): honor profile API approval before shared rejection
* fix(git-graph): keep loading commits while the end of history is in view
Git Graph only asked for the next page from a scroll event, so a pane
taller than the first 50 commits (or one enlarged later) had no scrollbar
and never loaded older history. The next page is now requested whenever
the end of the loaded rows is within the visible range, once per loaded
result; a failed page waits for Load more or Refresh, and a page that adds
no commits keeps the previous result so it cannot repeat.
Tracked in STA-14490.
* fix(git-graph): keep viewport paging's once-per-result latch across remounts without retaining old history
* fix(git-graph): page only the result whose rows were measured in view
* test(git-graph): replaced history is released while the pane stays mounted
Native chat strips pane env, so Orca's Codex hooks only spawn a shell per
event. On Windows with Store PowerShell first on PATH, Codex fails every
command-hook spawn with os error 5 (openai/codex#47810), which native chat
showed after each tool call. Disable just Orca's hooks.json entries for the
app-server launch with a session -c hooks.state override; user hooks keep
running.
* fix(native-chat): list Codex models in the chat's folder when its command line needs that folder
A Codex command such as `node node_modules/@openai/codex/bin/codex.js` failed from Orca's empty probe folder, so the picker fell back to the built-in list. Like Claude's probe, a command line that may name files relative to the chat's folder now lists there, with that folder untrusted so its project config never changes the account's list.
* fix(native-chat): untrust the lowercased folder key Windows Codex looks up first
* fix(acp): retry transient -32603 during session model catalog probes
opencode answers ACP session/new with a transient -32603 while its
providers still open, and a single probe failure degraded the chat model
picker to one pinned model. Retry initialize and session/new up to
3 times with abort-aware backoff, mirroring the existing sweep retry.
* fix(acp): address CodeRabbit review on transient retry
Re-check operation currency after the backoff sleep so a cancelled or
rotated probe never issues another request, cap retries at three
attempts total (two backoffs), document the helpers, and cover the
abort-during-backoff case with a test.
* fix(acp): retry only OpenCode's session/new and use the abortable timer
* test(acp): list OpenCode's catalog after a -32603 session/new
---------
Co-authored-by: Mazurov Anton <anton.mazurov@reksoft.com>
* relay: renew the relay token right after wake when it fell due during sleep
Node timers stop while the machine sleeps, so a renewal due during a sleep fired that much later
after wake, after the token's wall-clock expiry. With the host-sent keepalive the control survives
the sleep, so the relay closed the live control 4401 a few minutes after wake (cutting any phone
session started since). The renewal and its retries now use a wall-clock timer that runs a due
task on system resume.
* relay: re-arm the renewal from the wall clock on a resume before it is due
A sleep that ends before the renewal is due still cost the timer clock the whole sleep, so the
renewal fired that much late. On resume a task not yet due is re-armed for the wall-clock time left.
The settled-turn fold kept only the last prose row, so a completed Codex image generation folded behind the final answer. Mark generated-image rows and keep them out of the fold, like plans and turn notices.
* fix(codex): take Codex's idle report as its live composer so handoffs reach a blank status line
* fix(codex): drop the idle verdict when Codex reports blocked, error or clear
The profile request now carries the caller's refresh token alongside the
access token, so the server can require proof of the long-lived sign-in
before issuing the new profile's session. Servers that do not expect the
field ignore it.
* fix(cloud-auth): keep users signed in through transient auth errors
Only the auth server's JSON 401 invalid_refresh_token verdict now ends a
desktop sign-in. 403s, HTML or other non-JSON answers, other 401 codes,
5xx, 429, timeouts and network errors keep the session and retry later.
An unanswered refresh is now retried once within the server's rotation
grace (20s timeout, 10s pause, one retry) instead of replaying the token
90s later, when the server treats it as reuse.
A wrapped request that still answers 401 right after a successful refresh
returns its error instead of discarding the session the server just
accepted.
* fix(cloud-auth): refresh only on a 401, at most once per backoff window
A 403 from a signed request is a permission answer, so it no longer
spends a refresh-token rotation. A request that keeps answering 401
forces at most one refresh per session every 5 minutes; concurrent
rejections join the refresh already in flight or reuse a newer token,
and later ones return their 401.
* feat(cli): read and message agent chats with orca chat list/read/send
Carried over from #33115 (squashed onto current main; conflicts with chat rename resolved).
* feat(cli): wait for a chat to settle, read text from stdin, refuse paired hosts
chat send --wait and chat wait poll the history's working flag until the
chat is idle or waits on a question, keeping a queued message pending until
it runs. chat read is one history fetch and returns a cursor. Unattached
and paired-host refusals say what they mean.
* fix(cli): settle a held queued message, skip subagent rows, resolve chat list --worktree
* fix(cli): show chat errors, keep waiting through queue handoffs, return the whole settled turn
* fix(cli): settle any queued message the host will not send, show grouped questions and only answerable prompts
* test(cli): drive chat tests through a real client and fake timers
* fix(cli): describe chat --session, --wait and --state in command help
* fix(cli): report chat wait in chat list's states, reject unknown --state, flag truncated reads
* docs(cli): say chat wait settles on the chat's own turn; no truncated flag on held
* fix(cli): chat rename help asks for a session id, not a handle
---------
Co-authored-by: YangNuoCheng <42427439+YangNuoCheng@users.noreply.github.com>
Prints the notes the user left on a browser tab and has not sent, the same text the tab's Copy button gives (--json returns them). Reads the saved session, so it works for closed-and-restored tabs; SSH hosts reach it through the desktop browser bridge. A page drawn by a paired desktop reports that its notes stay there.
#40249 narrowed Settings to 784px, which left the default-surface section
below its two-column breakpoint (tiles always stacked) and squeezed shortcut
names to a few characters beside their badges.
* fix(mobile): serve the phone page from a Linux install updated in place
Package managers (pacman, apt, dnf) replace Orca's files while the old
process keeps running. The host cached the manifest for the life of the
process and read assets through Electron's launch-time asar header, so
every read of the replaced files failed with asset_changed until Orca
restarted. Read from app.asar.unpacked and re-read the manifest when
manifest.json changes on disk.
Fixes STA-14385
* fix(mobile): check the page manifest off the main thread, and retry a mismatch
Read and stat the manifest with fs/promises and keep the probed root, so
bundle RPCs add no sync file calls. Keep only passing hash verdicts: a
package install writes files one at a time, so a mismatch may clear.
* fix(mobile): key the page manifest cache on its bytes
Inode, size and mtime can all repeat when ext4 rewrites a same-length
manifest within one clock tick.
* fix(mobile): read a newer in-place install's page manifest
A release written in place may add schema-v1 manifest fields the running
host predates. Read it with a stripping schema so the host serves the
fields it supports instead of reporting no bundle until restart.
* refactor(mobile): derive the installed-manifest reader from the writer's shapes
* wip(folder-sc): card header cleanup and Remove from Parent in card menu
Work in progress handed to a Codex session; see ~/orca-qa/folder-sc-card/handoff-codex.md.
* test(source-control): cover collapsed folder card identity
* Keep folder card controls usable while status is unavailable
* Retain branch before card body mounts and allow conflict rows to grow
* Preserve source control label size and folder card parent actions
* fix(browser): keep unsent page notes across restarts and ask before closing a tab that has them
Unsent browser notes lived only in the renderer store and hydration reset them, so a reload, restart or tab close lost them. Each saved browser page now carries its unsent notes, hydration restores them, and every close path (tab strip, keyboard, CLI, phone) asks before discarding them. A page script's window.close() can't discard them.
* fix(browser): keep tabs with unsent notes open on bulk close, like pinned tabs
* feat(orchestration): a paired Orca as a Run's coordinator on the server it placed work on (inert)
The server half of remote-owned workers. A paired Orca's call names one of its
Runs; the server admits it as a peer caller kind, writes that Run at frame
receipt, and holds it to the one access check. Its workers' mail and state
queue home under a sequence no reset reuses. Nothing sends the envelope until
the coordinator side ships, so this changes nothing today.
* fix(orchestration): reserve the peer address, keep conversation kinds apart, queue a correction once with its result
* fix(orchestration): hold back a corrected Task's change whatever its latest attempt; rotate pulls in a stable order per database
* chore(orchestration): typed field read, cast rationales, a wake test on fake timers
* fix(orchestration): a peer's receipts per conversation, its sends only into its Run, a page that fits every conversation, pending adopted Tasks keep their gate
* fix(orchestration): a peer's follow-up places where its worker ran
* fix(orchestration): a peer's current/new-child start gets the --on placement refusal
* fix(browser): hold a page drawable until its capture settles
A stalled capture stays pending until the page draws and keeps macOS display
sleep off ("Capturing"); dropping the paint hold at our timeout left it there.
Fixes#24946
* fix(browser): keep the debugger attached while a CDP capture is pending
* refactor(browser): share one settle-scoped hold helper for paint and debugger leases
* fix(editor): keep Mermaid labels readable on pastel dark theme palettes
In dark mode the Mermaid config fills nodes, actors and boxes with the
theme's --chart-3/4/5 tokens while every label uses --foreground. Themes
with pastel chart tokens (e.g. Catppuccin Mocha) put light text on light
fills, so sequence actors, class boxes and similar shapes became
unreadable (contrast ~1.06:1). The flowchart contrast pass only covers
flowcharts.
Tint each palette fill toward the background just until the foreground
reaches WCAG 4.5:1. Palettes that already read (Orca's default dark
blues) are unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(editor): tint only Mermaid fills under foreground labels
Darkening the palette seeds also darkened the git graph branch boxes and
venn colours, which Mermaid pairs with its own label colours, and the
active Gantt border. Keep the seeds and tint mainBkg, clusterBkg,
requirementBackground and the Gantt task fills instead.
* fix(editor): pin Mermaid fills only when the theme colour needs tinting
An always-set mainBkg overrode a diagram's own primaryColor in every dark
theme. Pin the tinted fills only when the chart colour fails, and cover
git tag pills too.
* refactor(editor): reuse readableOn for Mermaid fill contrast
Drop the hand-rolled hex mix loop and the extra luminance exports; move
hexToRgb next to rgbaToHex so terminal appearance and Mermaid share it.
* fix(editor): draw clickable Mermaid Gantt labels in the foreground colour
Mermaid's default dark-blue clickable label reads only on light bars; on
tinted or dark bars, and beside a bar on a dark page, it disappears.
* fix(editor): tint Mermaid railroad terminal and comment fills too
---------
Co-authored-by: Pro100v <2681328+Pro100v@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
`orca agent launch --focus` and `worktree create --agent --activate` left a
chat launch unselected: main marked the chat active only in its tab listing,
which the window follows solely on its own focus intent (#5435). Send the
existing focusEditorTab for that chat; when its tab is not listed yet, record
the focus intent so the listing selects it unless the user moved on.
Co-authored-by: Manuel Meurer <manuel@meurer.io>
The image wrapper was inline-block, so it sized itself from the image's
natural width. An SVG with a viewBox but no absolute width has none, so
the wrapper and the image collapsed to 0x0. Keep the wrapper inline so
the image sizes against the paragraph, as it does in the preview.
* fix(agent-status): accept OpenCode 2 hooks after OSC reports opencode
OpenCode 2's OSC app id is opencode, so the status plugin's opencode2 prompt was treated as a nested CLI and dropped. Branch rename never saw the first prompt. A different OpenCode process still does not own the pane.
* fix(agent-status): keep OpenCode 2 on rows its OSC 7501 calls opencode
OSC 7501 names every OpenCode `opencode`, so after an OpenCode 2 turn ended
its OSC idle relabeled the row and dropped the session it resumes from.
Read the OSC claim as the OpenCode 2 row's generation, and replace the
identity unit tests with one server test of the real report order.
---------
Co-authored-by: Kelvin Amoaba <97001695+AmoabaKelvin@users.noreply.github.com>
* Cache orchestration source facts by dispatch and address
* Declare keyed projection services and use lifecycle transaction in regression
* Keep empty orchestration reads lightweight without hiding inserts
* Preserve pane selection and bound unattended projection invalidations
* Use persisted lifecycle inputs in projection regression scenarios
* Own exact completion eligibility at the SQLite source
* Keep public status source fixture deterministic
* Coalesce pane candidates and preserve source refresh ownership
* Align projection fixtures and annotations with static checks
* Remove obsolete identity implementation-count comparison
* Expand each addressed terminal family once per snapshot
* Maintain addressed dispatch winners in source order indexes
* Keep terminal identity rows separate from public orchestration status
* Match optional public status reader to constructor dependency
* Complete orchestration status and fixture database contracts
* Retire terminal notices and pending discard state with their lifetime
* Preserve the DOM window in terminal notice lifecycle fixtures
* test: exercise fresh terminal eligibility and stale edit output
* Release notice contributions at accepted terminal retirement
* Keep terminal notice delivery independent of store initialization
* Assert the public workspace removal failure result
* Keep buffered terminal retirement within delivery modules
* Initialize canonical terminal maps in workspace slice fixtures
* Expose terminal lifecycle fixture actions after commit
* fix(linear): reject connections that omit pagination evidence
A list or activity page without a boolean hasNextPage was reported as a finished read. Callers that stop when hasMore is false then treated a dropped page as the full set. Fail that page with linear_partial instead.
* fix(linear): require pagination evidence in every Linear list walker
The desktop issue list, orca linear list, project and custom view issue
lists, project, custom view and project team lists still read a missing
pageInfo as the last page. Route them through the same check, and drop
tests that pass without the fix.
---------
Co-authored-by: Kelvin Amoaba <97001695+AmoabaKelvin@users.noreply.github.com>
* feat(workspaces): run setup and archive scripts for folder projects
Folder projects get the setup and archive scripts git projects have:
creating a workspace runs setup in a Setup tab, and removing one runs
archive first. The script sees the workspace's name and id, so
`orca worktree create` inside it attaches each new worktree to that
workspace, however the workspace was created.
- Folder creates (desktop IPC and runtime) prepare setup through the
shared setup prep; runtime creates start it with the worktree terminal
startup, so Setup-before-agent ordering matches.
- Runner files live in <folder>/.orca, one fresh file per launch, removed
with the workspace.
- Only the host whose catalog holds the folder reads its orca.yaml or runs
its scripts; a setup problem becomes a warning, never a failed create.
- Shared orca.yaml setup with no approval from an older client is skipped;
ask/inherit never refuses a folder create.
- No orca.yaml default tabs for folders, since every workspace shares the
directory.
- New capability worktree.folder-setup.v1 gates the Settings section on
runtime hosts; the composer, Settings and trust prompt reuse the
existing setup surfaces.
* i18n: add folder workspace hooks strings
* chore: drop the runner's sync-fs baseline and an array cast
* fix(workspaces): close review gaps in folder project setup
- Whole-project trust sends an explicit run for folder creates the
policy would run, since it carries no content hash.
- Folder setup skips file access for a skipped setup and never starts a
stopped WSL distro for a create nobody started; removal does the same.
- Runtime folder creates return the trust mismatch, so the window re-asks.
- The composer hides folder setup controls on hosts without
worktree.folder-setup.v1 and keeps their old explicit skip.
- Hook checks read a folder only on the host that owns it.
- Git archive hooks get the removed workspace's id; WSL hooks blank
inherited pane identity too.
- Runner files are written through the drive path WSL needs for its
drive mounts, and kept out of git status with .orca/.gitignore.
- The CLI's older-host warning covers --agent creates and --json output.
* fix(workspaces): wait for the folder setup capability and read orca.yaml once
Create now waits for a runtime host's folder-setup answer instead of
sending Skip while the probe is pending, and runtime setup reuses the
parsed orca.yaml when merging effective hooks.
* fix(workspaces): keep a failed folder setup probe unknown and retry it on create
* fix(workspaces): share folder setup capability answers with the composer
* fix(workspaces): re-ask the host for folder setup support on every create
* fix(settings): read orca.yaml for folder projects and use workspace copy in hook rows
QA found Settings reporting no orca.yaml for folder projects while the
composer ran that script, and the inner hook rows still said worktree.
* fix(folder-workspaces): open one Setup tab for an instant folder create
* fix(workspaces): run setup when a created workspace has only editor tabs
* perf(folder-workspaces): per-workspace runner dir, bounded setup answers, one archive config read
* fix(folder-workspaces): retain setup capability for active consumers
* fix(folder-workspaces): match hook search to workspace descriptions
* fix(i18n): drop obsolete hook search descriptions
* test(folder-workspaces): follow relocated setup trust modules
* refactor: finish terminal and Mobile defining-owner imports
* fix: retain completion coordinator type binding
* refactor: consolidate direct terminal tree imports
* refactor(renderer): import typography from defining owners
* refactor(renderer): group file and document feature owners
* refactor(renderer): remove orphaned editor recovery registration suite
* refactor(renderer): colocate file explorer tree result contract
* feat(plugins): add editor.readTypography and editor.typography.changed
Plugins that render code next to Orca's editor had to open the private
profile database and reimplement Orca's font rules to match it. Host API 1.6
adds editor.readTypography (no capability; worker, panel and editor frames):
the font family and CSS stack, size with editor zoom, weight, line height in
px, ligatures, word wrap and minimap that the file editor resolves now.
editor.typography.changed carries the same values after a settings write or
an editor zoom changes them; it is the first event that needs no capability.
The pure resolution (editor typography, editor zoom, monospace font stack)
moves to src/shared so main and the renderer use one implementation.
* fix(plugins): keep editor typography resolution from throwing in main
A hand-edited profile with a non-string font family made the shared resolver
throw, which the main-process watcher would surface at startup and on every
settings write. Font values are now type-checked, the watcher catches and
logs, and it reads live settings so a write without listeners cannot leave the
event payload stale. Over-long font families are cut to the schema bound
instead of failing every read. Regenerates the testing runtime.
* fix(terminal): keep remote-viewer clipboard env on command-less creates (#39852)
A paired viewer's plain terminal reaches the host renderer's tab-create
bridge with spawn env (ORCA_REMOTE_VIEWER_CLIPBOARD, PI_CLIPBOARD_OSC52)
but no startup command. The bridge queued pendingStartup only when a
command existed, dropping the env, so the spawned shell never saw the
remote-viewer clipboard marker and copied text stayed on the host
clipboard (#39852).
- Queue the startup whenever the request carries launch material
(env/envToDelete/launchConfig/resume), not only a command.
- PtyPaneStartup.command becomes optional for env-only startups; spawn
options already tolerate a missing command.
- Keep the plain-shell pre-bind input hold for startups that plan no
post-bind work, so an env-only startup types as a plain shell does.
Co-Authored-By: Claude Code <noreply@anthropic.com>
* test(e2e): layout oracle marks only panes the user can see
A hidden tab with a queued startup is laid out at opacity 0 so it spawns at
real geometry. The marker check counted it as visible because it has a size,
then waited for output that the hidden-delivery gate correctly withholds.
Paired-client creates now queue spawn env, so their background tabs hit this.
---------
Co-authored-by: Chen <zwq19980411@gmail.com>
Co-authored-by: Claude Code <noreply@anthropic.com>
* test(ssh): isolate connection manager session holds
* test(ssh): reset both session-hold stores in the shared SSH connection fixture
The fixture reset now clears credential declines as well as user disconnects,
so every suite built on it starts without a stale hold from an earlier file in
the same worker. The per-suite resets it supersedes are removed.
Fixes#40291
---------
Co-authored-by: Vyacheslav Scherbinin <gentslava@mail.ru>