* feat(mobile): show the context usage ring in the chat composer
Desktop's ring reads the structured session's context facts; the phone
never read the host's contextUsage answer. The summary rules move to
src/shared so both read the same numbers, and the title card's anchored
card machinery is generalized so the ring's breakdown opens above the
composer without dropping the keyboard.
* refactor(native-chat): share the context ring's critical threshold
* test(mobile): stub the context ring where composer tests stub its siblings
* fix(mobile): keep the context card with the composer and the keyboard up
Touching the card no longer takes focus from the draft, the open card
moves with the composer as the keyboard or draft resizes it, and the
composer's own menu closes it.
* fix(mobile): close the context card when the composer hides, and let long titles wrap
* refactor(mobile): share the anchored card layer and the ring readout
* test(e2e): pass the new options arg in the permission publication test
* feat(native-chat): show the chat account usage for /usage
* fix(native-chat): derive usage card lifetime from its owning turn
* test(native-chat): keep runtime manifest coverage additive
* fix(native-chat): advertise usage from the host options reader
* fix(native-chat): read cold chat usage through the chat's own Codex launch
- Cold /usage starts a short-lived app-server the way the chat launches
(configured command, args, environment, pinned home), as Codex rename does;
the status-bar probe returns to its original path.
- Report each reset outcome inline after the card refreshes.
- Send the chat's account as a typed kind plus email; the client owns copy.
- API-key accounts are recognised by a typed error, not message text.
- Keep the caret after kept text; drop unreachable WSL matching.
* refactor(native-chat): share the at-rest Codex app-server launch between rename and usage
* fix(native-chat): keep a reset's outcome when the usage refresh fails; label accounts by kind
* fix(native-chat): drop stale usage replies by request id instead of a render-time ref
* test(native-chat): keep the usage card test inside the web project
* fix(native-chat): clear the usage card when a waiting prompt changes; retire its callbacks on unmount
* chore: drop accidental pnpm lockfile churn from the main merge
* fix(native-chat): put the caret after kept text on /usage; offer the reset once the host's first Codex read lands
* fix(native-chat): type the usage snapshot wait and its test state
* fix(native-chat): re-read the usage offer when the chat host's Codex state changes, instead of forcing a host read
* fix(native-chat): watch the usage host from the card's opening and keep one background re-read at a time
* fix(native-chat): bind the usage card's background re-read to its opening
* feat(native-chat): open /usage as a modal like /resume
The chat's Codex usage card now opens in a root-hosted dialog with the
same surface, width and dismissal as /resume's Session History, instead of
a full-width card docked above the composer. Closing the modal retires its
reads; docked-only clearing on turn, prompt and session changes is gone.
* fix(native-chat): give the /usage modal /resume's fixed height and drop a replayed mount's first read
* fix(native-chat): size the /usage modal to its card and keep the card's layout while loading
* fix(native-chat): pin the /usage modal's top where /resume's sits so loading never moves its title
* chore(native-chat): describe the /usage loading placeholder accurately
* feat(mobile): dock the chat's plan above the composer
Desktop docks the latest plan above the composer; the phone only drew it
inline in the transcript. Move desktop's docked-plan rule to src/shared and
draw it on the phone as a collapsible strip in the background-tasks box.
* perf(native-chat): keep the docked plan's identity until the plan changes
* refactor(native-chat): read the docked plan from the newest message back
* refactor(mobile): drop a cast in the docked plan's open memory
* test(mobile): pass the tray's new taskList in the recovery test
* feat(mobile): name and link agent senders on queued chat messages
Queued cards and the queued-message editor drew the sender from the saved snapshot name as plain text. They now share the transcript card's sender row, so a queued message names its sender's chat by its current title and taps through to it, as desktop does.
* fix(mobile): keep the queued sender line on one row
* refactor(mobile): tidy the queued sender row and editor heading
* fix(mobile): bound the queued sender row to its container width
Cmd+J and the new-tab search built open-tab rows only for a hand-kept
list of tab kinds, which never included native chats. Workspace tab
kinds are now every kind except browser and simulator (which have their
own rows). Chat rows use the tab strip's chat name and provider icon,
and selecting one activates it the way clicking its tab does, including
dismissing a paired-device page placeholder over it. The new-tab search
reads only its own workspace's chat names.
Tracked in STA-13638.
* fix(tabs): show the agent session's name on terminal tabs
The tab strip rebuilt each terminal tab without its session title and then re-ranked it, so the first-prompt title won over the session's own name. Carry the session title through the projection, and give the tab strip, unified tab label and sidebar agent row one shared name order so they cannot drift.
Co-authored-by: AJIADb9 <ajiadb9@bgd.team>
* fix(tabs): paired desktops take the host's session name for mirrored terminal tabs
The host projection now forwards the window's session title to paired clients, and the client's rebuild adopts it (older hosts omit it, so the client keeps its own). Without it a mirrored tab re-ranked to the client's first-prompt title.
* fix(tabs): one writer per session for a mirrored tab's session name
The paired client's own title sync keeps a session it already tracks current; the host's name only fills a session the client doesn't know, so a stale host snapshot can't revert a rename the client already read.
* fix(tabs): a paired host is the only writer of a session name it publishes
* fix(tabs): only a host window that resolves session names speaks for them
* fix(tabs): derive session title authority from live publishers
* fix(tabs): keep the session title publisher check concrete for runtime subclasses
* fix(tabs): one publication when a closing window drops browsers and title authority
* test(tabs): follow main's runtime test helper layout
* fix(tabs): paired desktops keep a quick-command name ahead of the session name
* fix(tabs): a name the host cleared doesn't come back as the idle pane's title
* test(tabs): build the idle-pane fixture as its own surface variant
* fix(tabs): refresh live session names from their authoritative source
* fix(tabs): preserve title recovery and bound refresh retries
* fix(tabs): preserve Codex index names at EOF
* fix(tabs): track the observed Codex index end
* fix(tabs): point the moved session-title projection at its new shared path
---------
Co-authored-by: AJIADb9 <ajiadb9@bgd.team>
* feat(mobile): show background task rows in the chat transcript
* fix(mobile): truncate the task output path like desktop
* fix(mobile): scale and select task rows like the rest of the transcript
* fix(mobile): translate the task output line
* refactor(mobile): read task rows from the shared row content
* test(mobile): restore the text reader for task row tests
* fix(native-chat): show defaults for chats that have never started
* fix(native-chat): share default projection across controls and picks
* test(native-chat): prove controls recover from cached discovery
* test(native-chat): type deferred catalog as its wire result
* test(native-chat): preserve the catalog origin literal
* test(native-chat): remove duplicate RPC work-count cases
* Show source scan notices accurately in mobile Agent History
Reuse the existing desktop presentation policy in shared code, keep host failures and source notices separate from skipped transcript files, and retain their scanner-authored messages.
Adapted from the remaining mobile presentation in original PR #15671. Rebased onto main: the classifier now lives in src/shared/ai-vault/scanning/, desktop keeps its translated skip reasons, and mobile reuses its existing skipped-transcript notice.
Co-authored-by: Brennan Benson <79079362+brennanb2025@users.noreply.github.com>
* refactor(ai-vault): share the scan issue row key between desktop and mobile
---------
Co-authored-by: Neil <neil@stably.ai>
Co-authored-by: Brennan Benson <79079362+brennanb2025@users.noreply.github.com>
* fix(tabs): show the agent session's name on terminal tabs
The tab strip rebuilt each terminal tab without its session title and then re-ranked it, so the first-prompt title won over the session's own name. Carry the session title through the projection, and give the tab strip, unified tab label and sidebar agent row one shared name order so they cannot drift.
Co-authored-by: AJIADb9 <ajiadb9@bgd.team>
* fix(tabs): paired desktops take the host's session name for mirrored terminal tabs
The host projection now forwards the window's session title to paired clients, and the client's rebuild adopts it (older hosts omit it, so the client keeps its own). Without it a mirrored tab re-ranked to the client's first-prompt title.
* fix(tabs): one writer per session for a mirrored tab's session name
The paired client's own title sync keeps a session it already tracks current; the host's name only fills a session the client doesn't know, so a stale host snapshot can't revert a rename the client already read.
* fix(tabs): a paired host is the only writer of a session name it publishes
* fix(tabs): only a host window that resolves session names speaks for them
* fix(tabs): derive session title authority from live publishers
* fix(tabs): keep the session title publisher check concrete for runtime subclasses
* fix(tabs): one publication when a closing window drops browsers and title authority
* test(tabs): follow main's runtime test helper layout
* fix(tabs): paired desktops keep a quick-command name ahead of the session name
* fix(tabs): a name the host cleared doesn't come back as the idle pane's title
* test(tabs): build the idle-pane fixture as its own surface variant
* fix(tabs): point the moved session-title projection at its new shared path
---------
Co-authored-by: AJIADb9 <ajiadb9@bgd.team>
* Show background completion mail as its command source
* Use minted sender handles in identity regression fixtures
* Verify command source labels in translated chat views
* Preserve command-only queued source regression coverage
* Use a minted terminal identity in host sender coverage
* Reuse command sender labels across unchanged message and queue reads
* Keep sender performance contract within the shared typecheck boundary
* Keep command reports in the background surface and preserve observed sender identity
* Use the shipped phone background report translation namespace
* Settle the prior dispatch before testing terminal reuse
* Keep live worker status tied to its recorded agent invocation
* Withdraw worker invocation proof when identity refresh fails
* Drop unproved worker associations at the failed refresh boundary
* Cover ordinary and remote sender rows during failed refresh
* Assert preserved session and peer content on failed sender reads
* Align sender navigation and relay tests with observed provenance
* Keep background report sources neutral and bound sender snapshot caches
* Construct readonly phone report fixture without mutation
* Keep callback-free federated transport assertions exact
* Keep orchestration sender identity separate from endpoint activity
* Validate mailbox receipt fixture shapes without casts
* Keep current Crew endpoint status separate from saved message activity
* Keep sender activity fixtures within lint contracts
* Avoid repeated serialization for fitting relay pages
* Use the valid workspace sidebar value in scale coverage
* Keep operation-count SQL expectation in sync with main
* fix(native-chat): make file links in terminal-backed plan approvals actionable
Each chat view now provides its link handler through one per-chat
context that link-drawing components read themselves, replacing the
onLinkClick/allowFileUriLinks props threaded by hand through rows and
cards. The terminal-backed approval card was the surface that never got
them; any card inside a chat view now gets links without wiring.
Tracked in STA-13722.
* native-chat: correct link context comment
* native-chat: fixture for a terminal-backed plan approval with file links
* native-chat: drop stray blank line in turn-diff rollup
* fix(agents): tell Codex subagent rows apart by task name instead of role
A Codex subagent's task name only reached the sidebar when one early read of its rollout succeeded; otherwise every child fell back to its role, so two workers both read "worker". The child poll now re-reads an unnamed child's own rollout, the first-line read allows the existing 256 KiB line cap, and a child with no task name or nickname carries the tail of its id, as Codex's own agent list does. Labels keep the path below the root so nested children with the same leaf stay distinct.
* fix(agents): retry an unnamed Codex child's own rollout without a parent transcript
A relay restart can leave a child hook as the only evidence, sent before the child's rollout was readable. Keep that path as pending identity work and retry it through the existing transcript poll, which now stays scheduled while a child still owes its name.
* fix(agents): carry the id tail to every child-row surface and bound identity retries
- Full-mode sidebar rows and dashboard subagent cards use the same suffixed label as compact rows.
- A role a host publishes as the name (Claude's subagent_type) no longer counts as a name.
- A final identity miss no longer re-arms polling; retries take turns, eight children per poll.
- Replace an error cast with a type guard.
* fix(agents): keep every identity read inside the per-poll budget
The parent-rollout poll now queues an unnamed child for the bounded, rotating identity retries instead of reading it directly, and full-mode rows keep the id tail for a child with no name or role.
* fix(agents): keep plain names on task-only rosters and guard the queued rollout path
A host that publishes only a task roster carries no role, so its names can't be told from roles and get no id tail. Update the sidebar lineage test for a role-only child's id tail.
* fix(agents): tell role-named tasks apart on task-only rosters
A host that publishes only a task roster sends Claude's subagent_type as the task name, so two such tasks read identically. A named agent task with no description now carries its id tail; an unnamed one keeps its kind label.
* fix(agents): a task path found meanwhile wins over a queued header read
Placeholder labels (e.g. unknown) count as unnamed when queueing, and a child the parent rollout named before its turn drops its pending read instead of being overwritten by the header's nickname.
* fix(acp): permission prompts from an agent's own work wait for you
A permission or question that an ACP agent (OMP, Grok, OpenCode, others)
asks during work it started itself, such as picking up a finished
background job, was answered "cancelled" at once and never shown. It now
shows as a card, raises the needs-input alert, and waits for the answer,
unless Stop, a steer or teardown cuts it short.
While OMP refuses a sent message as busy, a request from its own turn now
appears at thread level instead of being cancelled, so it never lands in
the held message's turn.
Tracked in STA-13625.
* fix(acp): keep later requests askable after a Stop, and honor the agent's withdrawal
A Stop or a card's Cancel left the chat refusing every later permission
request until the session ended; the stop now covers only the work it
interrupted. A request the agent withdraws with $/cancel_request now
withdraws its card. Cancel on a card from the agent's own work reaches the
agent even when no message is running.
* test(acp): narrow approval rows before reading their resolution
* fix(acp): a live request's card outlives its turn instead of being cancelled with it
Requests group with the active turn again, as before. A permission or question
the agent is still waiting on now stays pending and answerable when its turn
ends, is replaced, or is settled by the host; only the person's answer, the
agent's withdrawal, Stop, a steer or the session ending settles it. Settled
requests are pruned at turn end.
Stop covers only Orca's running message, so later requests from the agent's
own work can still ask. Cancel on a card with no running turn now reaches the
host from desktop and phone for every agent, and a question the agent
withdraws before its card opens no longer leaves a stuck card.
* fix(acp): never strand a live request without a card, and scope Cancel to it
A request the agent still waits on now always gets an answerable card, even
when its turn settled before the card was written, and answering it releases
the timeline's hold. Cancel on a card from an agent's own turn refuses further
requests from that turn until it ends. Desktop never turns Cancel on a card
into a whole-chat Stop on hosts that can't take a card cancel.
* fix(acp): a new message is never covered by a Stop of the agent's earlier turn
* fix(native-chat): a card's Cancel with no running turn passes the RPC schema
The cancel params required a turn whenever a card was named, so Cancel on a
card from an agent's own work (and Pi's turnless card Cancel) was rejected
before it reached the host. A background-task cancel still names its turn.
* test(rpc): a card with no running turn cancels by itself
* refactor: organize runtime semantic operations by concrete owner
* refactor: consolidate terminal tab close type imports
* refactor: finish runtime contract owners and mobile catalog snapshot ownership
Double-clicking a file or folder name no longer starts inline rename.
The second click of a fast pair on a folder now toggles it back, and a
file name double-click pins the preview like the rest of the row.
Rename stays on Enter and the context menu.
Update, Rollback, Recover and Restart of a managed server already reset
its crash-loop brake as Connect does, but left the user's Disconnect of
the server and its SSH host in place, so the action was refused. They
now lift the holds Connect lifts (server and host Disconnect, cancelled
sign-in, re-pair cap) without dialing the host first, since Connect's
server-update check would run before the action (a Rollback would then
roll back the update it just made). Status resumes once the action ends.
A host with "Reconnect on launch" off holds its servers disconnected at
every launch. Their status now says so ("Reconnect on launch is off for
<host>. Connect to resume.") instead of claiming a manual disconnect the
user never made. The error code is unchanged.
Refs #38347
* perf(plugins): read catalog images in batched Git calls
Each catalog refresh ran one ls-tree and one cat-file per image or
manifest read. Batch every file an extraction round asks for into one
ls-tree listing and one cat-file --batch read, then rerun extraction
over the loaded files until nothing is missing.
* fix(plugins): bound speculative catalog blob prefetch
---------
Co-authored-by: m4air <m4air@Mac.localdomain>
Co-authored-by: Neil <neil@stably.ai>
* perf(tab-bar): reuse each tab's activity status across unrelated store writes
* fix(tab-bar): retain only each tab's activity memo inputs
---------
Co-authored-by: m4air <m4air@Mac.localdomain>
Co-authored-by: Neil <neil@stably.ai>
Opening a branch in Source Control already compares it. The first status
and upstream loads then each looked like a HEAD move or a push and
queued one or two more full compares. Only treat known-to-different
values as a change.
Co-authored-by: m4air <m4air@Mac.localdomain>
Forge detection asks GitLab, GitHub, GitHub Enterprise, Bitbucket, Azure
DevOps and Gitea in turn, and each probe ran its own git remote get-url.
Share one read per remote across a single detection pass; the scope
closes when detection returns, so later reads see current config.
Co-authored-by: m4air <m4air@Mac.localdomain>
Each local terminal spawn with a Pi agent home rewrote three Orca-owned
extension files (~54 KB) synchronously on the main thread even when their
contents were already current. Compare the read we already do for the
ownership check and write only when the content differs.
Co-authored-by: m4air <m4air@Mac.localdomain>
The first agent-availability derive forced a second interactive login shell
moments after the Claude profile router's capture; settings changes did the
same per update. Recapture now accepts a capture started within the 10s
shell-environment TTL, and startedAfter lookups answer from a finished run
that started after the request.
Co-authored-by: m4air <m4air@Mac.localdomain>
The saved-password detector re-scanned every credential form on each
mutating page twice a second (forcing layout per input and walking the
page's buttons), but main only reads those snapshots for 2.5 s after a
login navigates. Main now tells each document at enable whether it wants
them.
Co-authored-by: m4air <m4air@Mac.localdomain>