* fix(jcode): keep the agent row for Jcode panes and read its working title
On Linux the Jcode release runs jcode-linux-<arch>.bin behind a jcode wrapper, so
the foreground read never identified the pane, and Jcode's own title
(<emoji> jcode/<server> <Codename> · work ~2s) was not classified. Once Jcode
replaced its startup title, the title-derived row lost its only identity and
disappeared. Map the platform binary to jcode, accept the server-qualified
identity title, and read the work/last tail as working/idle.
* fix(jcode): read the bare title tail only in a Jcode pane
The activity tail on conversation and SSH titles is too generic to prove an
agent, so title-only readers must not treat it as one. Gate it on the pane's
agent, as Hermes markers are, keep identity titles self-describing, narrow the
server segment, and keep the title strip linear.
* fix(jcode): keep the turn tail out of title-only readers
Title-only readers (completion tracking) saw a turn from Jcode's identity title
and then idle when Jcode switched to a conversation title naming another agent.
Read the tail only through the pane-scoped reader, check it before generic
title status in the sidebar row, and stop treating a bare jcode/<dir> as Jcode.
* fix(jcode): escape the title separator so the orcad bundle stays ASCII
Usage attribution only knew live worktrees, so deleting one moved its
sessions out of the Orca scope on the next scan and Stats & Usage totals
went down. Remember every worktree Orca has had in a small usage-owned
history and attribute against live plus remembered worktrees, with live
rows claiming reused paths first. The history loads off the main thread,
scans wait for it, and an unreadable or newer file is never overwritten.
* fix(cli): chat wait checks the chat's work state instead of reading its history every second
`orca chat wait` and `orca chat send --wait` polled `agentSession.history` once a second only to
learn whether the chat was still working. Each poll made the host build a transcript page, scan
every retained item twice for the running turn, and send the newest reply's full text, all
ignored by the waiter.
The host now answers `agentSession.workState` with just the facts a wait decides from (working,
a waiting question or approval, queued ids, the next queued send, the fence), and the journal's
running turn comes from its existing per-row turn index instead of a scan. The CLI polls that
read and falls back to history pages on hosts without it. The final transcript read is unchanged.
* test(cli): type the chat wait host test without assertions
* docs(cli): say what a work-state check skips, not that it does no history work
* test(cli): pin the chat wait's exact final reply and its single history read
* docs(cli): name the scan a work-state check skips
* ci: typecheck the chat wait host test with the cross-process test project
* Share account model lists across Settings and launch menus
Use one surface-aware model policy and demand-driven catalog acquisition for Settings defaults and new-agent menus. Preserve literal saved selections, native invocation boundaries, and older-host listing reads.
Co-authored-by: temp_final_v5 <73724370+qq2144@users.noreply.github.com>
* Keep model menus scoped, responsive, and editable
* Keep model menus stable while host listings refresh
Retain applicable listings through refresh failures, preserve host availability metadata, and distinguish unlearned registration from known absence. Show Settings pending choices without blocking discovery, scope the fallback note to failed demand, and register its translations. Verify the structured phone reader and menu wrapper share the composer policy without changing phone presentation.
Co-authored-by: temp_final_v5 <73724370+qq2144@users.noreply.github.com>
* Keep retired model lists out of reopened menus
Keep completed empty and unknown workspace answers in the shared snapshot cache so successor menu owners cannot seed older account or workspace models. Derive observer state from that cache and remove the duplicate owner retirement guard. Extend the lifecycle regression through last unsubscribe, owner replacement, failed reopen and a fresh replacement answer.
* Preserve catalog answers across scope and owner changes
* Reuse unchanged model catalog projections
* Keep new-chat model placeholders scoped to their own catalog
* Use the launched surface’s model catalog in Settings and launch menus
Select protocol sources before applying the shared model-menu policy. Keep Antigravity CLI and Chat answers independent, route discovery through the actual host/runtime, and clear menu-owned effort only on an explicit model-only replacement.
Co-authored-by: temp_final_v5 <73724370+qq2144@users.noreply.github.com>
* Keep paired launch mock clearing out of hook cleanup
Co-authored-by: temp_final_v5 <73724370+qq2144@users.noreply.github.com>
* Bound catalog invalidation epochs by host and agent
* Keep CLI fallbacks out of terminal choices and suppress unchanged listings
* Acquire terminal catalogs only for consumers of that surface
* Restore setup panel explanations
* Reuse settled CLI catalogs in Settings menus as well
* Discover models in the terminal agent execution runtime
* Exercise catalog demand and retire regression fixture observers
* Use the visible draft rather than its default for CLI demand
* Keep discovery runtime fixture independent of Electron paths
* Share effective terminal execution selection with PTY planners
* Separate workspace inventory resolution from launch preparation
* Use read-only worktree projection for terminal inventory selectors
* Preserve PTY context precedence without redundant default-distro reads
* Declare the read-only selector on the runtime construction boundary
* Add terminal model discovery without changing Git discovery routing
* Revalidate held terminal model lists on demand after ten minutes
* Classify legacy model fallbacks from agent probe metadata
* Repair terminal catalog boundary test harnesses
* Refuse foreign execution owners in terminal model discovery
* Resolve model menu validation failures
* Restore terminal model discovery in the new-tab menu
* Repair model menu CI test boundaries and fixtures
* Restore settings read bound across picker generations
* Keep discovery registration and selected-agent admission reliable
* Assert the terminal discovery response envelope after reopening
* Keep model discovery reads and waits in their own phases
* fix: retain model discovery through demand-owned phase transitions
* fix: ignore obsolete model catalog job completions
* Keep Settings model labels through unchanged settings refreshes
* Show idle Settings model labels before opening discovery
* Trim low-value model menu tests
* Move terminal model discovery to its own branch
* Use host model catalog replies directly
* Keep Settings display scoped to its current source
* Assert the saved model displayed text
* Refresh paired launch defaults on reopen and preserve legacy reads
* Narrow merged Settings rows and type the catalog fixture
---------
Co-authored-by: temp_final_v5 <73724370+qq2144@users.noreply.github.com>
OpenCode 2.0.13-2.0.18 submit a bare --prompt before the agent/model
catalog loads and drop it (fixed upstream in 2.0.19). Orca only routed
2.0.12 and 2.0.16 through its startup-prompt plugin, so the other
releases kept the prompt in the composer while the tab showed Done.
Route the whole broken run through the plugin. This also lets model
picks on 2.0.14/15/17/18 deliver their prompt again.
* Keep Git Graph rendering work scoped to visible and appended rows
* Skip graph primitives outside the visible column
* Keep graph viewport callbacks compatible with renderer compilation
* Keep graph scroll restoration tied to the pane owner
* Use typed DOM lookups in the graph viewport test
* Record Git Graph compiler compatibility improvement
* Correct graph retention fixture cleanup and commit boundaries
* Refresh the editor copy hint from owner events
* Document the bundled editor event type refinement
* Prune the removed editor hint interval allowance
A keyboard's mic button switches to a separate voice IME, which closes the keyboard and opens the voice panel about 250 ms later. The page read every Android keyboard close as Back and blurred the field at once, so the voice IME's text had nowhere to go. Blur only once the keyboard stays closed for a second; a reopen within that window keeps focus.
* test: remove 60 low-value cases and orphaned conversion fixtures
* docs(ci): list supported Windows SSH host cells
* test: recognize direct Windows orcad server entry
---------
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
* relay: skip the edge row read for hosts above the edge leave ceiling
With the edge on, every assign of a host outside the cohort ran leaveEdge (a
relay_assignments read) and every resolve ran edgeAssignment, on the director's
3-connection pool, ahead of the in-memory lanes. At 1% this saturated the pool at
peak: acquire timeouts and 503s for GCE hosts, and some cell heartbeats.
New optional edge.json flag leaveCeilingPermille: the highest rollout ever applied.
A host above it, the current rollout and the env percent, on no allow or deny list,
cannot have an edge row, so both reads are skipped. Absent: today's behaviour.
The evacuation sweep reports orca_relay_edge_row_above_ceiling if it finds an edge
row above the ceiling (set too low).
* relay: edge leave ceiling: void a ceiling below the rollout; document operating rules; test reads under it
* fix(terminal): stop workspace activation from opening a fresh tab per orphaned counter-id PTY
Activation adoption minted a new tab with initialPtyId for every unowned
PTY. For bare local counter ids ("3", "13") main never reattaches by id
alone on a non-attach spawn, so each visit started a fresh shell and the
orphan stayed orphaned, producing another empty tab next time.
Counter-id orphans now still try their recorded pane (the attach-only
path that can reattach them); only the fresh-id createTab fallback is
declined and reported via declinedPtyIds. The all-digit check moves to a
shared isLocalCounterPtyId helper used by main and the renderer.
Fixes#40920
Co-authored-by: Neil <neil@stably.ai>
* test(terminal): pin the clock in the orphan counter PTY adoption test
---------
Co-authored-by: Neil <neil@stably.ai>
Persist windowFullScreen on enter/leave-full-screen (frozen once the window
starts closing) and re-enter fullscreen on reveal after the saved maximize,
skipping background launches. Ignore the spurious unmaximize macOS emits
while a launch-maximized window enters fullscreen so windowMaximized and
windowBounds keep the pre-fullscreen state.
Fixes#40510
Co-authored-by: Neil <4138956+nwparker@users.noreply.github.com>
Session History picked each session's workspace chip by matching cwd, so
when several folder workspaces shared one folder every row showed the
first workspace in the list. Prefer the live (non-archived) workspace
recorded in structuredSession.workspaceId on the session's host, and fall
back to the existing cwd match otherwise.
Fixes#41044
Co-authored-by: Neil <4138956+nwparker@users.noreply.github.com>
Picking a split terminal tab from Cmd+J or the tab bar's switch menu
focused the first pane, because the picker already held focus and the
tab-wide focus query fell back to the first xterm textarea. Pass the
tab's stored activeLeafId to focusTerminalTabSurface (and to the paired
host activation) so input returns to the pane that was last active.
Co-authored-by: Neil <neil@stably.ai>
The explorer drops node_modules and .git from every listing page, so a
reveal under them waited for a row that never appeared. The request stayed
pending and auto-reveal ignored later editor tabs.
getRevealTarget now cuts the reveal off at the first folder the listing
filter rejects. A nested hidden folder selects the folder that holds it; one
directly under the root clears the request. Hidden folders are never
expanded or read.
Fixes#41039
Co-authored-by: Neil <neil@stably.ai>
The Orca claude shell function launched Claude inside a ( ... ) subshell.
Bash can keep that subshell as the pane's foreground process, so Orca saw
"bash" instead of Claude. The subshell now unsets the claude function and
execs the binary, leaving Claude as a direct child of the pane shell.
Co-authored-by: Neil <neil@stably.ai>
Factory Droid has no PermissionRequest hook event, so `droid doctor`
flagged the hook Orca wrote into ~/.factory/settings.json as unsupported.
The installer no longer registers it; reinstall drops only the
previously managed Orca command on that event and keeps user hooks.
Approval waits continue to come from PreToolUse and Notification, and
the now-unreachable PermissionRequest listener handling is removed.
Fixes#40607
Co-authored-by: Neil <4138956+nwparker@users.noreply.github.com>
The right sidebar's Activity Bar Position lived only in renderer state, so
choosing Side reset to Top on the next launch.
Persist it with the other right-sidebar UI fields: PersistedUIState, the
paired-client update schema, the default and startup-fallback UI state, the
renderer write baseline and writer, and hydration. Profiles without the field
stay at Top, and hydration maps any value other than 'side' to 'top' so a
corrupt value cannot hide the activity bar. The ActivityBarPosition type
moves to shared ui-chrome-types so the persisted contract can use it.
Keep the field pairing-local for web clients, like sidebarOpen: older hosts
parse ui.set with a strict schema and would reject the whole update, so the
browser strips it from host writes and pins its own value on ui.get. Desktop
persists it through IPC.
Fixes#40887
Co-authored-by: Neil <neil@stably.ai>
Dev-folder plugins are hashed at discovery with DEV_FOLDER_SKIPPED_DIRECTORIES
(e.g. .orca/), but the worker activation integrity check re-hashed the whole
tree. Once Orca wrote typings into .orca/types, the activation hash no longer
matched the reviewed hash and the dev worker refused to start. Pass the dev
flag through to the integrity check so both hashes skip the same directories.
Co-authored-by: Neil <4138956+nwparker@users.noreply.github.com>
The scripted Codex fixture hard-coded /home/dev/.codex as the account
home on every platform. Startup now reads hook configuration from the
account home, so coordinator-worker tests stalled on macOS before the
scripted connection opened. Build the fake account home inside each
test's temporary fixture root and pass that root to every attach caller.
Package identity hashed files in a segment-wise depth-first walk order, so a
file like references/refs.md sorted after references/refs/image.webp. The
manifest validators require complete paths in code-unit order, so such
skills failed with skill-bundle-manifest-path-order. Sort the complete
paths by code unit in both the runtime identity and the build-time manifest
generator, and cover the sibling file/directory layout with a round trip.
Co-authored-by: yukurust <76849725+yshi112358@users.noreply.github.com>
Co-authored-by: Neil <neil@stably.ai>