Commit Graph
20622 Commits
Author SHA1 Message Date
Jinjing 316b1887fd Size tabs to titles and preserve floating panel drag space (#34025)
* Size tabs to titles and preserve floating panel drag space

* Stabilize agent tab layout during activity changes

* Balance tab widths across titles and tab types

* Reserve terminal tab icon space before agent detection

* Run floating header drag E2E in the isolated headful project

* Prevent native text selection on the floating panel drag handle

* Cap expanded tab width at 24rem

* Let tabs expand to fit titles in available space
2026-10-26 16:51:33 -07:00
OrcaWinandOrcaWin 7782fd5171 test: extract WSL host connector fixture to restore lint (#34132)
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
2026-10-26 16:48:52 -07:00
Brennan Benson 1b64adbaad Linux cookie import says when secret-tool is missing instead of blaming the keyring (#34099)
* fix(browser): report why Linux cookie keys cannot be read

* test: cover cookie warning forwarding across import hosts

* test: place wire fixture cast rationale at assertion start

* fix: declare Linux cookie import warning translations
2026-10-26 16:32:50 -07:00
Brennan Benson 823ca6870f fix(settings): show cookie import as available before skill setup (#34097) 2026-10-26 16:27:42 -07:00
Jinwoo Hong c1198d2f41 refactor(connector): the desktop takes Discord and Linear conversations as well as Slack (#33927)
The desktop's connector accepts conversations from Slack, Discord and Linear and lists all three sources in its hello; per-source details (the Sent from line) come from one table. Nothing changes until those adapters are configured; behind the experimentalConnectors setting.
2026-10-26 19:25:54 -04:00
Neil 0b30b284c6 fix(terminal): keep ConPTY's viewport top through a width change (#34061)
* fix(terminal): keep ConPTY's viewport top through a width change, checked against a captured transcript

A captured ConPTY 1.23 resize (wsl.exe) shows it keeps the line at the top
of its viewport through every resize and repaints only that viewport. xterm
keeps the cursor's rows instead: a wider grid that rejoins wrapped rows pulls
rows out of scrollback (ConPTY's repaint then overwrites them), and a
narrower one that rewraps pushes rows into it (the repaint then repeats
them). The windowsPty row rule covered neither. ConPTY-backed emulators now
put the top line back on its row after a resize.

* fix(terminal): ConPTY resize correction respects unfinished escapes and history replay

- Skip the widen correction while the parser is inside an escape sequence,
  so a resize landing mid-SGR/OSC no longer aborts the app's sequence.
- Skip it when an app set a scroll region.
- Replay daemon history (cold restore from log, durable rebuild) with the
  live emulator's ConPTY model, so replayed and live screens agree.
- Keep the saved cursor with its text when rows come back on narrowing,
  and never drop a background-coloured blank row.

* fix(terminal): replay a saved log with the resize model of the daemon that wrote it

- A daemon now stamps resizeModel into each session's meta; the history reader uses the ConPTY
  replay model only for a stamped session and keeps xterm's for one an older daemon recorded.
- Fix the DECSC adjustment: xterm keeps savedY absolute, so popping a blank row already keeps
  DECRC on its text; the old +1 sent it to the top row.
- Tests: narrow-direction replay, older-daemon replay, DECSTBM skip, DECSC/DECRC after narrowing,
  a background-coloured blank row kept.

* fix(terminal): take the history resize model from the daemon hosting the session

Main writes history and rebuilds durable checkpoints, but a daemon outlives an app update, so
main's own code is not what the live emulator ran. The daemon now reports its resize model in
hello (older daemons omit it, meaning xterm's); main stamps it into meta on open, restamps it
when a checkpoint starts a fresh log, and rebuilds durable history with it. The client's token
read moved to its own module to keep client.ts under the line limit.

Also clamps a saved cursor (DECSC) on a popped row to the new bottom row, as xterm's reflow does.

* fix(terminal): a disconnect leaves the history resize stamp alone

The client keeps the last daemon's reported model through a disconnect (the next hello replaces
it); undefined, before any daemon has answered, now means unknown and skips the restamp instead
of reading as an older daemon. Tests: a disconnect mid-commit keeps the stamp, and a Sleep-cache
wake onto a newer daemon restamps with its first checkpoint (#34060).

* fix(terminal): read the rebuild's resize model through the history manager

The durable rebuild called client.getDaemonResizeModel() in the checkpoint path, which tests that
fake the client with only request() could not answer, so the rebuild fell back to the live
snapshot. The history manager already holds the hosting model's provider; the rebuild reads it
there, keeping the checkpoint path's client use to request().
2026-10-26 16:21:36 -07:00
Kelvin Amoaba d1f6f6ac83 fix(mobile): resume history sessions with desktop's resume and host rules (#33943) 2026-10-26 23:18:59 +00:00
NeilandClaude 923bea9269 fix(files): open host files outside workspaces for any client with terminal access (#33958)
* fix(files): open host files outside workspaces for any client with terminal access

Paired clients that can open terminals on a host can already read and write
anything its user can, so the per-terminal provenance gate on files outside
workspaces protected nothing. The host now grants any existing file outside
its workspaces; older hosts get a clear update message instead of a refusal.

Co-Authored-By: Claude <noreply@anthropic.com>

* fix(files): refuse SSH, device and WSL-home paths instead of misreporting them

Co-Authored-By: Claude <noreply@anthropic.com>

* perf(files): size grant digests to the file and skip status checks for local fallbacks

Co-Authored-By: Claude <noreply@anthropic.com>

* fix(files): read procfs files whose stat reports size 0

Co-Authored-By: Claude <noreply@anthropic.com>

---------

Co-authored-by: Claude <noreply@anthropic.com>
2026-10-26 16:18:09 -07:00
Neil 95ffa4fcce fix(wsl-host): a cold wake that loses orcad recovers by itself instead of leaving a dead pane (#33147)
* fix(wsl-host): a cold wake that loses orcad recovers by itself; stopped-distro refusals stay final

* fix(wsl-host): identity and pairing refusals stay final; no second wake after a stop; settling is retryable
2026-10-26 16:17:38 -07:00
Brennan Benson ca8eb2904e feat(orchestration): add a Settings switch to turn worker heartbeats off (#34070)
* feat(orchestration): add a Settings switch to turn worker heartbeats off

Dispatched workers are told to send a heartbeat every 5 minutes. A new
"Worker heartbeats" switch under Settings > Agent Orchestration (on by
default) lets users turn that off: newly dispatched workers are no longer
told to send heartbeats, and the stale-heartbeat check is skipped.

The interval the brief states and the stale check both derive from one
resolver over the live setting, read from the runtime's own store like
the other orchestration settings.

* Test heartbeat preferences across settings and worker dispatch

* Keep focused heartbeat preference contracts

* Explain partial runtime fixture assertion

* Correct CLI integration fixture contracts
2026-10-26 16:16:12 -07:00
Jinwoo Hong d5ac6ebbe4 fix(connector): one turn id from the host's stamp everywhere (#33909)
The host's turn-start timestamp is the only turn id the connector uses: snapshots, turn ends and replies all carry it, and the desktop's separate turn cache is gone, so they can no longer disagree. The unused turn-bound cancel was removed (Stop is parked). The hook server reads the main agent state through the same shared accessor.
2026-10-26 19:11:29 -04:00
Neil ccedfe312e fix(ssh): move enabled SSH automations to the host's Orca server (#34044)
* fix(ssh): move enabled SSH automations to the host's Orca server

Connecting an SSH host moves its saved state to the host's managed Orca
server. An enabled SSH automation refused that move on every Connect
("automations (1), automation runs (4)"), leaving the host unconnectable;
Move anyway connected it but stranded the automation on the desktop, where
it no longer ran.

An enabled automation whose runs have all finished now moves with its run
history. The manifest still carries it disabled, which every server version
accepts; once the move commits the desktop disables its retained copy and
turns the server's copy back on through automation.update, re-sending its
start time so the next run is the next future occurrence. A server that
can't is noted in Settings; an unreachable one is retried on the next
Connect. While a move fences the host, the desktop scheduler, Run now and
the launch re-check write nothing for its automations, so a tick can no
longer break the fenced export; releasing the fence resumes them. A run
still in flight keeps blocking and the refusal now says to wait for it.

Fixes #29083

* test(ssh): mock the server automation enabler in the delta-move handler test

* test(e2e): keep the Move anyway specs refusing now that enabled automations move

The inline Move anyway spec seeded an enabled automation to force a
refusal, which this branch now moves instead. It seeds one pinned to an
earlier registration of the host, which still stays behind. The relay
bridge spec's Move anyway lookup also matched the refusal toast's
button since #34041; it now takes the pane's own.
2026-10-26 16:11:06 -07:00
NeilandClaude e630f27940 test(terminal): a pinned parked tab's process exit asks first, then closes as a pty-exit (#34121)
Co-authored-by: Claude <noreply@anthropic.com>
2026-10-26 16:09:39 -07:00
OrcaWinandOrcaWin ebeb677943 test: remove 30 low-value cases and seven suites (#34120)
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
2026-10-26 16:08:54 -07:00
Jinwoo Hong 22185818c8 test(connector): freeze the shipped connector schema behind an upgrade test (#34115)
Freezes the connector's shipped table definitions: later schema changes must be additive statements. Adds a baseline fixture and an upgrade test (baseline, then current schema, compared with a fresh database on SQLite and Postgres), plus the statement-shape check relay already uses. No runtime change.
2026-10-26 19:08:29 -04:00
NeilandClaude 0fef4a8ce6 feat(wsl-host): start a WSL host's distro when one of its automations comes due (E9 B) (#33839)
* feat(wsl-host): start a WSL host's distro when one of its automations comes due

E9 connect policy, part 2. A WSL host's automations run inside its distro, so a
distro that is off (a reboot, an idle release) missed them. While a host is connected
the desktop now reads its enabled automations' next run (on connect and every 15 min)
and keeps the soonest one per host in userData. When that time comes with the host off,
it boots the distro once, and orcad's startup catch-up fires the run within its missed-
run grace. A run due while the computer was off fires once Orca starts. Nothing wakes
past the grace window, and a connected host is left to its own scheduler.

Co-Authored-By: Claude <noreply@anthropic.com>

* test(wsl-host): a due automation boots a parked host once, never with WSL hosts off

Co-Authored-By: Claude <noreply@anthropic.com>

* fix(wsl-host): keep the following run, and forget changed automations (E9 review)

Review of #33839:
- A run handled while connected dropped the host's next due time. The wake now keeps
  each host's enabled schedules and computes the following run locally whatever
  happens to this one (wake failed, past grace, handled by the host), and re-reads the
  real one from a connected host.
- A deleted, disabled or rescheduled automation kept waking the distro at its old
  time. A successful automation.create/update/delete from this desktop now re-reads the
  host's automations, as do the 15-minute re-read and every connect. Nothing boots a
  distro to check: on wake, a distro already running is just reconnected.
- wakeForAutomation/isConnected live here now (moved out of #33838); isConnected reads
  the host's reachability, never booting.

Co-Authored-By: Claude <noreply@anthropic.com>

* refactor(wsl-host): say isConnected answers for this process; keep the service in bounds

isConnected reports whether the host answers through this process; false is not
"stopped" (a fresh process has no bridge yet, and the wake just connects). The
service's quiet record read moves beside the other record helpers so the file stays
within its line limit after the E9 additions.

Co-Authored-By: Claude <noreply@anthropic.com>

* refactor(wsl-host): give the connector contract its own file; one wake path for focus and automations

After rebasing onto #34063, #34093 and #33110 the WSL host service was over its line
limit. The connector contract (what the service drives) moves to
wsl-host-connector-contract.ts, re-exported from the service, and the focus entry and
the automation wake share one private wake step: lift the park, then reconnect unless
the host answers, read with #33110's focusReachability so neither pays a WSL round trip
when this process has no bridge yet. An automation wake no longer reconnects a host
that already answers.

Co-Authored-By: Claude <noreply@anthropic.com>

* test(wsl-host): an automation wake with no bridge skips the reachability probe

Co-Authored-By: Claude <noreply@anthropic.com>

---------

Co-authored-by: Claude <noreply@anthropic.com>
2026-10-26 16:07:16 -07:00
Brennan Benson f06f737802 Unify Source Control action permissions and card layout (#30449)
* Source control actions start chats and terminals on their saved model

A "start an agent" action's model lived only in free-text CLI arguments, which a native chat
never reads, so AI Fix opened a chat on the default model. Each action now saves a structured
model and effort that both routes apply: chat create options, or the agent's own flags in a
terminal (winning over the same flag in CLI arguments). Desktop, dialog, fix-checks and mobile
launches carry it; Settings rows get Model/Effort selects and the CLI arguments field says it is
terminal-only.

Tracked in STA-11102.

* Name the model in the repository override note

* Type the dialog's model hand-off; keep Agent in English in Japanese copy

* fix: preserve action chat model choices through launch

* Preserve action selection ownership across chat launches

* Keep terminal host contract fixtures aligned with preflight

* fix: wait for action Settings agent inventory

* fix: consolidate direct agent routing imports

* fix: use standard action option labels

* fix: align action launch contracts with shared types

* fix: sync action option localization metadata

* test: provide action Settings inventory in mounted fixtures

* Keep action options row height stable while loading

* Let each Source Control action choose its chat permission mode

An action's saved chat choice may now carry a permission mode, with or without a model;
"Same as new chats" saves nothing. A model is replaced only when the action names one,
so a permission-only choice keeps the chat's remembered model and options.

* fix(native-chat): leave older hosts their own permission mode and keep action options readable

- An action's saved permission mode is sent only to hosts that advertise
  agentSession.create.options-mode.v1. Older hosts get no mode, in create
  options or a later setOption, so the chat starts on that host's new-chat
  default, as a phone launch to such a host already does. Hosts from
  1.4.225 to 1.4.227 refused a mode their tables lacked (OpenCode, Grok,
  OMP), leaving the action unable to start.
- Settings action rows give Model and Permissions full rows in the options
  column so saved values are readable; the loading placeholder reserves the
  same rows.
- Remove two unused locale keys; fix two stale comments.
- Tests: the older-host create carries no permission mode; a permission
  mode picked alone keeps the remembered model on an acquired create.

* fix(settings): reserve one options row while loading an action with nothing saved

Terminal and permissions-only rows no longer shrink when loading ends; a chat
agent with a model list may grow by its Model row once known.

* fix(native-chat): keep the create options mode a checked literal type

* fix(settings): share verified action option fields

* fix(settings): keep action selectors on standard typography

* Keep the launch files under their length limits after the main merge

The structured route imports its result types where they are defined, and the two older-host
action-launch tests share one setup helper.

* One action settings section for chat and terminal launches

A Source Control action's Model, model options and Permissions now apply whether it opens a
chat or a terminal; terminals receive them as the agent's own flags, and a repository's own
CLI arguments keep the flags it sets. Extra CLI arguments stay terminal-only.

* fix(source-control-ai): one terminal projection for saved action choices

Ask in a terminal now states its permission instead of leaving it to the
user's own config: Claude and Grok pass --permission-mode default, Codex
passes -a on-request -s read-only -c approvals_reviewer="user" (the
interactive CLI has no untrusted policy, so a read-only sandbox is what
asks before edits). Agents whose CLI has no flag for a mode show the
existing "Applies to chats only" hint.

The strict launch-preferences projection now requires the launch agent at
every caller, composes model ids through the resolver's own step, carries
a mode only where the agent's terminal has a flag for it, and the local
string wire keeps booleans as 'true'/'false', so Cursor Thinking/Fast reach
the terminal and an OpenCode permission-only choice is not refused.

The argument parser knows flag arity, so removing a boolean permission
flag keeps other options' values, following positionals and '--'.
Pre-admission and executor share one terminal admission check on the
options the terminal will receive. Customize with Save launches the recipe
as it will resolve once saved; legacy partial repository overrides are
edited as the complete recipe they resolve to. Empty Extra CLI arguments
start collapsed.

* fix(source-control-ai): an edited repository action saves complete

Every Settings edit of a repository action (agent, model, permission,
prompt or arguments) now starts from the complete recipe the action
resolves to, whether its stored override is owned or a legacy partial.
The resolved agent selection is kept (never an agent only detected to run
a default), an explicit null args clear stays null, and empty args stay
empty instead of being dropped. Clearing the last preference therefore
means the action agent's own defaults rather than re-inheriting Global.

The action text draft is lossless: unset or cleared prompt and args stay
so until the user types, and the inputs show them as empty, so saving a
prompt no longer writes empty args that suppress the agent's default
flags. Untouched sibling actions are not rewritten by the edit.

* fix(settings): style the Extra CLI arguments toggle through Button's own variant and size

CI's changed-code quality check refuses restyle classes on Button and
CollapsibleContent. Use the ghost variant at size xs with a margin, and
put the content spacing on a plain inner wrapper.

* fix: keep saved action and restart launch recipes consistent

* fix: describe inherited arguments and chat-only permissions accurately

* test: check repository action settings fixture type

* test: map saved action options into terminal compiler inputs

* fix: retain saved action controls during agent detection

* fix(i18n): retire obsolete Portuguese action labels

* test: align folder launch fallback mock with outcome export

* fix: carry resolved connector launch intent and mode together

* test: pin shared action launch branches to recorded agent output

* test: preserve saved source control choices through detection and migration

* test: align launch fixtures with integrated result contract

* test: retain recipe and restart contracts after main integration

* Unify Source Control action permission settings

* Keep native Ask copy with its owning change

* Preserve action drafts and old-host permission intent

* Consume rejected Source Control action saves

* Follow the moved Settings persistence fixture

* Keep permission integration contracts in the cross-version test project

* Include the action permission inheritance label in English catalogs

* Align launch contracts with shared permission recipes

* Keep Source Control action controls within their Settings columns

* Use primitive variants for compact action settings controls

* Show action arguments only for terminal defaults and widen recipe rows

* Apply terminal-only action arguments visibility to repository overrides

* Align action permission control with model controls

* Use shared settings label for action permissions

* Hide action model controls until argument migration ships
2026-10-26 16:01:56 -07:00
Jinwoo Hong aec426c2fa feat(connector): Discord adapter on the shared connector core (#34100)
Adds Discord as a second connector adapter on the shared core: signed interactions for answer buttons, one gateway worker (same image, single leader by database lock, commits on the lock's connection, checkpoints for resume), thread posts through the shared post queue, owner-only control, and teammate context only from linked accounts. Inert until the Discord settings are configured. A narrow gitleaks allowlist entry covers connector Discord env var names in config errors.
2026-10-26 19:01:05 -04:00
NeilandClaude 1d1c6da582 fix(terminal): a parked local tab whose process exits closes as a pty-exit, not a user close (#34083)
The parked watcher passes only hostCloseReason 'pty-exit' (so the pinned
guard still applies), and the local branch then let closeTab default the
reason to 'user': a process exit wrote a user tombstone and retired the
session. The local close now carries the pty-exit reason.

Co-authored-by: Claude <noreply@anthropic.com>
2026-10-26 15:56:28 -07:00
Jinwoo Hong ccfe30a05f feat(connector): Slack-started agents can reply in their thread (orca connector reply, local only) (#33855)
A connector-started agent is told it can answer in its thread with orca connector reply --text; the desktop posts the reply through its Orca Cloud connection, naming the conversation and turn, so the machine never holds a Slack token. Works for agents on this machine; elsewhere the command answers that replies aren't available from this host yet, and the turn's final message is still posted when the turn ends. Behind the experimentalConnectors setting.
2026-10-26 18:55:05 -04:00
Neil 01fea97cde refactor(mobile): group native chat options and queued editing (#34074)
* refactor(mobile): group native chat options and queued editing

* refactor(mobile): use a concrete type import in the recording adapter
2026-10-26 15:53:50 -07:00
Neil 067c614764 fix(orcad): use the app's bundled agent-browser driver for orca serve (#34111)
* fix(orcad): find the app's bundled agent-browser driver for orca serve

Desktop orcad templates omit the driver for size, so orcad materialized from an
installed app reported driver_missing with ORCA_BROWSER_EXECUTABLE set. orca serve
now hands orcad the app's resources copy via ORCA_AGENT_BROWSER_DRIVER; the
slot's own driver still wins for standalone artifacts.

Fixes #33846

* test(serve): expect the app's agent-browser driver handed to orcad

* fix(serve): run a profile copy of the driver on Windows so app updates stay replaceable

* fix(serve): never lend the installed Windows driver when staging fails

* fix(serve): keep another launch's in-progress driver copy

* refactor(serve): share claimed snapshot publication for the Windows driver copy
2026-10-26 15:50:05 -07:00
Jinwoo Hong d4544c831d test(relay): wait for the relay's own close before confirming a resume (#34117)
The served-relay blackbox test closed the phone and data sockets from the client and sent the resume confirm before the relay had processed the close, so on a busy runner the relay correctly answered device-resume-confirmed and the test failed (about 1.8% under load). The test now closes only the phone and waits for the relay to close the data leg with 4408, which happens in the same step that marks the connection inactive. Test-only.
2026-10-26 18:47:27 -04:00
Neil 73ede0fbed fix(terminal): keep a brand-new remote pane's typing for the terminal it creates (#33859)
* fix(terminal): keep a brand-new remote pane's typing for the terminal it creates

* fix(terminal): new-pane typing goes only to a genuinely fresh create, never an adopted or restored terminal

* fix(terminal): decide a new pane looked blank at connect; at bind re-check only what the create can't cause

* test(terminal): replayed history from the real restore path drops a new remote pane's typing

* fix(terminal): type the replayed-history marks by xterm Terminal
2026-10-26 15:46:50 -07:00
BrantandNeil 3f256ad4d5 fix(browser): keep annotate session alive across iframe loads (#24032)
did-start-loading fires for subframe loads too, so a page that reloads an
iframe on each poll invalidated the annotation document every cycle: the
pending card closed, grab mode was cancelled and saved-note markers were
retired. Main-frame did-start-navigation already invalidates for every
document replacement (including same-URL reloads) and same-document
navigation, so drop the did-start-loading handler and move the overlay
viewport reset next to that invalidation.

Fixes #23988

Co-authored-by: Neil <neil@stably.ai>
2026-10-26 15:45:34 -07:00
NeilandClaude a97c7ab7d5 fix(terminal): a WSL bridge pane whose distro went away keeps its tab and cold-restores (#34095)
* fix(terminal): a WSL bridge pane whose distro went away keeps its tab and cold-restores

wsl --terminate (or a shutdown or crash) exits every live bridge pane with an
ordinary code, so Orca closed those tabs as if the shell had exited, and the
next launch opened new sessions instead of restoring the old ones. A proven
exit of a WSL bridge session now checks the shared, coalesced
wsl --list --running (never boots, bounded); if the distro is confirmed gone
it is host loss: code -1, history left unended, tab kept, exactly as after a
daemon crash. A running distro or an unanswered check leaves the exit as is,
so  still closes the tab. Native and SSH sessions are untouched.

Co-Authored-By: Claude <noreply@anthropic.com>

* fix(terminal): trust only a running-list probe that started after the exit; close a kept tab's history

Review of the WSL bridge distro-loss check:
- A probe already in flight from before the exit can predate the distro's
  boot, so it could call a user's own quick exit host loss. Only a probe that
  started after the exit answers; one fresh probe is chained after an older
  in-flight one and shared by the whole wave.
- The outer bound drops to 3 s: every bridge exit waits on it.
- Closing a kept tab later hit SessionNotFound before removeSession, leaking
  its history; an explicit close now treats that as already stopped.

Co-Authored-By: Claude <noreply@anthropic.com>

* fix(terminal): only a session this adapter lost to its distro may close as already gone

Swallowing SessionNotFound for any id could remove the history of a session a
legacy daemon (sharing the history dir) still runs. The adapter now records
the sessions it turned into host loss, clears them on respawn or close, and
swallows SessionNotFound on an explicit close only for those.

Co-Authored-By: Claude <noreply@anthropic.com>

---------

Co-authored-by: Claude <noreply@anthropic.com>
2026-10-26 15:44:35 -07:00
OrcaWinandOrcaWin b8c596ea88 test: remove 68 low-value cases and 18 suites (#34112)
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
2026-10-26 15:43:25 -07:00
Kelvin Amoaba d7a8bb9240 fix(mobile): show the diff when tapping a changed file from a session (#34073) 2026-10-26 22:42:11 +00:00
Brennan Benson ffb7561f04 Stop hidden chats re-rendering on every tab change (#34020)
* perf(native-chat): stop hidden chats re-rendering on every tab change

Skill discovery now subscribes to tab and workspace state only while the
slash/skill picker is open, and the per-chat image owner subscription
reads only its own workspace's tabs. Previously every mounted chat
re-rendered and rescanned the tab maps on any tab change anywhere.

* Resolve native chat image context from its selected owner

* Cover selected chat image owners through preview consumers

* Use typed reads in chat subscription performance fixture

* Key chat subscription probes by fixture chat identity

* Type dense chat subscription measurement results

* Name the read-only floating chat resolver view

* Exercise document markdown in selected-owner preview test

* Check unavailable chat image through its preview dialog
2026-10-26 15:41:53 -07:00
Jinwoo Hong d4a5609d30 refactor(connector): provider-neutral connector core with Slack as its first adapter (#34088)
Moves routing, machine choice, held starts, the post queue, prompt cards and owner controls out of the Slack files into a provider-neutral connector core, with Slack as the first adapter behind one adapter type. Conversation records and delivery ids are keyed by source, so Slack and Discord ids cannot collide. Behaviour-neutral for Slack apart from a slack: delivery-id prefix and a 403 (not 404) from the reply route when Slack is off. Staging's connector database is reset after deploy.
2026-10-26 18:41:17 -04:00
moonrailgunandNeil 037cf27429 fix(codex): show live usage on the active account row, including System default (#20842)
The Codex switcher only rendered usage bars on inactive account rows from
the per-account cache, so the active row (and System default, which never
has a managed account id) showed nothing. Render the live Codex usage on
the active row when this desktop owns the accounts; a remote owner's usage
belongs to that host's target and stays off desktop-selected rows.

Co-authored-by: Neil <4138956+nwparker@users.noreply.github.com>
2026-10-26 15:40:01 -07:00
zhangxaochenandKelvin Amoaba 8291297b0b fix(mobile): recover terminal input lease on attach and preserve picked file names (#32987)
Co-authored-by: Kelvin Amoaba <97001695+AmoabaKelvin@users.noreply.github.com>
2026-10-26 22:34:31 +00:00
NeilandClaude 8a001a93c4 fix(runtime): a restored host pane resumes its agent from the hook store, never replays the launch (#34054)
* fix(runtime): a restored host pane resumes its agent from the hook store, never replays the launch

When a WSL host's daemon restarted, the host re-created each pane with its
original launch command (a fresh Codex conversation), or a plain shell for an
agent typed into one: orcad has no resume record, because only layout-owner
builds record hook status. A pane with no record now resumes the conversation
its own hook rows name (local rows only, this workspace's), through the same
pane-owned resume path a recorded session takes.

Co-Authored-By: Claude <noreply@anthropic.com>

* test(runtime): hook-store resume vetoes: other worktree, two sessions, shared or live elsewhere, structured host

Co-Authored-By: Claude <noreply@anthropic.com>

* fix(runtime): a vetoed hook-store resume launches the tab's agent fresh, as before

A record read from the hook store is no promise to keep: when it is vetoed
(two sessions, shared or live in another pane, no resume command) the tab's
agent now launches fresh as main did, not a plain shell. Its two-session veto
counts only the rows it was read from (local, this workspace), so a relayed
SSH row no longer vetoes a local resume.

Co-Authored-By: Claude <noreply@anthropic.com>

---------

Co-authored-by: Claude <noreply@anthropic.com>
2026-10-26 15:31:05 -07:00
OrcaWinandOrcaWin 86a75e99c6 perf(bench): measure startup memory and cold SSH latency (#33912)
* perf(bench): separate historical startup loading evidence

* fix(bench): retry owned root identity before teardown

* fix(bench): format survivor identities explicitly

---------

Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
2026-10-26 15:29:32 -07:00
Mkjung GithubandNeil 4a8cb6fc71 fix(terminal): keep legacy bash prompt dispatch out of OSC 133 command start after a DEBUG trap change (#29165)
On bash <= 5.0 the PROMPT_COMMAND is a single scalar string. After the
user changed the DEBUG trap at the prompt (`trap - DEBUG`, `trap ':' DEBUG`),
Orca's preexec never saw the status-capture command, so the legacy wrapper
flag stayed unset and the dispatch tail emitted OSC 133;C before the next
prompt was drawn.

Set __orca_in_legacy_prompt_wrapper directly in the PROMPT_COMMAND string,
and re-arm the Orca DEBUG trap at the top level of that string: bash <= 4.3
(including macOS /bin/bash 3.2) restores the caller's DEBUG trap when a
function returns, so the re-arm inside __orca_finish_legacy_prompt_dispatch
was undone. Tests force the legacy dispatch on any bash and also run with
/bin/bash on macOS.

Fixes #29164

Co-authored-by: Neil <neil@stably.ai>
2026-10-26 15:28:41 -07:00
Jinwoo Hong 1a723194c3 chore(native-chat): delete the orphaned duplicate structured chat pane menu (#34086) 2026-10-26 18:28:10 -04:00
Kelvin Amoaba 86f2f24ddc feat(mobile): open PDFs from the file browser in Quick Look or the system viewer (#33771) 2026-10-26 22:26:58 +00:00
Neil b58513a049 test: import mocked-module graphs one at a time after vi.mock (#34103)
Same Vitest registration race as the daemon-init fix: concurrent first imports
can load dependencies before pending vi.mock/vi.doMock calls are registered.
2026-10-26 15:26:32 -07:00
NeilandClaude c2c545f245 fix(wsl-host): no-boot connects stay quiet, and liveness recovery never boots (E9 follow-up) (#34093)
* fix(wsl-host): no-boot connects stay quiet, and liveness recovery never boots (E9 follow-up)

Two lows from the #34050 review:
- A no-boot connect published "Connecting" before its running-list read, and a quiet
  refusal then left the row on "Connecting". It no longer publishes the pending state.
- Liveness recovery reconnects only after confirming the distro runs, but that read
  could go stale before the reconnect spawned anything. Recovery now passes the same
  running check to the connection manager, which re-reads it right before spawning.

Co-Authored-By: Claude <noreply@anthropic.com>

* fix(wsl-host): a no-boot recovery connect still publishes its own pending status

Only the default "Connecting" is skipped for a no-boot connect; an explicit status
(liveness recovery's "retrying now") is still published.

Co-Authored-By: Claude <noreply@anthropic.com>

---------

Co-authored-by: Claude <noreply@anthropic.com>
2026-10-26 15:25:30 -07:00
NeilandClaude 268f3d3af8 fix(wsl-host): a clean watch or holder exit is settled like a failed one (E9) (#34063)
`wsl --shutdown` can end the watch and holder with code 0. Two places only reacted
to a failed exit:
- the settle window that keeps a poll from reconnecting into a stopping distro;
- the liveness run's 500 ms settle and running-list re-read before the verdict.
On a clean exit the run read a possibly stale list that still showed the distro,
and readIdentity then exec'd wsl.exe into it, booting it again. Both now use one
"any watch or holder exit" predicate.

Co-authored-by: Claude <noreply@anthropic.com>
2026-10-26 15:25:24 -07:00
Neil ad5f787ad0 chore(process-host): drop the WSL hook relay launcher from the direct-import baseline (#34078) 2026-10-26 15:24:14 -07:00
Neil 26b158d7bd fix(browser): delete a removed server's browser folder on the next start, not while loaded (#33280)
* fix(browser): delete a removed server's browser folder on the next start, not while loaded

Removing a server (or an SSH target, or evicting a binding) cleared the partition through
Chromium, which loads its session, then deleted the folder right away. On Windows the loaded
session keeps files open, so the delete failed with EBUSY half-way. The data is still cleared
through Chromium at once, but the folder is now queued and deleted on the next start, before
any session loads; startup orphan collection no longer loads the sessions it deletes.

* fix(browser): keep deferred partition deletes per profile and inside Partitions

The pending-delete list now lives next to the active profile's binding file,
so one profile never deletes a folder another profile bound again. Listed
paths must resolve strictly inside the Partitions folder before a recursive
delete, and bound-folder checks fold case for Windows paths.

* fix(browser): re-check bindings before each deferred partition delete

Read the bindings again for every pending folder so a partition bound while
an earlier delete was awaiting is never removed, and keep folders queued
during the startup pass.
2026-10-26 15:23:02 -07:00
Neil ba85f1a6f3 fix(main): share one window listener across overlapping requests to stop MaxListeners warnings (#33102)
* fix(main): share one window/WebContents listener across overlapping requests

Per-request lifecycle watchers (renderer-gone aborts, tab-close relays,
project-move pause, SSH-access link, Jira summary, workspace-cleanup scans)
each added their own destroyed / render-process-gone / did-navigate /
closed listener to the long-lived main window. They were removed on
settle, but with a dozen remote-runtime subscriptions or tab closes in
flight they stacked on top of the window's permanent listeners and tripped
MaxListenersExceededWarning.

addFanoutListener keeps one native listener per (emitter, event) and fans
out to a callback set, detaching when the last subscriber releases.

* test(fs-watcher): await watcher conditions instead of sleeping

* test(window): one lifecycle event rejects every overlapping close request
2026-10-26 15:22:58 -07:00
Neil 39b390516e fix(terminal): save a woken terminal's first history as a full snapshot (#34060)
* fix(terminal): save a woken terminal's first history as a full snapshot

A wake that reused the Sleep-time cold-restore cache reopened the history
writer without asking for a full checkpoint, so the new process's output was
appended to the pre-wake checkpoint, which lacks the fresh-shell padding the
seed gave the daemon. The next save that replayed checkpoint + log (quit's
final save, or a relaunch's adoption) printed the new shell's prompt on the
restored one's row (`$ $`). Mark a full checkpoint for a new process in that
path, as the uncached cold-restore path already does.

* test(terminal): drive the periodic save through a test subclass instead of a cast
2026-10-26 15:21:50 -07:00
d2f9617615 fix(omp): stop finished subagents holding the pane on working and name child rows (#29263)
Co-authored-by: Kien Le <122910950+kien-ship-it@users.noreply.github.com>
Co-authored-by: Kelvin Amoaba <97001695+AmoabaKelvin@users.noreply.github.com>
2026-10-26 22:20:16 +00:00
ad2156c358 test: remove 140 low-value cases and 49 suites (#34062)
* test: remove 140 low-value cases and redundant browser probes

* fix: remove unused upstream chat menu import

* test: pin the host-split layout fixture branch

---------

Co-authored-by: Orca Test Audit <test-audit@stably.ai>
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
2026-10-26 15:16:27 -07:00
Neil 7423c8c6e1 fix(automations): settle a run on the agent's own done when its screen never reads idle (#34096)
A Claude Code that negotiates OSC 7501 drops its title glyph, so after a stream
gap or a runtime restart main holds no rest evidence for the finished pane and
tui-idle never settles. Runs then sat dispatched for 6h. A turn-end done
reported after dispatch that has stood for 30s, with no row of the pane saying
otherwise, now completes the run; a blocked screen still resolves first.

Fixes #34064
2026-10-26 15:15:52 -07:00
Neil 9bfabff0ca fix(runtime-environments): drop a recipe VM's rows and session partition when cleanup forgets its server (#33805) (#34101)
Recipe cleanup removed the saved server without the retirement a Settings
removal runs, so the host's session partition stayed (listings kept it
under omittedHostIds) and the sidebar kept the VM's primary checkout until
the next catalog read. Cleanup now retires the server through the same
routine as a Settings removal, the renderer re-reads the catalog once
cleanup returns, a catalog read that started before a change is followed
by one more, and registry edits made outside Settings (CLI environment rm,
recipe cleanup) also drop the removed host's session partitions.
2026-10-26 15:14:23 -07:00
Neil 7a5df406f5 perf(wsl-host): focus connects without first probing WSL when no bridge exists yet (#33110) 2026-10-26 15:13:14 -07:00
Rongzheng LiuandRongzheng Liu b2270cd184 fix(usage): include GPT-6.1 Sol in Codex cost estimates (#29707)
Price gpt-6.1-sol (and its effort/suffix variants) at its own base and
long-context rates instead of leaving it unpriced.

Co-authored-by: Rongzheng Liu <tianlrz@users.noreply.github.com>
2026-10-26 15:11:00 -07:00