* fix(tabs): a session's own name replaces a quick-command tab name
* fix(tabs): only a session's own name replaces a quick-command tab name
Session titles now say whether they are the session's own name (a rename
or a provider-generated name) or a stand-in such as the first prompt. A
quick-command tab keeps its label until the session has a name; a name
typed on the tab still wins. Titles from older hosts and saved tabs with
no kind keep the label; old saved titles are asked for once.
* fix(tabs): classify History-cached titles for session-id-only title requests
* fix(tabs): keep a cached session title when its transcript cannot be reread
* fix(tabs): keep a session title when its classification reread fails
* fix(tabs): keep the transcript for an unclassified cached session title
* test(tabs): keep the cached-title fixture's agent literal
Rewinding to a Claude local command (e.g. /usage) cut the fork at the
command row's parent, which is Claude's isMeta <local-command-caveat> row.
The fork then ended on the caveat, so the next prompt was read as the
local command and Claude replied "No response requested." Cut at the
caveat's parent instead.
Fixes#38686
* fix(serve): keep `orca serve` running while it probes the login shell
`orca serve` started from an interactive terminal stopped itself ("[1]+
Stopped") before printing its pairing link. orcad inherits the terminal
and probes the login shell with `$SHELL -ilc`; an interactive bash 5 or
zsh takes the terminal's foreground job, so orcad's next terminal access
raised SIGTTOU/SIGTTIN. Give both shell probes (login environment and
PATH) a POSIX session of their own so they never hold a controlling
terminal. Windows keeps attached spawns, where `detached` would open a
console.
Refs #38347
* fix(serve): end a detached shell probe with its owner and on timeout
A probe in its own session no longer receives the terminal's Ctrl+C or
hangup, so a hung rc could outlive `orca serve`. Kill the probe's process
group by its own pid when it times out and when its owner exits while it
still runs; orcad and Electron turn INT/TERM into an exit, so a Ctrl+C
reaches it that way. No signal listeners: one would replace Electron's
graceful signal quit. The timeout now also ends what the rc started, not
just the shell.
Refs #38347
* Open a terminal when splitting a chat pane
* Clean empty terminal splits after remote creation settles
* Align retained menu test with terminal split labels
* Verify translated terminal split rejection messages
* Load remote regression dependencies in suite setup
* Keep split actions searchable by chat context and terminal terms
* Preserve later workspace selection when splitting into a terminal
* Use the existing group argument in terminal creation control
* Preserve existing split searches when opening terminals
* Rank eligible palette actions before checking split results
* Describe terminal splits accurately in the chat tour
* fix(browser): Escape typed in a page exits grab, find and the password list
A focused page keeps its keys, so the renderer's Escape listeners for
element grab/annotate, the find bar and the saved-password list never
fired. Main now hands Escape from browser and HTML preview guests back
to the renderer for that page; during a grab pick the page doesn't
also get it, like C/S.
* test(browser): say why the grab Escape test waits out the toast
* refactor(browser): share one page-Escape subscription hook
* fix(native-chat): Cmd/Ctrl+Enter on an empty composer steers the first queued message
* fix(native-chat): empty-composer Cmd/Ctrl+Enter steers only where the chord means steer
With Queue follow-ups off, Cmd/Ctrl+Enter queues the typed message, so a
second press on the now-empty composer would steer the card just queued.
Chat @ file search, Quick Open and the + menu looked a folder workspace up without a host, so a
same-id folder on two hosts resolved to nothing and listed no files. They now resolve the selected
copy, the same way skill lookup does.
Refs STA-13130
New hero still: a coordinator running two workers with the mobile app replying. The Features table is rebuilt from the website's product animations (13 rows led by orchestration, chat or terminal, run anywhere and the mobile app), Also in the box lists the rest of the feature wall, the tagline matches the website, and the contributors image shows up to 500 people.
* fix(worktrees): let the first listing replace a restored server workspace stub
A restored active server workspace starts as a session stub with no head.
If git status fills in its branch before the first listing lands, the
listing merge took that as a concurrent branch switch and kept the stub,
dropping the catalog row (instance id, lineage, provenance). The workspace
then showed standalone until the next listing.
* fix(worktrees): accept a headless row's listing only when it confirms git status
A stale listing could otherwise roll back a branch switch git status saw on
an empty-head row (e.g. an SSH fallback row) during the first connected listing.
* fix(git): keep the agent-terminal credential guard scalar-only so env scrubs can't break git
Agents that scrub env names matching KEY/TOKEN/... (DeepSeek Harness) dropped
GIT_CONFIG_KEY_n but kept GIT_CONFIG_COUNT, so every git command in those
terminals failed with "missing config key GIT_CONFIG_KEY_0". GCM_INTERACTIVE
already carries credential.interactive and suppresses GCM's GUI, so the guard
now emits only scalar variables. Tracked in #26594.
Co-authored-by: yu.xia <yuxianice@163.com>
* chore(git): drop stale indexed-config comments and a dead WSL forward branch
---------
Co-authored-by: yu.xia <yuxianice@163.com>
* fix(orcad): keep the shared node runtime out of artifact-cache eviction
pruneOrcadArtifactCache treated every non-dot entry under a target
directory as a version slot, including runtimes/ — the Node runtime the
slots share across Orca versions. When an upgrade introduced a third
build, runtimes/ was usually the oldest entry by mtime and was removed,
after which orcad could not start (#38181). Skip the reserved directory.
* docs(orcad): document what the artifact prune keeps and what it must not evict
* fix(orcad): only evict names that parse as artifact version slots
Retention now shares the slot-name grammar with the materializer, so
runtimes/, staging dirs and any future sibling under a target are never
counted as a version slot. Installs that already lost runtimes/ re-place
the pinned Node on the next orca serve start.
Fixes#38181
---------
Co-authored-by: Pr1p <zwq19980411@gmail.com>
* fix(browser): attach the desktop browser bridge to environment recipe SSH hosts
Recipe workspaces connect runtime-owned SSH targets that serve a managed
Orca server, but the bridge picked candidates from the SSH settings list,
which hides runtime-owned targets, and browser routing refused them too.
Pick bridge candidates from the managed-orcad claims, validate route
partitions by registration, and route deployment hosts whoever owns them.
Fixes#38603
Reported-by: Mehul K (@mek97)
* fix(browser): follow recipe host connections for the bridge and page routes
Owned SSH targets returned before the bridge rechecked, so a recipe host
connecting never attached it, and recipe browser panes had no published
SSH state to wait on. Recheck the bridge on every SSH state change, and
read a recipe target's connection from its server's state.
Fixes#38603
* fix(browser): settle a recipe browser route when its server is unreachable
Only a live dial waits; lost or never-made contact now lets the route
card offer Retry and browsing from this device.
Fixes#38603
* test: annotate hoisted fixtures instead of casting
Fixes#38603
* fix(mobile): say why a chat launch started a terminal instead
When the host falls back to a terminal for an agent the user set to Chat
(for example Antigravity without its chat runtime installed), show the
host's reason in the launch toast instead of opening a CLI silently.
* fix(mobile): skip the fallback notice for agents that have no chat
* fix(mobile): keep the launch notice toast up long enough to read
* refactor(agent-launch): own the chat-fallback rule in the launch contract
The server-side download transfer store wrote through the runtime file
mutations without a host expectation, so every write was refused as
coming from an outdated client. Each transfer now captures the
workspace's host as it prepares the download directory, and passes that
expectation on every later mutation, so a host that moves mid-transfer
refuses the rest.
Fixes#38122
Prepare a missing owned Claude account home through its existing setup owner and retain useful startup failure guidance. Keep uncertain opening messages in their original chat for explicit Retry, accept exact late proof without duplicate messages, and persist one aggregate launch snapshot before notifying listeners.
Verified with independent code and performance review, Claude/Codex runtime recovery and upgrade QA, targeted renderer and persistence contracts, and required CI. Tracked in STA-13879.
A paired desktop (client kind 'runtime') was classified with phones as an
untrusted relay caller, so the host stripped resumeCommand and filePath
from search hits and the desktop stripped them again on receipt. The same
pairing already returns those fields from the session list, so Resume in
New Tab worked from the list but was disabled for the same search hit.
Classify by client kind once: phones keep the redacted view, paired
desktops get the same fields the session list gives them.
Fixes#38555
Reported by @ArtemMakaryev
* fix(daemon): a main-process freeze no longer tears down the terminal daemon link
On a Windows host where starting a process blocks for seconds, main spends most of its time
frozen inside synchronous spawns (git, mostly). After such a freeze Node runs due timers before
the socket completions that arrived meanwhile, so the 5 s write-settlement deadline expired ahead
of a write the daemon had already taken, and main tore the daemon connection down as dead. Every
session on that daemon then refused input until re-attached, and the reconnect's hello and connect
deadlines failed the same way. Only acknowledged input waits on that settlement, which is what a
paired desktop sends: its keystrokes were refused in a loop while phone and local typing went
through.
The settlement, hello and connect deadlines now count only the time the event loop could run: a
freeze is credited as a single tick, and a tick that ran late never expires a deadline itself, so
the I/O phase runs first. A daemon that stops answering while main runs is still condemned after
the same timeout.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(daemon): freeze-tolerant connection-attempt and RPC deadlines
---------
Co-authored-by: registered2nd <39094401+registered2nd@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(runtime): stamp title-only agent status at the PTY status transition
Program activity moves a PTY's agent status without a new title, so a
title-only frame dated by the title clock alone could sort behind the
working row a paired client already holds. The client then dropped the
done as stale and kept the spinner. Title-only frames and shell-title
demotions now carry the later of the title time and the status
transition time.
Fixes#25136
Co-authored-by: Fede654 <buzondefede@gmail.com>
* fix(runtime): stamp the no-hook title fallback at the PTY status transition
The builder's fallback for a pane with no live hook dated its title-only
frame by the title clock alone, so it could sort behind a title-only
working the renew path had stamped at the status transition.
Fixes#25136
Co-authored-by: Fede654 <buzondefede@gmail.com>
* fix(runtime): never date a shell-title demotion behind the status it replaces
Fixes#25136
Co-authored-by: Fede654 <buzondefede@gmail.com>
* test(runtime): keep the title-only stamp tests beside the mobile status projection
---------
Co-authored-by: Fede654 <buzondefede@gmail.com>
* fix(remote): re-attach terminals a daemon reconnect detached, for remote views and input
When the host's main process loses and re-makes its daemon connection, the daemon drops main's
attachments and the adapter refuses input to every session until it is attached again. Only a pane
mounted in the host's own window re-attaches by itself; a session with no pane there stays silent
and refuses every keystroke from a paired desktop, a phone or `orca terminal send`, while
`terminal list` still calls it connected and writable. A client remount or restart did not help:
its new subscription never re-attached the session.
Main now notes each session the provider's endpoint loss names, re-attaches it once a remote view
shows it (at the loss or when a view subscribes later), and holds input for it until that attach
lands instead of refusing it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(runtime): main re-attaches every session an endpoint loss detached
* fix(runtime): held input honours cancellation and the session it was sent to
Fixes#38433
---------
Co-authored-by: registered2nd <39094401+registered2nd@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat(mobile): rewind a chat to an earlier message
Bring desktop's "Rewind to here" to phone chats. The rewind flow moves
into a shared React-injected hook so desktop and mobile share one set of
rules; desktop behaviour is unchanged. The host now lets phones call
agentSession.rewind behind agent-session.rewind.phone.v1, so a phone on
an older host offers nothing it would be refused.
* feat(mobile): put the message time first, then copy and rewind together
* fix(managed-server): drop a cached update deferral once the host's active build moves
Status reads the host record every time but kept a local deferral until the
host's active version compared equal to or newer than the candidate. Two
builds of the same release differ only by content hash, which compareAppVersions
cannot order, so after the host moved the deferral could stay for days and
the UI kept reporting a pending update that described nothing.
Record the host's active version with the deferral; any change clears it.
This addresses the stale-cache part of the issue; the interrupted-transaction
retry and the supervised-update workflow are separate.
Refs #38400
* fix(managed-server): key a deferral to the host's activation, not just its version
A host that moves to another build and back between two status reads keeps
its version but gets a new activatedAt; the deferral it recorded no longer
describes that host. Compare active and activatedAt, the record identity the
activation code already uses for the same question.
Refs #38400
* fix(managed-server): drop a deferral whose candidate the host already runs
Refs #38400
---------
Co-authored-by: Pr1p <zwq19980411@gmail.com>
* fix(mobile): send committed IME text to the terminal at commit time
WebKit fires no input event after compositionend, so the live input
mirror kept holding committed Japanese text until the next key. Re-run
the mirror with composition ended when the field reports compositionend.
* docs(mobile): say compositionend is the commit signal on every engine
* feat(omp): show OMP's ask questions in chat
Orca's ACP client never advertised form elicitation, so OMP started in
the chat view left out its ask tool and extension dialogs. The OMP
dialect now advertises forms and maps each elicitation onto the
existing question card: multi-question tabs, multi-select and Other.
PI_NO_PTY keeps `pty: true` bash from opening a TUI overlay ACP can't draw.
Co-authored-by: Narry <3047793+NarryG@users.noreply.github.com>
* fix(omp): tell OMP which ask questions past the fourth were never shown
* test(omp): assert behaviour, not note copy, in ask form tests
* fix(omp): let older clients answer single-question OMP forms
* refactor(acp): answer form elicitations in the generic request path
---------
Co-authored-by: Narry <3047793+NarryG@users.noreply.github.com>
The shared-control connection now bounds OPEN to ready with a 30s deadline
owned by its readiness timer. When it elapses, the generation closes with a
ready_timeout cause and reconnects through the existing backoff, which only
resets after 30s of stable readiness, so a slow host cannot cause a storm.
Fixes#37330
* fix(native-chat): list OpenCode 2 commands before the chat's first message
OpenCode chats had no at-rest command catalog, so the / menu showed only
Orca's own commands until the first prompt started the agent. Widen the
ACP at-rest catalog to every agent that lists models in a chat-folder
session: OpenCode 2.x opens a throwaway session in the chat's folder,
reads its available_commands_update and deletes it, as the 2.x model
probe already does. OpenCode 1.x cannot delete sessions and is skipped
without spawning.
* test: drop a no-op OpenCode launch-args assertion
* refactor(acp): share the release listing rule and session-delete policy with the model probe
* feat(mobile): copy, save and share an image from the chat image viewer
* refactor(mobile): pass image viewer actions in so diagrams skip them
* fix(mobile): name the image verb native.image.act and serialize image actions
* fix(mobile): queue image actions per page and skip SVG links
* refactor(mobile): share the cache-folder helper and table the viewer's image actions
* fix(mobile): keep the toast's live region mounted so screen readers hear it
* test(mobile): re-record agent history goldens for the always-mounted toast region
* test(mobile): import the declared routes in the moved routes test
An explicit Update, Rollback, Recover or Restart resumed the server's
status before invalidating its transport, so the first probe could ride
the connection about to be dropped. The action now includes its own
invalidation and note clearing, and status resumes after both. A test
also covers the SSH host's Disconnect being lifted for a managed server.
Refs #38347
* feat(mobile): set, pause, resume and clear a chat's goal from the phone
The phone sent /goal to the agent as plain text and showed no goal. It now
has desktop's goal mode (Goal chip, goal placeholder) and a goal strip on the
composer's top edge that expands to Pause/Resume and Clear goal.
The goal logic desktop and mobile share moves to src/shared: the goal report
(journal rows over the options answer), status labels, elapsed format, the
goal-mode pick rule and the goal row filter. agentSession.threadGoal joins the
phone allowlist behind agent-session.thread-goal.phone.v1, so older hosts keep
showing the goal without offering changes.
* fix(mobile): open each new goal's strip collapsed
* fix(mobile): keep goal sends' delivery choice and scope goal locks per chat
* fix(mobile): offer goal changes only when the paired desktop relays them
* test(mobile): pin which goal changes the phone offers per host
* refactor(mobile): reuse the queued box style and keep the goal strip stable per chunk
* fix(mobile): set phone goals through the composer's changeThreadGoal
Checks sidebar edit/delete of PR conversation comments always used desktop
IPC, so server-owned repos and SSH workspaces behind a paired server edited
and deleted with this computer's GitHub credentials while reads and posts
used the server's. Add one owner-aware client for slug-addressed GitHub
operations and move every slug caller onto it, so ownership is resolved at
the client boundary instead of in each component. An unknown owner now
fails explicitly instead of falling back to desktop credentials, and a
result that lands after the panel moved on no longer touches the list.
Refs STA-13254. Reported by Jinjing.
Co-authored-by: Claude <noreply@anthropic.com>
* fix(new-workspace): restore right-click "Set as default" on the agent picker
The shared agent picker (#35802) replaced the combobox in the new-workspace
composer and dropped the context menu that set the default agent. Wire
defaultAgent/onSetDefault through AgentLaunchPicker so agent rows, the
Blank Terminal row, and the closed field offer it again.
Co-Authored-By: Claude <noreply@anthropic.com>
* fix(agents): keep the "Set as default" menu open when the mouse moves
The context menu was non-modal, so hovering the agent rows beneath it
moved focus to them and dismissed the menu. Make it modal so focus stays
in the menu until the user picks or dismisses.
Co-Authored-By: Claude <noreply@anthropic.com>
* fix(agents): keep the row highlighted while its "Set as default" menu is open
Row highlight follows focus, which moves into the context menu. Mark the
trigger with data-context-menu-open and style it like the hovered row.
Co-Authored-By: Claude <noreply@anthropic.com>
* fix(agents): address review on the Set as default context menu
- Keep the context menu non-modal; prevent focus-outside dismissal instead,
so combobox callers keep one-click selection and scrolling.
- Drop the field-level context menu: it clobbered the dropdown trigger's
data-state/data-slot, ignored the disabled gate, and doubled up on long-press.
- Pass onSetDefault through unchanged so memoized rows stay stable.
- Reset the open marker when the menu unmounts while open.
- Stop asserting the CSS-only highlight marker in tests.
Co-Authored-By: Claude <noreply@anthropic.com>
---------
Co-authored-by: Claude <noreply@anthropic.com>
Repeated clicks on the native chat composer + (Attach file) button opened
one OS file picker per click because shell:pickAttachments opened a
parentless (modeless) dialog with no in-flight guard. Route all shell:pick*
and repos:pick* handlers through a single-flight wrapper; overlapping
requests resolve as canceled, which every caller treats as a no-op.
* feat(mobile): offer Sign in on a signed-out chat via a host terminal login
* feat(mobile): say which host is out in the chat composer, with Reconnect for the desktop link
* refactor(mobile): fit the host outage line beside main's chat changes