Cloning always went into <parent>/<repo name>, so a same-named repository
from another owner (or any non-empty folder of that name) could not be
cloned into the same parent. Before cloning, Orca now checks the target
on the clone host. If it is taken, the clone forms show a Folder name
field with a free suggestion (<repo>-<owner>, then <repo>-2...) and clone
into that instead. RPC repo.clone and `orca project setup-clone` accept
the folder name too.
Review rebuilt only when a git.status read changed, so a base move that left this worktree's status as it was kept the old compare (also cached 30 s). The compare entries now take git.status's gitStatusChanged signal. A status read that lands after the signal marked the shown compare rebuilds Review without re-keying worktree diffs, and a compare read that lands marked is read again.
* fix(mobile): paint host labels and relay server rows from the phone's store on relaunch
* refactor(mobile): reuse the SSH target summary schema for stored host labels
* fix(browser): import the session registry from its new profiles folder
#40002 moved browser-session-registry into sessions/profiles, and #39613 landed after it with the old path, so main no longer typechecks or builds.
* fix(test): keep the popup Electron fixture in its own worker
#40067 lets unit files share a worker's module cache. The popup compatibility fixture keeps its Electron app, mock server and temp root at module level, so after the first file the others reuse a closed browser.
* fix(native-chat): show newly installed skills in the Codex $ menu before the first message
Resting Codex chats served the background probe's skills/list from a
5-minute cache, so a skill installed in that window showed "No matching
skills", even in a new chat. Each menu open now compares a cheap stamp
of Codex's skill folders and skill/plugin config with the one taken
before the last scan, and rescans only when it changed.
Probe requests always force a reload, and probe pools are keyed by the
catalog's launch generation instead of the whole env, whose 10 s refresh
started a second Codex on every rescan.
Fixes STA-14359
* fix(native-chat): keep the structured session hook within its line limit
* perf(mobile): answer a page's ready that arrived before its bridge host
A page's ready can reach the shell before the screen has built its bridge
host (the host waits on the client and the host profile read). It used to
be dropped, so init waited for the page's next retry, up to 2 s later.
Keep the latest ready per session and answer it once the host exists.
* perf(mobile): keep one prewarmed page document while Home is shown
While native Home is on screen, boot one page document for the most
recently connected host with a cached build, parked invisibly in the
window. Opening a page from that build adopts it instead of building a
WebView, which removes the WebView start and script parse from the tap.
The spare is dropped when Home is left without a claim (2 s grace), on
background, memory pressure, its own failure and before the cache deletes
its files. It is never kept beside a shown page, and only phones with
more than 3 GiB of RAM (4 GB phones) get one. A parked page is told to
stop asking for init; the adopting view answers the ready it sent.
Builds on Jinwoo's spare pool and replay work in #32203 and #32204.
Co-authored-by: Jinwoo-H <73622457+Jinwoo-H@users.noreply.github.com>
* fix(mobile): unregister the shell's memory callbacks from the context that registered them
---------
Co-authored-by: Jinwoo-H <73622457+Jinwoo-H@users.noreply.github.com>
* feat(viewer): fit PDF previews to pane width
- Apply the saved scale on pdf.js pagesinit; a 'page-width' preset set
before page views exist was dropped, so PDFs opened at 100%.
- Refit 'page-width' when the viewer container width changes.
- Ctrl+wheel / pinch zoom stops on the fit-width scale when crossing it.
* fix(viewer): refit PDF page width once a resize settles
- Refit after the container stops resizing (150 ms) instead of every
frame of a split drag; each refit re-renders the visible pages.
- Drop the fitted-width cache: Fit to width, the wheel stop and
pagesinit fit without updating it, so returning to an old width
skipped the refit. pdf.js already no-ops a same-scale refit.
- Observe the border box so a scrollbar the refit toggles can't loop.
- Apply the latest scale preference on pagesinit, so a zoom made while
the first page loads isn't undone.
- Record the wheel stop's 'page-width' before update() can move the
current page, and read the fit scale only for zoom wheels.
* test(viewer): cover PDF wheel zoom stopping at fit width
* fix(viewer): apply the PDF wheel stop as the page-width preset
---------
Co-authored-by: stmoon <munhoney@gmail.com>
* feat(cli): list and reload installed browser extensions
* docs(browser): document extension command contracts
* docs(browser): describe extension test fixture factory
* refactor(cli): validate extension reload once and trim list output
The RPC params schema owns the ID-or-path and ID format checks. Reload
drops --profile and the constant scope field, since it always reloads
every profile where the extension is enabled. List no longer returns
icon data URLs or permission lists.
* test(browser): keep five extension reload tests at the command owner
* fix(cli): route orca extension through the packaged Linux launcher
* fix(browser): refresh Settings after an extension reload from the CLI
* test(browser): type the reload fixture list without a cast
---------
Co-authored-by: Kelvin Amoaba <97001695+AmoabaKelvin@users.noreply.github.com>
The native shell view now hosts a MobileWebShellDocument that owns the
WebView, its scheme handler or request intercept, the network block, the
bridge and the navigation policy. The view keeps layout, the back-edge
swipe and its React events. Nothing changes for a page; this is the seam
a prewarmed spare page needs.
Based on Jinwoo's page split in #32202.
Co-authored-by: Jinwoo-H <73622457+Jinwoo-H@users.noreply.github.com>
* fix(native-chat): an unanswered model or effort change fails only its message, and each agent process end is logged with its cause
A model or effort write the agent didn't answer within 30 s, or a send withdrawn while its
write was pending, closed the agent's stdin. OpenCode exits 0 on that, so the chat showed
"OpenCode stopped while this response was in progress (code 0)" and its background work
died, with nothing logged. Session setters now carry a call deadline that sends
$/cancel_request and never touches the stream; later controls and prompts wait for a
withdrawn write to settle. Every agent process end logs who ended it and why.
* fix(native-chat): name Orca as the one ending an agent it stopped after its own failure
The exit record now reads endedBy orca for a host force-close and for an ACP agent Orca
stopped after losing its connection or refusing a journal write, with that reason leading.
The withdrawn-write test no longer races its deadline.
* fix(native-chat): keep who ended an agent when its last journal write is refused
Ruled by the independent decider: the failure-close cause is recorded before any publish that
can re-enter cleanup, an ended or requested ending never takes a new one, and the ended event
reads it from before publishing. A test drives a real refused journal write on an agent's own
exit and on a lost connection.
* fix(native-chat): redact the agent process end record's reason before it is logged
The reason can carry the agent's stderr tail, and the console line is not redacted downstream.
* fix(native-chat): let Continue in Chat UI switch when Orca can't prove the terminal stopped
Continue in Chat UI closed the agent's terminal and then refused the chat
unless the host proved a clean exit, so an idle Claude on a slow or remote
host failed with "couldn't confirm Claude stopped". Any settled exit wait now
lets the chat start; the host's create still refuses a conversation another
terminal holds, using the hook rows and foreground-process checks it already
has. The wait outlasts the host's explicit-close stop.
A conversation the agent never saved (nothing sent yet) has no history to
open, so every Retry failed. After the terminal closes, that chat now restarts
in the same tab as a new conversation instead.
Tracked in #39085.
* fix(native-chat): read a Claude transcript nothing was sent in as empty, and let an unknown writer check switch
A Claude session that never got a message can leave a metadata-only
transcript. Its import found no turns and refused as unreadable, so Continue
in Chat UI still failed. A Claude file with no user or assistant record now
reads as empty, the same refusal a missing transcript gets, which the
handoff answers by starting the chat as a new conversation. Records Orca
can't decode still count as a conversation, so unreadable history keeps
failing.
A host that couldn't say whether it checked other terminals no longer stops
the switch before the close; the create checks them again.
* fix(native-chat): read an empty Claude transcript as empty through adoption, and a broken record as a possible turn
Adoption checks a transcript's identity before using it, and a metadata-only
file carries no working directory, so the empty file still refused as
unreadable. A file with no conversation adopts nothing, so it skips that
check. A record too broken to parse may be a turn, so it keeps the history's
own failure instead of reading as empty.
* fix(native-chat): only a typed record with no message reads as Claude metadata
A record shaped like a turn but missing a known type could read as metadata,
so a transcript holding a real prompt could be taken for one nothing was sent
in. Now only a JSON object with a non-empty type other than user or assistant
and no message counts as metadata; anything else may be a turn and keeps the
history's own failure.
* refactor(native-chat): narrow the Claude record type without a cast
* fix(native-chat): read a Claude meta user record as metadata when it shows nothing
A Claude session where only a local command ran, such as /rename, saves a
user record Claude flags as meta and no turn, so Continue in Chat UI still
failed for it. A meta user record the decoder can't show now counts as
metadata; one it shows, such as a tool result, still counts as a turn.
* fix(codex): recognize the 16 app-server notifications added through Codex 0.167
Users run their own Codex, so 0.167 frames already reach Orca. Unlisted notifications fell back to visible raw rows in the chat timeline; classify each one from the 0.167.0 schema instead.
* test(codex): journal no row for app-server notifications that carry provider text
* chore(claude): update the Claude Agent SDK to 0.3.318
Includes the upstream fix for omitted permissionMode (claude-agent-sdk-typescript#519), so the 'use my Claude settings' permission choice honors settings defaultMode.
* test(orcad): expect the SDK's joined --permission-prompt-tool=stdio argument
Claude Agent SDK 0.3.295+ passes named option values in the same argument as their flag.
* refactor(claude): drop the permission flag SDK 0.3.318 no longer reads
The SDK leaves an omitted permissionMode to the CLI, so the 'own' choice needs no opt-in option.
* perf(terminal): group park-exempt sleeping records once per map; index captured panes by leaf
Each mounted worktree's exemption selector rescanned every sleeping record
after a record-map change (worktrees x records), and pane reconciliation
compared every captured pane against every fallback pane (panes^2 per tab).
* perf(terminal): skip the pane index on empty fallbacks; reuse the accumulating leaf traversal
goneSessionsKeepTabMounted scanned every sleeping record per eligible tab,
so a workspace switch with thousands of tabs did tabs x records work on the
renderer thread. Build both owner sets once per source identity instead.
The host stops the old agent (about 0.6 s for Claude, up to 3 s with slow
MCP servers) before it writes the divider, so the old transcript lingered.
Linear: STA-14361
* Move session search SQLite into dedicated workers
* test: spawn the session search test worker with the shared worker helper
* fix: pass only drain promises to the channel's drain wait
* Repair session search failure and lifecycle boundaries
* Stop indexing tool output and reclaim existing rows
* test: say why the session search worker tests need a longer timeout
* Bound search cleanup and preserve failure and digest semantics
* Use the database row type for tool purge batches
* test: drop the same-connection mid-page write case now that each page reads one snapshot
* test: prove a mid-page delete from the writer can't change that page's hits
* Repair transcript cancellation cleanup and search test runtime admission
* fix: cancel active transcript finalization and enrichment waits
* fix: close transcript handles when cancellation wins delivery
* fix: preserve scan cancellation errors across parser waits
* test: prove cold session search bypasses an active writer batch
* fix: preserve search continuation through background tool cleanup
* fix: preserve search pages during orphan reclamation
* fix: bound typo repair posting visibility probes
* fix: preserve exact search terms when visibility is inconclusive
* test: drop orphan-reclaim cursor staleness case superseded by frozen continuation
* Bound session search work before ranking candidates
* Preserve the limit notice for empty search windows
* Bound session eligibility lookups and reuse FTS scoring statistics
* Index session scopes for population and candidate searches
* Derive search status from the live index after clear
* Preserve disabled search status during settings transitions
* Share planned expressions between spelling probes and search
* Keep identifier fragments out of spelling presence checks
* Report search initialization through its pending transition
* Bound spelling vocabulary work with the search posting budget
* Preserve search fallback while bounding distinct vocabulary seeks
* fix(session-search): drain removals before the worker queue fills; keep aborted close waits from failing teardown
* fix(session-search): hold writer commands when the worker queue is full instead of stopping the writer
* chore(ratchets): baseline the session search worker's one-shot entry check
* fix(browser): show site favicons on remote host browser tabs
Host-run browser tabs mirrored to a paired client always showed the
globe: the host's session-tab snapshot carried no favicon. Hosts now
publish the active page's icon URL as an optional faviconUrl, capped at
2 KB and dropped when it points at the host's loopback. Headless hosts
pick it up from page-favicon-updated and publish only when it changes;
desktop hosts include it in the existing graph-sync key. Clients keep
their current icon when an older host omits the field.
* fix(browser): publish a remote tab icon on arrival, not on every swap
Read the headless favicon through the agent browser bridge so the
runtime stays free of Electron imports, publish only when a page gains
an icon so animated icons ride later publishes, and drop IPv4-mapped
loopback icon hosts.
* fix(browser): clear a remote tab icon when a cross-origin load starts
A load that fails on the new origin never commits, so clearing only on
did-navigate kept the old site's icon beside the failed URL. Also give
the runtime tests' bridge fakes the new favicon getter.
* test: give the session-tab bridge fakes the favicon getter
* fix(session-history): show the last list at once after a restart while it rescans
The renderer's list cache lived only in memory and deleted entries on every
rescan or chat link change, so a restart or a forced rescan left the panel on
a skeleton until the host finished scanning. Save each scope's last rows in
IndexedDB (no message text), mark outdated entries stale instead of dropping
them, and paint that list as refreshing until the rescan replaces it.
Fixes#39308
* perf(session-history): skip the saved-list write when a rescan changed nothing
* fix(session-history): skip unchanged saves across panels and keep a saved list through a cancelled publish
* fix(session-history): evict saved lists by last use and save once the profile loads
* test(session-history): drop an identity-only refresh test and correct the truncation comment
* fix(session-history): let the React compiler handle the moved new-session rescan
* fix(worktrees): use Session History's Claude bucket rules when retiring names
Retirement backfill matched Claude project buckets with the old encoder, so it
missed hashed long-path buckets, root workspace folders and the \\wsl$\ share
spelling. Use the shared bucket prefixes, and read the cwd of a hashed bucket
to recover the workspace name its name no longer carries.
* test(worktrees): drop retirement cases production cannot reach
* fix(worktrees): fold case when matching a hashed bucket's cwd to the workspace root
* refactor(worktrees): match each retirement bucket once and drop the old bucket rule
* perf(worktrees): overlap long-bucket probes, skip rescans on denied transcripts
A transcript that stays permission-denied forced a full retirement rescan after every 60 s backoff.
The last-status, GitHub cache, notification dismissal and model catalog stores each grew their
own legacy-file import, read-only startup read, changed-row writer and retry backoff. They now
share src/main/sqlite/row-cache/ (KeyedJsonRowCache with load/write, the legacy JSON source,
one failure classifier and backoff); each store keeps only its cadence and fencing policy.
Edge cases now behave the same in every store:
- a corrupt or rejected older-build file keeps the stored rows (it no longer wipes them);
- an older-build file that exists but cannot be read is never treated as absent;
- the import receipt is the file's content hash, without its mtime, so a copied leftover is
still recognised as imported;
- while the rows or that file cannot be read, the store saves nothing that session and never
deletes a file it did not load (dismissals keep retrying, as before);
- files are user-only and hardened everywhere.
The last-status and GitHub caches move to the shared row layout, so each rebuilds empty once.
* Rotate the server pairing identity when ORCA_INSTANCE_ID changes
* Back up replaced identity files, keep the recorded id on reset, keep staged files once the rotating marker is published
* Add identity-reset files to the sync fs baseline and document the backup folder
* Report a reset honestly after finishing an interrupted rotation; keep first backups and the newest one
* fix(vm-recipes): record each VM before create runs so a quit or crash can't leak it
Orca now saves a "provisioning" record for a recipe VM before running its
create command, and updates it when create finishes. If Orca quits or
crashes mid-create, or create fails without returning a result, the VM
stays listed in Settings > Cloud VMs as Failed with its instance id, so the
user can run Cleanup (destroy gets the instance id) or remove it from the
list. On startup, provisioning records with no create running are marked
as interrupted.
Records without a recipe result live in a separate file that older builds
never read, so downgrading keeps working. Records also store the repo path
so Cleanup, Copy command, suspend and resume still work after the repo is
removed or re-added under a new id (#17293).
* fix(vm-recipes): keep no runtime row when create is cancelled or rejected before its script starts
* fix(vm-recipes): harden write-ahead records from review
- Never overwrite a provisioning-records file this build cannot read; refuse new records instead.
- Remove the provisioning-records file when empty instead of rewriting it on every store write.
- Only fall back to the saved repo path while it still defines the same recipe.
- Don't let Cleanup or Attach act on a create that is still running or never returned a result.
- Show Provisioning before Cleanup disabled; stamp running records with the save time.
* fix(vm-recipes): keep new store code off direct sync fs calls and render-path translate
* fix(vm-recipes): detect a missing provisioning-records file without a type assertion
* fix(antigravity): show installed skills in Antigravity Chat
Orca's managed Antigravity server runs with its own GEMINI_HOME so its
sign-in stays separate, which also hid the person's user-wide skills.
Before each launch, link the chat home's config/skills and
antigravity-cli/skills to the ones in ~/.gemini, as the common pattern
does. Empty placeholder folders are replaced, folders with content are
kept, and a failure only logs.
Tracked in #39528.
* fix(antigravity): link a chat home's skills one launch at a time
Two chats starting together could both find the empty placeholder; one
removed it while the other failed, and a harness recreating it left the
chat without skills. Launches now link a chat home one at a time, retry
once when the placeholder reappears, and leave links alone when the
skills folder is unreadable rather than missing.
* test(antigravity): make the dangling skill link fixture portable to Windows
* fix(source-control): match the Git Graph button to the Commits header actions
Use the header's shared icon-button style and a go-to arrow, and restore
Cmd/Ctrl-click to open the Git Graph in a split.
* refactor(source-control): share one Commits header icon button
The design-system lint needs static className strings, so a component
holds the style instead of a constant.
* fix(source-control): use the pop-out icon for the Git Graph button
* fix(remote-runtime): keep a resumed VM's device pairing while its host key is unchanged
* fix(remote-runtime): probe before dropping the transport, keep saved key spelling, leave SSH wakes as they were
* Keep inherited fork actions with the original chat
* Keep fork boundary tests aligned with inherited actions
* Keep inherited fork actions with their original chat
* Keep fork refusal tests within their typecheck projects
* Allow phone forks for supported agents beyond Claude and Codex
* Gate inherited tip forks on host original-chat support
* Require current host proof for inherited fork offers
* Bind inherited fork actions to the current host runtime
* Keep unsent browser forks definitive and offer accurate retry guidance
* Offer copied tip forks only at the fork point and name their source
* Offer forks on all completed copied replies
* Explain which original response can be forked
* Start OpenCode 2 with a picked model through its launch config
OpenCode 2's root command has no --model, so launches that carried one
exited with 'Unrecognized flag'. On supported 2.x releases the PTY launch
hook now moves a literal root --model into OPENCODE_CONFIG_CONTENT and
starts a private server so the TUI reads it. Anything it can't apply is
left as typed.
* Point the sync-fs ratchet baseline at the moved agent-hooks files
#39969 moved the agent-hooks installer files after #39930 wrote the
baseline, so the ratchet saw every moved file as new and failed lint.
Same counts, new paths; installer-utils' 20 split into its two new owners.
* Rewrite only one plain OpenCode command with a real --standalone
A --prompt or --session value spelled --standalone no longer counts as
the option, the cut starts at the previous token's end so its escaped
trailing characters stay, and a newline or shell operator leaves the
command as typed.
* Leave a command with an operator outside quotes as typed
A token that only starts with a quote, such as '--auto'&&echo, could hide
a shell operator; scan each token outside its quotes instead.
* Leave comments and explicit servers as typed
A word starting with # comments out the rest of the line, and --server
means another server that never reads this launch's config.
* Scan for shell operators with each shell's own quoting
cmd quotes only with double quotes and PowerShell escapes with a backtick,
so a posix-only scan could miss an operator they would split on.
* Rewrite only the command shape Orca itself emits
Replace the shell scanners with one check: every argument after the
executable must be exactly quoteStartupArg's output or a bare flag the
builders append, and the prompt must match the body Orca put in the env.
cmd also rejects any divergent token or raw newline. Anything else stays
as typed.
* Test that the launch hook hands the prompt body to the model rewrite
* feat(vm-recipes): optional per-step timeouts for recipe lifecycle commands
A recipe in orca.yaml can set timeoutSeconds (one number, or a map of
create/suspend/resume/destroy). When a step runs past its limit, Orca
stops the whole process tree the same way Cancel does and reports a
recipeTimedOut failure naming the step and the limit. Recipes that do not
set timeoutSeconds keep running with no limit, exactly as before.
Saved runtime records keep a recipe snapshot that older builds parse
strictly, so the snapshot leaves timeoutSeconds out; suspend, resume and
destroy read the current limit from the repo's orca.yaml instead.
Suspend and resume exit failures now go through the failure catalog with
the same English text.
* test(vm-recipes): fire the grandchild timeout only after the grandchild exists
* fix(vm-recipes): only reuse orca.yaml timeouts for the same recipe a runtime was created from