* Keep review note changes on their captured workspace owner
* Keep review note actions on the copy whose notes are shown
Review notes now read their owner and their notes together, so an action
always changes the copy the user is looking at:
- A paired SSH copy saves through its server even when its row does not
name the server, instead of saving on this computer.
- The Markdown preview shows and edits the selected copy's notes, not the
first copy listed with the same workspace id.
- While the selected copy is not listed yet, no other copy's notes are
shown; a note started then saves to that copy once it lists.
- A listing that stamps the same copy's host no longer looks like a new
copy: a pending Send stays held and unsaved note edits are kept.
- Clear all / Clear file confirmations stay on the copy they opened on
when the selected host changes.
- A copy removed since the user acted reports the existing save or clear
failure once instead of failing silently.
- Mounted note views skip ownership work on store updates that cannot
change it, and do not re-render for another copy's changes.
* Keep review notes on the exact workspace copy each surface shows
Notes, their owner and every note action now come from one copy identity.
Previews and editors of a server's copy read and save that copy, paired
SSH copies keep working through their server, an SSH draft never lands on
a local row, and controls stay disabled instead of claiming "All notes
sent" while a copy's notes are unknown. Open Clear confirmations share the
cached read, so unrelated store writes do no row work.
* Resolve review-note copies through the shared workspace ownership rules
Every listed row now gets its copy from the same rules the app routes
writes with, including server provenance from detected listings and the
SSH place behind a paired server for older rows without host stamps.
Previews, editors and diffs read notes from their own tab's provenance
instead of the selected copy, folders honor their source's host, and a
note composer's shortcut captures the copy its surface shows when it
opens.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* Keep folder review notes on the folder copy their source names
A folder's notes now come from the same source rules as worktree notes,
so a file from this app never shows or saves to a server's folder with
the same id. Queued folder saves and rollbacks check the captured folder
copy the same way reads do, and resolving copies no longer rescans the
project list for every row.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* Read review-note copies through the shared id indexes
Folder and worktree note views now read only their own workspace's
catalog entries from the shared indexes, and readers of one folder
share its qualification, so listing updates cost work proportional to
what is shown rather than catalog size times readers. Also fixes the
type errors and the end-to-end note seeds, which now pass the owner of
the worktree they seed.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* Share review-note copy resolution across rows and readers
Rows of one workspace on the same host now share a single ownership
answer per catalog snapshot, so duplicate listings of an SSH worktree
no longer make every note view rescan its peers. Folders that are not
listed return one shared answer instead of leaving cache entries behind.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* Name the catalog snapshots review-note ownership results are shared under
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* Save renamed-file drafts under the new path and encode restored SSH targets
A diff note draft opened before its file was renamed in place now saves
under the file's current path, still on the copy it was opened on. A
restored SSH file whose target id needs encoding now shows and saves its
own copy's notes.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* Update the diff note path ref after render instead of during it
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* Preserve provider failures from manual compaction
* Keep compact self-failures command-owned; attribute quota only to this attempt
An ACP /compact error now uses the ordinary failure row only when the merged
evidence carries a typed usage-limit or sign-in cause; other errors keep the
command's Compaction failed row with the agent's detail, as before.
Claude /compact replies stay hidden but feed their typed provider errors to the
usage-limit evidence, with a sign-in failure as an explicit other cause. Account
rejections count for a failed manual compact only when received during that
command; older ones still supply the window and reset.
* Select compact failures in the command composer; attempt-owned Claude rejections
ACP: the compact composer merges the settlement into the retained evidence and
asks the ordinary failure owner's classification; established provider evidence
(quota, sign-in, or OpenCode's structured provider error names) writes the
ordinary row with a thread-only join, otherwise the command keeps its own
compactionFailed row. The ordinary owner no longer touches compaction state.
Grok's -32003 RPC code now reads as a rate limit.
Claude: rejection types seen while a command runs belong to that attempt and
must still be rejecting; a hidden sign-in reply selects the ordinary sign-in
notice, written once at result time.
* Assert compact failure rows by their encoded item ids
* Keep a compact's 403 access denial in Claude's words, not as sign-in guidance
* Pin the clock in the compact failure tests instead of reading it
* Parse the recorded sign-in fixture instead of casting it
* Allow profile repair to replace damaged automation history metadata
* Keep verified automation history when repairing its placeholder
* Test structural profile open and repair output for kept automation history
Schema verification no longer reads automation history metadata, so the
read-concurrency tests now assert that open succeeds without reading it and
that ordinary reads still keep snapshots consistent and refuse corrupt
metadata. Add output coverage for the recovery-required message, the
startup failure text (English and a translation) and the bundled CLI
recovery route printing kept and backup-restored sections.
* fix(review): reconcile hosted reviews after failed writes
* fix(review): reconcile PR page, phone and Checks after failed writes
- PR page: merge, auto-merge, close/reopen and reviewer changes reread details after every attempted write, and the page's displayed state follows a freshly read details state so buttons reflect what landed.
- Phone: the PR actions engine and title save reread once per attempted write after busy clears; a failed reread never replaces the write's outcome or turns a successful write into an error.
- Checks: a failed merge's error stays visible when the reread shows the review merged; a GitLab reread that settles after the panel switched reviews no longer commits details for the other context.
* fix(review): reconcile GitHub and GitLab item dialogs after failed writes
- GitHub item dialog: merge, auto-merge, close/reopen and reviewer changes reread details after every attempted write, after pending clears and after the close/reopen revert. Success toasts and patches stay success-only.
- GitLab MR dialog: merge, close, reopen, details save and reviewer changes run the dialog's existing refresh after every attempted write. The write's error toast and the user's drafts stay.
* fix(review): keep shown review data and ownership across write rereads
- Phone: a write's follow-up read that fails keeps the PR already shown and the write's own error instead of replacing the panel with a load error. Manual Recheck, Retry and HEAD refreshes still show a failed read.
- Phone: a load started for an earlier branch can no longer claim the current one, and a title write that settles after the view moved to another PR stays silent and skips its reread.
- Phone: an older title Save that finishes late no longer closes a newer edit or hides its failure.
- Checks: the GitLab details read after a write lands only on the review the panel currently shows; an old or fallback MR can no longer take over a replacement MR's checks and comments.
* fix(review): keep loaded item details on screen through rereads
- GitHub item dialog and PR page: when a write's reread (or any other invalidation) drops the cached details, the same item keeps showing its last loaded details while exactly one fresh read runs and if it fails, so the comment composer and its unsent draft stay mounted. A cold first load, a retry with no data and switching items still show loading and errors.
- GitLab MR dialog: the state badge and Merge/Close/Reopen follow the item's freshly read details, falling back to the list row; the Reviewers section stays visible while a reread runs; the load-error banner shows only when there is nothing loaded; switching items drops the previous MR's details before paint.
* fix(review): keep loaded details at their cache and scope GitLab details to the full target
- GitHub item dialog and PR page: invalidation keeps the loaded details in the cache entry, retires its pending read and owes exactly one fresh read, so Viewed, description, reviewer and checks updates keep landing on what is shown, even while that read runs or after it fails. A failed read, an empty result or an optimistic comment does not start another read. Removes the separate retained-details hook.
- GitLab MR dialog: details, reviewer/label options and drafts belong to the full target (task source, GitLab project, item and repo); switching source or instance with the same item id drops the previous target's reviewers and state, and a late result for the old target is ignored.
* fix(review): keep owed and running detail rereads through local field updates
Each GitHub details cache (item dialog and PR page) gets one payload-only patch operation that copies the entry's read ownership (an owed reread and the running read) by construction. Viewed, description, reviewer, checks and the optimistic comment all go through it; read start, settlement and invalidation stay separate. A comment that lands with a write's invalidation no longer cancels the owed reread, and a comment during a running reread no longer lets an unrelated invalidation discard that read. A comment alone still starts no read.
* fix(mobile): reread the PR after every attempted write on main's PR tab
Rebuilds this PR's mobile behavior on main's restructured PR tab:
- Engine and title/description edits reread after every attempted
write once busy/saving clears; the write's outcome is the only
feedback and a failed reread is contained.
- The controller gives writes a dedicated reread entry that a poll
can't skip, keeps the shown PR when the read fails, and retires a
details read started before the write.
- A reread whose checks read failed still shows the PR's new state
(merged/closed), keeping prior checks only for the same review.
- Details carry, dedup and completion key on repo + number, so the
same PR number in another repo doesn't inherit details.
- An older Save can't close a newer edit; a write that settles after
the view moved to another PR shows no error and rereads nothing.
* test: repair CI for the reread tests
- Use a fixed fetchedAt for the unrelated cache entry in the details
hook tests instead of reading the wall clock.
- Mock platform haptics in the mobile controller probe and text action
tests so they don't load react-native, and give the act callbacks
that awaited a load result a Promise<void> body.
* fix(mobile): publish PR details against the latest queued state
Phase-two details spread the last rendered PR data, so when they settled
before phase one rendered (a fast read, or a closed client failing at
once) they restored the PR state the reread had just replaced: a Close
or Merge the host applied still showed open. Details now patch only
their field through a functional update whose identity, sequence and
same-review checks run against the state React applies them to.
* fix: type the reread test fixtures and commit identity refs after render
- Replace type assertions in this PR's tests with typed fixtures; the
GitLab primary-actions test keeps one partial dialog-state cast with a
SAFETY note, as neighbouring hook tests do.
- Assign the mobile controller and text-action identity refs and the
GitLab dialog owner ref in a layout effect, so a render React discards
can't leave an identity that never committed for a late result to
check against.
* fix(github): route the saved-body patch through the details payload helper
Main's issue-body rule (a saved description supersedes a read already
running) now goes through the one field-patch helper, which keeps an
owed reread and copies the running read for every other patch.
* fix(github): replace a read retired by a saved issue description
A saved issue description drops the details read already running so it
can't restore the older body. When that read was an ordinary one (such
as the reread after a write), the dialog now owes one replacement read,
so the new conversation still arrives with the saved body. A Refresh
read keeps relying on its own loop, which already retries a superseded
attempt. Starting the replacement consumes the obligation, and a failed
replacement owes no retry.
* test: fix typecheck errors in the dialog and checks-panel reread tests
* fix(gitlab): keep a late write on the previous MR from touching the next one
A save, reviewer change, close/reopen/merge or comment that settled after
the dialog moved to another MR still reread and cleared busy state for
whatever was shown, restarting the new MR's first read and discarding its
answer. Those finalizers now reread and clear busy only while their own
MR is still shown, as pipeline retry already did, and switching MRs
resets the save, action and comment busy flags so the next MR is never
left busy.
* test(gitlab): give the pipeline tab test a details owner after the main merge
* Add standalone chat right-click session actions
* Update fork draft fixtures for source focus callbacks
* Read chat menu data only while the menu is open
Quick Commands and the provider Copy Session ID now read their data from
components that mount only inside the open chat menu, so closed menus in
retained chats do no work on repo, project or agent-status writes. The
add-command editor reuses the terminal's editor dialog and outlives the menu.
Chat menus also stop showing the Insert hint, since they run every quick
command in a new tab the way the tab bar's Quick Commands menu does.
* fix(agent-status): let Claude's own hook record its process when the pane's owner has none
An owner recorded without a process (Claude's trust prompt seen before any hook, or a hook that couldn't capture one) refused every later process the agent's own hooks proved, so live Claude terminals stayed unproven and the next Claude in the pane inherited the same owner. The agent's first non-exit hook that proves a process in the same session (or when the owner names none) now claims it; nested agents run another session and stay refused.
Tracked in STA-13222.
* fix(agent-status): a terminal observation doesn't name the pane owner's session
The trust prompt's row carries the pane's previous session (a forked resume's source, an earlier Claude), so the owner it recorded didn't match the session Claude then reported and its process was still refused.
Tracked in STA-13222.
* feat(agent-status): classify a hook's process against its pane from one process table
A hook process is the pane's root when no agent runs above it inside its
terminal session and it holds the foreground (or the foreground has no
agent); an agent above it makes it nested, a foreground agent makes a
background job competing, and anything missing or unreadable is unknown.
The reader validates PID and start identity with the existing probe before
reading the shared budgeted process table, and coalesces concurrent reads.
* fix(agent-status): only an agent's own evidence names a pane's owner; its root process acquires an unproven pane
Terminal, title and process-name reports and Orca's own restatements
(inferred settles, timer and poll republishes) now publish status but keep
the recorded association as it is, suspended and retired ones included, and
never create one. A genuine hook from an agent without process capture still
names its own session. An admitted exit is now an explicit result, so a
retired record carried on the next agent's terminal report never re-clears
it or refreshes the exit.
When a Claude hook carrying its process reaches a pane whose row has no
proven live owner (a trust prompt seen first, a launch seed's source session,
a hook owner that never sent its process, another agent's leftover record or
a retired one), the execution host classifies the sender before provider
folds run, in the shared hook preflight on both the desktop and the relay
(HTTP and spool). A root acquires agent, process and session together;
nested and competing background processes are refused; unknown evidence is
applied as a hook without a process and retried on the next hook. A late hook
from the retired process is refused before folds. Hooks matching a proven
owner never read the process table, and proven-owner rules are unchanged.
* test(agent-status): pin root acquisition gates, unreadable evidence and retired-process folds
Covers a mid-turn record left by another agent (the identity gate must not
refuse the proven root), an unreadable acquisition over a trust prompt (no
guessed process), and a late hook from the retired process being refused
before provider folds.
* test(agent-status): drop the terminal-first presence test the root acquisition contract now covers
* fix(agent-status): answer a hook's root read within the hook's own timeout
A busy Linux process table can take over a second; the hook's curl gives up
at 1.5s and spools its event. Each hook now waits at most 500ms, reads as
unknown past that, and the next hook joins the still-running read.
* fix(agent-status): prove a hook's process belongs to its pane's own job
The first rebuild judged a hook's process against the sender's own terminal, so a shell
wrapper named claude read as a nested agent (every hook refused), a Claude in another
terminal that inherited the pane key could take a Codex pane, a real nested `claude -p`
(run by Claude's Bash tool in a new session with no terminal) read as unknown, and a slow
whole-host process table made every blocking hook wait without ever healing.
Acquisition now needs proof that the process runs in the pane's own job on the host that
owns the pane: the pane's root comes from its PTY provider's inventory, the sender's
ancestry is walked across detached tool sessions up to that root, shell scripts and npx
layers count as launchers, the pane's terminal and foreground job decide root versus a
competing background or foreign terminal, and tmux panes are tied through the outer pane's
foreground client. Reads are targeted (the sender's lineage and the pane's terminal), one
500 ms answer deadline is shared per attempt, late results are kept, unproven evidence is
retried once per turn, and exits get fresh proof. The pane root's own exit retires the
same agent's unproven record once. Desktop, serve and orcad wire the resolver; the WSL
relay asks the desktop for the pane's guest root and keeps the legacy path when the desktop
or the pane's PTY predates it; a relayed process is pane-root proof only from a relay that
asked this session.
* feat(agent-status): name a WSL pane's guest root from the PTY that owns it
A WSL pane's PTY belongs to Windows, so the guest-side hook relay had no way to know which
guest shell is the pane's root: the Windows PID of wsl.exe means nothing inside the distro,
and an inherited pane key proves nothing.
The WSL bootstrap now prints a one-shot marker with its guest PID and Linux start identity
before it execs the login shell (same PID, every shell, never waiting on anything). The PTY
owner, the daemon session or the in-process provider, watches only the launch output for it
and keeps it as volatile metadata of that PTY incarnation in its inventory. The desktop
answers the relay's pane-root request from that inventory for the relay's own distro, and
marks that link as one whose relay proves pane roots. A PTY started before its owner
recorded roots answers legacy, so the relay keeps its existing path.
* test(agent-status): keep a Claude run under Hermes out of its scoped binding, then let the pane's Claude own it
* test(agent-status): mark the slow-host reader's fake-timer delay as no real wait
CI's flaky-test ratchet flagged the simulated read delay in the owner-presence deadline tests, which fake timers drive; the ignore names that, so the 800/2,000 ms contracts stay as they are.
* fix(agent-status): a pane's first unproven hook keeps main's process; only proof replaces it
Round 3 found four places where pane-root acquisition trusted something that is not proof:
- A WSL relay that merely asked for a pane root was trusted for every pane on its link, so after a relay restart a nested `claude -p` could take a pane on a legacy answer and its exit cleared the parent's row. The desktop now issues a binding only for a returned guest root, per pane and link generation, and accepts a relayed owner as proved only when it echoes that binding for the pane's current PTY.
- An untraceable launch (a spawning shim, screen, an unreadable ps, a missed answer deadline) into an empty pane recorded no process, so its exit no longer ended the row. As on main, that first hook now records its process, tagged as a fallback that a later proved root replaces (saved, so it survives a restart). A Claude in a tmux session the pane can't be shown to display gets its status, session and Done without a process.
- A slow host's late answer was dropped after 10 s and each turn waited again. The answer is kept, each process waits at most once, and a late answer now heals the pane, upgrades or withdraws a fallback, or retires the row on an exit that missed its answer, with no later hook and no replayed prompt.
- A suspended owner let any other process take the pane. Only the pane's own foreground job replaces it now; a nested or unverifiable sender is refused before it changes the prompt.
A hook that challenges the owner no longer erases the owner's proved exit unless it is admitted as the successor, and a pane inventory snapshot taken before a PTY spawned is re-read once instead of answering for it.
* perf(agent-status): cap a host's pane-root reads at four at a time
Each pane's first hook started its own ps reads, so a burst of panes (a restore, many agents starting together) spawned one process-table read per pane at once; on a loaded Linux or Mac host past ~70 panes that alone outran the hook's 500 ms answer. Every subprocess or /proc read the acquisition makes (the sender probe, per-PID and per-terminal ps, Linux start identity, tmux list-clients/display-message) now takes one of four shared slots, released on success, failure or abort, and an attempt past its work budget gives up its queued reads.
* perf(agent-status): share one pane-root request among a WSL pane's concurrent hooks
Hooks of one pane arriving together each asked the desktop for the pane's root; they now share the request in flight.
* fix(agent-status): read no tmux from agent-teams' synthetic TMUX; refuse a pane only shown elsewhere
Orca's agent-teams launch gives its Claudes a synthetic TMUX that names no tmux server, so their hooks sent a tmux hint and an untraceable first hook into an empty pane showed status without recording the process main records. One shared constant now names that synthetic socket for the launcher and the hint parser, which reads no hint from it.
A tmux session attached only in another app's terminal read like a detached one (status only). When no client runs in the pane and every client showing the hinted pane has a fully read lineage outside it, the hook is now refused as foreign; anything unverifiable stays status-only.
* fix(agent-status): a late root heals what its next hook would; a stopped fallback resumes as itself
A late answer only reached the pane if the row still had the association the read started against, so the status-only record a hinted first hook minted into an empty pane while its read was pending kept the root out until the next hook. A late root now acquires over any record a root outranks on the hook path (none, an unproven one, a fallback); a stopped or retired owner must still be the one the read started against, and an owed exit retires only the record that exit saw. The hand-off to the host follows whether a hook actually went on without the answer, not a second reading of the clock, since a hook's timer can fire before it.
A Ctrl-Z'd fallback owner's own hooks after fg were refused as a would-be replacement. Suspension now blocks only another process; the owner's own hook resumes it with its process, session and fallback tag, and a late upgrade of its own fallback keeps it suspended.
* test(agent-status): read a tmux pane shown only in another terminal through the real bridge reader
* fix(agent-status): point the moved local-PTY modules at the shared WSL root marker
main moved the local-PTY modules into src/main/providers/local-pty/; the merge carried this PR's two imports of the WSL guest root marker into them at the old depth, which broke the build.
* test(agent-status): type the pane-root reader test's process mocks
* test(agent-status): type the reader test's platform without an assertion
* perf(agent-status): give a spool drain one acquisition answer deadline
Startup replay ran each unproven pane's acquisition in series, so every pane
added up to 500 ms before the listener bound or live hooks were answered. The
drain now owns one deadline on desktop, serve and the WSL relay; every record's
attempt, joins included, is capped by it and hands a later answer to the host.
* fix(orcad): install the pane-root reader before startup replay
orcad started its hook server, and so replayed the spool, before installing
the pane-root reader; replayed hooks took the legacy path and recorded their
processes as proven owners. The reader is now in place before the server
starts, so replay reads the same evidence as live hooks.
* fix(agent-status): record a WSL guest root printed before its session subscribed
Output a PTY prints before its session subscribes is replayed while the
session is constructed. If that output held the guest-root marker, the
callback read the session before it existed and the WSL session failed to
start. The root is now held until construction finishes, then recorded.
* fix(native-chat): let createSupport ask whether another terminal runs a resumed conversation
A resume's createSupport can now carry resumeFrom (behind
agent-session.structured.resume-writer-admission.v1, since older hosts'
strict params reject it). The host runs the same writer check create runs,
leaving out the panes the client will close first (matched by key or by
the PTY they resolve to; a shared tmux/OpenCode server is never left out),
and probes the candidates together so a bounded client wait is not spent
on one probe after another. The host's English refusal says "another chat"
only when it names one. The resume params move to their own module to keep
the params file under its line limit.
Tracked in STA-13440.
* fix(native-chat): refuse a resume before anything closes or opens when another terminal runs it
Continue in Chat UI asks the host before closing the terminal, naming the
panes the close takes; when another terminal runs the conversation it says
so in one toast and leaves the terminal open with no chat. Session History's
Resume in New Chat (and any other resume launch) asks through the launch
admission and, on that refusal, opens no placeholder tab: its caller's one
toast is the only notice. A local admission that times out still never
leads to a close. Older hosts without the capability keep today's flow.
The launch admission's toasts move to their own module to keep that file
under its line limit.
Tracked in STA-13440.
* fix(native-chat): say why a resumed chat failed when a terminal holds it or its history is missing
A failed start refused because a terminal's agent still runs the
conversation (no chat named as holder) now reads the existing "already
running this conversation in another terminal" words instead of a bare
"Chat could not be started.". A transcript the host could not find yet gets
the same history words an unreadable one already had. This covers the
create-time backstop: a terminal started between the pre-check and create,
or an older host without the pre-check.
Tracked in STA-13440.
* fix(native-chat): keep exporting ResumeSource from the session params module
* fix(native-chat): keep a terminal open when its host's resume check could not be confirmed
A failed capability read was taken as an older host, so the resume question
was left out, the host admitted, and the terminal closed before create refused
the conversation another terminal runs. An unread capability now leaves the
resume unanswered; a host that reports an older capability list keeps its path.
* fix(native-chat): say "another terminal" only where the refusal's owner is still known
The write failure drops the refusal's owner, so a chat-owned conflict on a
send, mutation or phone notice read as a terminal. Only the failed start,
which keeps the raw refusal, now records that no chat was named; everywhere
else keeps the generic wording.
* perf(native-chat): resolve panes in the writer check only when some are left out
Every create, resume and acquire check resolved each matching row's pane to
its PTY, even with no panes to leave out, and each unresolved key scanned
every terminal. With nothing to leave out no pane is resolved now; with some,
one identity read context serves every key.
* test(native-chat): pin createSupport's resume refusal to create's, and History's one notice
Runs the real createSupport handler on a runtime whose status store proves
another terminal live: leaving out the source pane admits, otherwise it refuses
with create's code and details. The Session History replacement keeps its chat
and toasts once when the host refuses before anything opens.
* fix(native-chat): translate the "another terminal runs this conversation" toast
It is now the only notice when Continue in Chat is refused before the terminal
closes, and only English carried it, so every other language showed English.
* fix(native-chat): withhold an unread resume capability only where a terminal closes next
Reading an unknown capability as unreachable refused Session History and
/resume launches on a paired host that main admits and create completes. The
host question now asks the plain question on an unread capability and says so
on its answer; only Continue in Chat, which closes the terminal next, treats
that answer as not admitted, from the same read that chose the request.
* test(native-chat): count the writer check's terminal reads with a typed map
The perf contract counted iteration through a proxy, which the type-aware lint
rejects. It now counts record reads on a Map subclass; a scan of every
terminal per row still shows up as rows times terminals.
* test(native-chat): read the writer-check fixtures without type assertions
The changed-code gate rejects casts. The perf contract builds real terminal
records through the identity fixture, and the createSupport parity test reads
create's refusal through the shared refusal parser.
* fix(native-chat): declare the refusal holder that failed-start cause words read
The failed chat's notice passes its launch failure, with the holder its
refusal named, through the cause parts to the words that tell a chat from a
terminal. Those functions now declare that field instead of carrying it
undeclared, which the typecheck rejected for a literal in the test.
* perf(native-chat): probe a conversation's writers a few at a time and stop at a holder
The writer check started a process probe for every matching row at once and
kept them all running after the first live holder refused. It now picks the
rows in one synchronous pass, probes at most eight at a time through the
shared bounded pool, and starts no probe once a holder refused.
* test(native-chat): pin the writer check's single terminal look on the real runtime
The scale contract built its own resolver, so a host that made an identity
read per pane, or passed none, still passed. It now runs the runtime's own
writer check over recorded terminals and counts read contexts and per-key
terminal scans: one context and no scans with panes to leave out, none
without.
Top-level agent rows had no press, so a tap opened the workspace's active
tab; and a session the host list opens in-page read the pane only from
the shell route, which never has it.
Fixes#34235
* test: remove 25 low-value checks and six complete suites
* Remove deleted startup benchmark from plugin CI routes
* Remove CI route for deleted pet layout smoke suite
* test: repair retained E2E labels and collision lifetimes
* test: remove synthetic activation collision scaffolding
* fix: activate folders opened on the selected runtime
---------
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
* fix(wsl-hosts): a stopped distro still lists all its projects after a restart
The desktop now keeps each WSL host's last project list (from the repo.list
answers the window already receives) and seeds those rows at startup before any
live host catalog is requested. The first live list replaces them, so projects
deleted on the host disappear on that fetch. Loading the saved list is a desktop
read only: no wsl.exe, no host RPC, no \\wsl.localhost access. The saved list is
cleared when the host is removed.
* fix(wsl-hosts): pin saved project list writes, removal, WSL gate and seed races
- Exempt HostRepoCatalogSnapshotPersistence.environmentId from the id-only
store write ratchet like the paired-server layout snapshot (the id names the host).
- A live list applied before the startup seed now skips that host's seed, and
a live answer requested before the seed may still drop seeded rows.
- Tests now count saves, cover remove then re-add, check paired servers in
storage and in the listing, and cover both seed/live-list orderings.
* WSL hosts: penguin mark for WSL host rows, and on the stopped-distro notice
Sidebar project headers and workspace rows that named a WSL host with a
text badge ("orca-demo (WSL)") now show a small penguin icon instead,
labelled and tooltipped "Runs on WSL: orca-demo (Linux)". The same mark
replaces the host chip in the jump palette. The "<distro> is stopped"
notice leads with the same penguin.
* Wait on the tooltip instead of sleeping in the WSL mark tests
* Redraw the WSL penguin as the classic mascot; focusable tooltip mark; muted token on the stopped notice icon
* Use the classic Linux mascot silhouette for the WSL penguin
* Tolerate unloaded runtime environments in the WSL host mark selector
* fix(wsl-hosts): keep the e2e fake WSL connector out of release builds
The fake WSL host connector was compiled into every build and honored
whenever ORCA_E2E_FAKE_WSL_HOSTS was set. Gate main and preload on
import.meta.env.MODE === 'e2e' (the mode every e2e build already uses),
so other builds fold the branch away and drop the module, and mark its
module-level schemas pure so none of it is retained.
* fix(wsl-hosts): build the e2e fake's zod schemas lazily so release builds drop them
Eager module-level zod chains survived tree-shaking even with a PURE
annotation on the outer call, so the fake's schema construction still
shipped in out/main/index.js.
wsl-host-paired-phone asserted the pre-#36771 'isn't running' copy; it now
asserts the stable remote_runtime_unavailable code and '<distro> is stopped'.
wsl-move-dialog's gate-closed case seeds a saved host, which since #34683 puts
the app in serve-only: the WSL hosts section still lists the host. Assert
instead that Add is hidden and the host row's menu has no move entry.
Co-authored-by: Claude <noreply@anthropic.com>
* fix(wsl-hosts): remove a freshly installed orcad that fails its start check
A WSL connect that uploaded an orcad build whose candidate then failed its
preflight or readiness check left the complete install in place, so every
later connect reused the same broken bytes. deployOrcad now reports whether
it uploaded the slot and whether the candidate's own start check failed, and
the WSL deploy removes that slot under the same pins, liveness probe and GC
claim the version GC uses (active, rollback target, the serving daemon's
build, journaled transactions), so the next connect re-uploads it.
* fix(wsl-hosts): fence the failed-install removal and keep a slot any process runs from
Review follow-up. The pin check and the delete now run under the
activation fence (a held fence keeps the copy), so a concurrent connect
cannot preflight or launch the slot between them; it waits, finds the
slot gone and re-uploads. Liveness now also scans the process table and
the daemon pid files for anything running from the slot, because a
candidate's stop ends only its server, not a terminal daemon it spawned
there.
* fix(wsl-hosts): match the resolved slot path in the slot process probe
Node realpaths its entry, so a daemon behind a symlinked home or data
root names the resolved slot. The probe now also matches
$(cd slot && pwd -P)/ and answers UNKNOWN (keep) when it cannot resolve.
* test(wsl-hosts): wait for sibling slots to run before proving this slot idle
Replaces a fixed 100 ms sleep (flagged by test-no-real-time-wait) with an
expect.poll until each sibling's own slot probes LIVE, so the DEAD answer
for this slot is meaningful.
* fix(github): prefer the open PR when a branch has several
The branch lookup asked GitHub for one PR across all states. GitHub sorts
a branch's PRs newest first, so a closed PR opened after the live one
shadowed it and got linked to the worktree on every checkout.
Fetch a page of the branch's PRs, REST and the `gh pr list` fallback alike,
and take the open one; with none open, keep the newest as before.
* refactor(github): keep branch lookup casts on their own lines
---------
Co-authored-by: agustin2606 <agustinvarela2606@gmail.com>
* fix(claude): Full access approves Claude's own permission asks in chats
A Claude chat in Full access still showed Allow/Deny cards whenever Claude Code
forwarded an ask it keeps under bypass mode (ask rules, ask-answering hooks,
built-in shell safety checks). Approve those at once while the chat runs with
Full access, read per request; questions and plan approval still go to the user.
* fix(claude): Full access grant comes from the launch; Claude's mode reports restrict it in wire order
Only a process Orca launched with Full access can auto-approve Claude's own
asks; Own settings never does, whatever Claude reports. Claude's init/status
mode reports, read from stdout before the SDK sees them, can suspend and
restore that grant, and each permission request keeps the mode in effect at
its own position in the stream, so a paused journal consumer or a read-ahead
chunk cannot apply a report late or early. Questions, plan approval and
requests Claude flags as needing the person's answer keep their card.
* fix(claude): Full access keeps every request's own wire position and restores after an approved plan
A permission request Orca never saw on stdout no longer inherits a later
mode: each request keeps the first snapshot for its id until the SDK hands
it over, including after a cancel and past any number of unread requests,
and requests resent in initialize's reply are recorded where that reply
arrived. Approving a plan in a Full access chat now reads Claude's mode in
wire order, so the restore is sent even while the chat's presentation still
lags behind the plan report.
* test(claude): narrow contract-pin frames to permission requests with a type guard
* test(claude): count the policy's stdout search work instead of timing it
* test(claude): type the contract-pin frame guard with the fixture frame union
* refactor(claude): let the launch permissions wrap the exit handler, keeping acquisition under its line limit
* fix(native-chat): show a terminal's unsent input in the chat composer and replace it on send
Switching a pane to chat view now seeds the composer with the text left unsent in Claude Code's or Codex's input box, and a chat send clears every line of it instead of one Ctrl+U. The clear is confirmed with the same typed-only read and kept under the 64-byte chunk Claude Code reads as a paste.
* test(native-chat): drop the removed screen-text clear check from the background-rows test
* fix(native-chat): clear a seeded multi-line draft before typing a Codex command from chat
* test(native-chat): expect the typed command's clear argument in composer tests
* fix(native-chat): confirm a seeded draft is cleared before typing a Codex command
* fix(native-chat): find Claude's closing frame past dim suggestion rows
A typed-only read stopped at the suggestion row, so a draft under Claude's hidden caret never reached chat.
On a Nothing A065 (Adreno 730) the transparent pixels of these two
scroll layers turn black while a selection handle is dragged. Fill each
with the colour already behind it so the layer has nothing to drop.
Refs #36553
* fix(mobile): back from a session lands on its host's session list
A session opened from Home's "Jump back in" or a notification replaced the
host list it had just mounted, so Back went to Home. It is now pushed over
that list.
A session opened from the host list lives inside the list's own page, and
the stack holding it has one screen, so the iOS edge swipe belonged to the
parent screen and popped the whole host to Home. While the page claims Back
the parent's swipe is turned off too, and a left-edge pan on the shell view
sends Back to the page.
* fix(mobile): keep the host swipe off until its last page claim ends
Count claims per parent screen instead of guessing whether a shell is its
stack's root, and measure the back edge from the shell's own left edge so
a landscape safe area does not hide it.
* refactor(mobile): share the session route name and write the host swipe once per claim run
* test(mobile): give the catch-all screen mock a parent navigator
* fix(native-chat): an open chat moves to the account you switch to before its next message
A running chat's agent read its account only when it started, and nothing compared it with the
account a start would use now, so open chats kept answering on the old account after a switch.
The agent a chat runs now records the account its launch used, and the host's replace-before-the-
next-send check replaces an idle one whose account is no longer what a start would use. A chat
mid-reply finishes on the old account first. Claude chats follow; agents whose chats keep the
account they were created on are never compared.
A chat's model-list reads and saves now use the account it runs on, so a moved chat no longer
writes its new account's list under its first account (STA-11281).
Tracked in STA-11211.
* fix(native-chat): declare the launch-account read for the runtime layer that wires the host
* fix(claude): find custom chat history before managed-account resume
* test(claude): assign the complete custom account home
* feat(native-chat): offer account switching and hand-off at usage limits
* fix: track the provider in account-list reload effects
* fix(native-chat): target recovery actions at the chat host and transcript
* fix(native-chat): verify account recovery for each chat on its host
* refactor(native-chat): retain the existing image-support result
* fix(native-chat): withdraw account recovery after failed eligibility reads
* fix(native-chat): leave unavailable recovery facts absent
* Align Japanese usage-limit recovery copy with catalog convention
* Preserve complete chat context through usage-limit recovery
* Keep Continue callback focus optional
* Keep recovery fixtures and account effects type safe
* Keep chat recovery on native sources and native accounts
* Validate native recovery files after path admission
* Use the optional cursor shape in recovery fixture
* fix(native-chat): exclude source CLI family from limit handoff
* Resolve recovery context in the owning workspace directory
* Add the continue-at-usage-limit-reset setting and its chat row lines
* Continue chats automatically after usage limits reset
* Fix automatic continuation fairness, lifecycle and host settings
* fix: bind automatic continuation withdrawal to accepted actions
* fix: withdraw source auto continuation after handoff starts
* Read unopened chats with the saved-record reader for usage-limit continue
Unopened chats were read through the raw-row replay, which no longer sees
chats saved as keyed records, so a usage-limited chat that was not open
was never continued after its reset. Read them the way the rest of the app
reads a chat without opening it. Also use the shared visible-tab check,
keep the ordinary rewind result without a sequence as main does, and adapt
two tests to the current queued-message and saved-status behavior.
* Keep a usage-limited turn idle after any rewind restores it
Rewind completion read the resulting conversation through the raw-row
replay, which no longer sees chats saved as keyed records, and a forked
rewind wrote its completion before the new history's records. So a
limited turn that a rewind brought back was continued automatically
after its reset. The completion now reads the saved result the way the
app reopens a chat, and the forked rewind writes its completion after
the new history in the same transaction.
* Type the usage-limit auto-continue test mock without an assertion
* Fix type errors from main's settings, failure-wording and refusal changes
* Keep ordinary settings replies when the paired host changes mid-call, and list the cancel method in wire contracts
Settings reads and writes that don't carry the automatic-continue choice go
through the common runtime call again, so a reply that completes after the
paired host is removed still merges, as before this change. Only a write of
that choice stays pinned to the host it was made for. The structured method
count and the cross-version method manifest now include the cancel method.
* Keep a stopped turn's automatic continue withdrawn when its usage limit arrives later
A person could Stop a running Codex turn, have the turn then end with a
usage-limit failure, and still get an automatic "Continue where you left
off." after the reset, because Stop had nothing to cancel yet. The journal
write that first reveals a limited turn the latest personal Stop owns now
saves the same exact cancellation in that transaction, and a Stop accepted
just after the limit landed withdraws it too. Resume, deleting a queued card
and restarting keep it withdrawn; manual Continue and later turns are
unaffected.
* Bound the automatic-continue sweep and keep notice rows from re-rendering
The 10-second sweep now does nothing while the setting is off, republishes
only chats with a scheduled continuation, reads at most three unopened chats
per pass, and keeps going when one chat's saved history can't be read (that
chat is retried after the others instead of stopping every chat on the host).
Settings writes republish only when the switch changes. Working out the
usage-limit cut no longer indexes the whole conversation on every streamed
row. The chat's notice rows no longer re-render for status changes they
don't show. Adds operation-count and render-count tests for these bounds.
* Test that streamed journal commits after a Stop scan no history and build no command index
Drives real Codex rows through the host at 20 and 200 history rows: each streamed commit runs the Stop's commit hook and the status projection's cut reader with no newest-turn scan, no render and no full command index; the next turn end scans once and renders nothing.
* Leave a usage limit manual once its reset passed more than a day ago
Turning automatic continue on later no longer sends into chats whose limit reset days ago. Eligibility, which the row's summary, the sweep and the pre-send recheck all read, now requires the reset to be within the last 24 hours; older limits show the usual manual actions and are never continued unasked.
* Show only manual actions for a usage limit Orca can never continue
A limit more than a day past its reset is never continued, but its row still showed the setting link, inviting people to turn on a switch that could not help that chat. One shared check now decides whether a cut can ever be scheduled; the status summary and the sweep's eligibility both use it, so past the bound the row keeps only Continue Now, Hand Off and Add Account. A row already on screen when the day passes drops the line on the shared minute clock; the host alone decides sends.
* List every journal row kind in the Stop cut filter
The type-aware lint requires exhaustive switches; epoch, tombstone, submission and queue rows still cannot reveal a cut.
* Type the status-subscription mock instead of casting its handler
The changed-code casting gate rejects type assertions; the mock now carries the real subscription signature, so the recorded handler is typed.
* Open store-less conversations without the Stop withdrawal hook
Acquisition-only opens have no record store, so a person's Stop followed by a limited turn end made the journal commit throw and drop the turn end. Install the withdrawal only when a store exists; without one there is no continuation to withdraw. Also narrow the status summary before reading it and type the sweep test's send mock.
* Show the open orchestration panel as a floating card
The open panel now floats in the closed tab's corner as a card as tall as
its rows. In chats it stops above the composer (the transcript frame
already ends there); in terminals it keeps the bottom quarter clear for
the CLI's prompt and recent output. Past that it scrolls inside.
* Keep the orchestration card's collapse button reachable in tiny panes
A terminal split can be 50px high, leaving the card no room under the 75%
limit, so its header and collapse button were clipped away. The card is
now never shorter than its header.
* Keep the orchestration card's collapse button inside narrow cards
In a narrow split the card is 20px narrower than the pane and its title
didn't truncate, so the collapse button was pushed past the card's edge.
The title now truncates and the header's side padding gives way before
the button, down to the 50px pane minimum.
* Launch an agent with a first prompt from its setup panel
The agent setup panel in the new-tab menu gets an optional prompt box above
its Launch buttons. It is the chat composer in a compact launch layout: one
line that grows to six, Attach as its only control, / listing the launch
workspace's skills and commands and @ finding its files. Enter launches the
panel's default way, either Launch button sends the prompt its own way, and
with nothing typed both launch exactly as before. The prompt rides the
existing launch prompt field and is kept in memory only until the launch.
* Preserve launch prompt input across submission and refusal
* Retain scoped composer submissions through launch ownership
* Keep launch prompt tests deterministic during collection and persistence checks
* Retire launch source drafts at committed qualified removals
* Retain workspace launch setup through ordinary rich drafts
* Preserve rich draft authority through accepted setup handoffs
* Keep setup prompt moves within current rich draft memory
* Create setup drafts on first input instead of on row render
Rendering an agent row in the launch menu or search no longer creates a
setup record. The row derives its scope from its workspace, host and
agent without touching session state; the record is created by the first
typed prompt, option change or pending attachment, matching main, which
kept only authored setups. Catalog applies, readoptions and renames now
visit authored setups only.
Option listeners use the existing per-scope draft listeners and subscribe
only while the setup popover is open. Also return the runtime-status
files to main, which only carried leftovers from a removed hook.
* Return group-delete draft revocation to main and repair launch tests
Deleting a project group no longer retires in-flight setup submissions
for its folders: folder keys are never derived again, so it changed
nothing users could see. The group mutation, its removal state and the
prompt-delivery type widening go back to main's content, with the test
that exercised the revocation.
Test fixtures catch up with the setup prompt composer: the TabBar window
stubs gain event listeners, the picker inventory's mock store gains agent
status, create-rejection handbacks expect inComposer, and the folder
removal test expects a same-ID survivor's chip to stay, as on main.
* Keep each search preset's setup options in its own slot
Opening a search result's setup no longer writes its preset over the
workspace's setup. As on main, each preset keeps its own options slot,
now inside the workspace/host/agent setup, keyed by what the search
parsed rather than by defaults; the plain row keeps its own slot. Only a
real change saves, into that entry's slot, and creates the setup then.
The typed prompt stays one per workspace, host and agent.
* Fix the moved agent profiles import and merge duplicate imports
Main moved the native chat agent profiles module under shared/native-chat,
so the setup prompt composer imports it from there. Files that imported
one module twice now import it once; nothing else changes.
* Fix the web typecheck for the setup prompt changes
The catalog continuity test no longer imports the main process's SSH
target reassignment, which pulled the whole main graph into the web
program; it builds the reassigned folder inline. Test fixtures and spies
now match current types, the edit-session tests pass a composer ref as
production does, and the setup panel again accepts callers that return
no launch answer. The pending-chip owner filter drops an unused name.
No shipped behavior changes.
* Show the setup prompt's skill and file lists above the setup panel
In the agent setup popover, the / and @ lists opened underneath the
panel, so they could not be seen or clicked. A list opened inside a
popover now takes the menu layer that selects and dropdowns already use
above popovers; an ordinary chat's lists keep their container and layer.
The prompt placeholder is translated in every locale, and folder draft
continuity takes the fetched catalog itself instead of reading its
folder list field.
* Fit the setup prompt box to a placeholder that wraps
With a longer translation, the empty setup prompt's placeholder wrapped
to a second line that the one-line box cut off. The empty launch prompt
now lets its placeholder's wrapped height count, so the box fits it;
English still fits one line, and an ordinary chat's box is unchanged.
* Type the submit test's pending sends as the boolean main now returns
* Show the dictation button in the agent setup prompt
* Update draft test handle for agent references