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.
* relay edge: a keepalive host already silent when its authorization expires closes 4408
At token exp + 60 s, a keepalive control that went silent (asleep, offline) had its silence probe
pending, so the expiry check closed it 4401. Production showed these as 4401 'never refreshed'
closes with the host silent for ~5-6 minutes, inflating the auth-failure count and hiding drops
from the 4408 comparison with the cells. Such a host now closes 4408 (orphan time back-dated as
for any silence close). Local e2e K4 (fails without the change: 4401). 48/48.
* relay edge: handshake time on control_active, control age and silence on dead-control closes
At 1%, many new controls went silent at or right after activation and were closed minutes later,
with no rebound from a retry. To tell a desktop that gave up the connect (15 s deadline, e.g. a
slow first hello on a new object) from one that died later: control_active double2 = ms from the
upgrade to activation; new silence_close (seconds silent, where found, keepalive/legacy, age);
auth_expired_close double3 = control age.
* Fix workspace delete shortcut targeting
Resolve the keyboard action from the current workspace and execution host,
keep clicked menu actions bound to their rows, and advertise the shortcut
only for the committed workspace copy. Preserve confirmation preferences.
Co-authored-by: Luca Critelli <lucacri@gmail.com>
Co-authored-by: Anton Kuligin <anton.kuligin@notraffic.tech>
* Document isolated deletion test fixture boundaries
* Type the shortcut command test input
---------
Co-authored-by: Luca Critelli <lucacri@gmail.com>
Co-authored-by: Anton Kuligin <anton.kuligin@notraffic.tech>
Native chat (agent-session) tabs project Claude status entries into
agentStatusByPaneKey, which made the terminal-agent presence check fire
the Claude Code theme-sync offer without the CLI ever being launched.
Status entries now count only when their pane belongs to a terminal tab.
* fix(native-chat): show the page a browser run drove, not another chat's
* fix(browser): run each queued agent command in its own RPC call
* fix(native-chat): once a chat claims its browser activity, ignore unclaimed activity
* fix(mobile): tell Android users which WebView to update when it is too old
The page shell needs androidx's DOCUMENT_START_SCRIPT:1, which stable
WebView only reports from Chromium 101; the comments claimed 83/88.
Name the required WebView and the one installed, and how to switch it.
* fix(mobile): read the WebView provider through the shell module index
Tests stub the module index; a direct file import loaded expo-modules-core unstubbed.
* 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
The assign path judges edge cohort membership with the region the desktop asks for; the sweep used
the stored region preference, which can miss or lag it. A host whose two disagreed was placed on the
edge, drained by the sweep, and placed back on its next ask: at 1% this drained 12 of ~31 moved
hosts within 10 minutes, and each director would repeat it every cooldown. The sweep now ignores
region scope (it still drains hosts that left the cohort by mode, deny or share); a host that asks
for a region outside the scope leaves on that ask.
* 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>
* fix(mobile): save the downloaded desktop page on Android 7
Below API 26, expo-file-system 55 moves a directory with File.copyTo, which
creates an empty directory, so committing a downloaded page build always
failed with cache-write-failed. Copy the tree recursively and delete the
source there instead.
* fix(mobile): remove a partial copy when an Android 7 page move fails
Desktop closes for expired relay authorization rose after the keepalive release (3/day to ~35/day
on the edge cohort). The close metric now carries whether the control took the keepalive offer and
how long the host had been silent, and control_active carries keepalive use, so the cause can be
told apart (stalled desktop timers vs a control whose refresh stopped while it stayed live).
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