* 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
* Project chat-mode worker liveness from the structured host
* Keep chat reach checks out of per-publication attention and Crew rebuilds
* Install the session host before judging structured workers in worker-list and worker-show
* Keep worker-list rows to the liveness fix
* perf(notifications): save mobile dismissal history as per-delivery SQLite rows
Each alert or dismissal rewrote the whole pretty-printed history file (hundreds of KB).
Rows now save individually through a shared row cache that fails fast on a locked file,
rebuilds once on corruption, and re-reads its baseline after outside commits. Unread
history is never replaced: events queue and merge once a retry reads it. An older build's
file is imported with a receipt committed alongside its rows, then removed only while it
is still that file.
The mobile-restore test now drains the original host's recovery-capsule work before
starting the recovered host, instead of relying on the old asynchronous file write.
* perf(model-catalog): save the agent model catalog as per-entry SQLite rows
Every listing change rewrote the whole multi-megabyte file. Entries now save only when
they change and failed saves retry with backoff. An older build's file is imported with a
receipt; an unreadable file is kept. If stored state cannot be read (a lock elsewhere),
the session starts cold and saves nothing, deciding nothing between the file and the rows.
Rich-text pastes now keep their hyperlinks as Markdown links, and pasting a
URL over selected words links them, as other message editors do.
Fixes#39153Fixes#39150
* refactor: organize browser guest lifecycle owners
* test: resolve cross-version client owners and pre-ticket baseline
* test: record the released terminal registry path
* fix(activity): keep live agents visible when showing unread only
A running agent's thread is read unless it carries an older unread event, so the
unread-only filter hid agents that were working again. Exempt live threads
(currentAgentState non-null) alongside the selected-row exemption.
* fix(activity): exclude unavailable agents from live filter
* fix(activity): retain unavailable identity in live snapshots
* test(activity): retain live agent badge after acknowledgment
* fix(orchestration): wake reattached Hermes terminal workers
Record the provider-proven terminal grid on the headless attach path before
restoring the screen. Without it, trusted-screen readiness rejected idle
Hermes workers after a runtime restart and stranded both send and reply mail.
Reuse the spawn geometry policy without resizing the surviving PTY. Cover
status and question-reply wakes plus busy and draft composer holds.
* fix(orchestration): retain Hermes activity across native titles
Hermes writes a status marker followed by an arbitrary session name and
model. These titles can lack a recognized agent-name token, clearing live
activity after the mailbox pointer is typed and leaving its Enter deferred.
Classify native markers only for an already identified Hermes terminal.
Reproduce the exact OSC 1/2 titles during both status and reply delivery,
retain busy/draft holds, and update the existing partial attach fixture.
* refactor(pty): keep runtime attach seeding under the line cap
The rebased attach path pushed operations.ts over the 300-line oxlint cap. Move the size commit and headless seed into their own module so the wake behavior stays and the file fits.
* fix(orchestration): retarget Hermes title imports after the agent-status move
Upstream moved agent-title-core and terminal-agent. The rebased title helper still imported the old paths, so typecheck could not resolve them.
* fix(pty): keep a resize that lands during runtime attach
Attach waits on the daemon before committing snapshot geometry. A resize in that window already published the live grid, so the later snapshot commit must not write it back.
* fix(pty): detect an attach-time resize by cache identity
A resize that returns to the pre-attach dimensions still publishes a new cache entry. Comparing only cols and rows let the snapshot commit overwrite that live grid.
* test(pty): assert attach reflow and Hermes idle status in existing cases
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* refactor(orchestration): keep the Hermes title rule with the other title providers
* fix(pty): give a resize that landed during attach a readable mirror
Reflowing the seeded snapshot marked the grid unrepainted, so the screen
rules kept refusing it after the TUI repainted for the resize.
* fix(orchestration): write the Hermes title markers as escapes for the ASCII server bundle
* test(pty): retarget Hermes attach test imports after the orchestration module moves
* fix(orchestration): restore a reattached agent's idle status from its trusted ready screen
A screen-ruled agent idle before a runtime restart may write no title after
reattach (Hermes repaints its title only on a state change) and has no restored
hook report, so it stayed without live status and mail was never offered.
When no report restores it, the agent's own strong ready rule on the trusted,
correctly sized grid now gives it a live idle status; busy, draft and unknown
screens still give nothing. Quiet-gated rules and a grid not yet readable get
one recheck.
The attach test no longer injects a fresh title after attach.
* fix(orchestration): keep rechecking a reattached ready screen until it settles
One recheck could land inside a redraw's quiet window or before the grid became
readable, leaving a quiet-gated agent without live status. Recheck within a
bounded window instead, and cover a Cline redraw after attach.
* fix(agent-state): read agy's idle composer with background task rows as ready
agy 1.4 lists running background tasks between the composer and the hint
row, so composer_ready never matched and a reattached agy with a task
running held its mail until the task ended. A sibling rule allows up to
six task rows; the hint row still decides, so mid-turn, draft and picker
screens hold.
---------
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-authored-by: Jinwoo-H <jinwoo0825@gmail.com>
* fix(orchestration): refuse worker-start on a busy terminal before any wait
worker-start --terminal and the follow-up a send to a finished worker starts
now claim the terminal through one check, before a Run binds, a Task or
Dispatch is written, or readiness is awaited. The Dispatch insert repeats the
claim atomically, and the late authority check stays as a backstop.
* fix(orchestration): refuse a busy terminal with no await before the Run binds
* fix(orchestration): keep the terminal_busy code and its data on the wire
* fix(orchestration): a start stranded by a restart does not hold the terminal
* test(orchestration): drop casts in the busy-terminal test
Desktops advertise client-keepalive-v1; the edge offers it after the hello-ack and
auto-responds to a fixed keepalive frame, so idle hosts need no 25 s ping alarm
(each setAlarm is a billed row write). Silent keepalive hosts are probed with one
relay ping before a phone is refused, closed at once where the host is leaving.
Shipped desktops and cells see nothing new. Kill switch CLIENT_KEEPALIVE=0.
* fix(orchestration): refuse a reply to a finished worker's report and name the follow-up that works
* fix(orchestration): say what the action under a finished report does
* fix(runtime): keep a restored tab selected after orca serve restarts
Since #38844 a cold rebuild restores the saved tab groups, and a saved
group's null active tab was kept as an explicit "nothing selected". A
headless server never saves its own selection, so after a restart its
workspaces listed every terminal with none selected. Saved groups now
only declare a null selection when the session also saved an active
group; otherwise the restored tab stays selected, as before.
* test(e2e): bring layout-compat and paired-client specs up to current behavior
- old-phone baseline: phone snapshots carry tabGroupLayout since #38844.
- tab composition: drop onto where the active tab sits once a drag
undocks it; create the server-placed browser page on the server, since
a phone's create through the desktop is desktop-hosted (#37705); the
desktop serves its phone the server page it mirrors (#36447).
- project removal: retry the host's "can't answer yet" terminal list and
wait for a terminal whose shell has spawned.
---------
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
The PR/issue cache only seeds next launch's sidebar, but every flush rewrote the whole
~200 KB orca-github-cache.json. Store one row per entry in orca-github-cache.db, write only
changed rows, and save at most every three minutes plus at quit and explicit flush barriers.
An existing sidecar is imported and removed; older builds read a missing sidecar as empty.
last-status.json was rewritten whole (~190 KB) up to every 5 s while agents ran. Status now
lives in agent-hooks/last-status.db with one row per pane and per authority commitment, and a
save writes only rows whose serialized content changed. Routine saves wait 3 minutes; authority
changes still save at once, and stop, quit and hook-disable flush. Rows past the 7-day TTL are
no longer saved. An existing last-status.json (written by this or an older build) is imported
on start and then removed.
* perf(session-history): answer Workspace and Project from their own sessions
Workspace and Project send scopeOnly. The scanner then skips listing and parsing cwd-bucket agents (Claude, Pi, CodeBuddy) outside the scope, keeps the recency pass for the other agents but returns only its in-scope rows, and checks name-matched Claude buckets file by file when their newest transcripts name no in-scope cwd. The tab move lookup and All keep the full scan.
* test(session-history): pin that scope-only drops out-of-scope recency rows
* fix(session-history): keep every row main shows when scope-only skips bucket agents
Parse the whole recency window and keep all of its in-scope rows, bound unverified bucket files apart from confirmed ones and let their parse decide, and keep a scope's rows on screen across a depth change.
* fix(session-history): keep Pi listed for scope-only and let scoped rows stand in across scopes
OMP shares Pi's folder under PI_CODING_AGENT_DIR and Pi's listing decides which files OMP parses, so scope-only keeps listing Pi. Workspace and Project rows now stand in for any scope but All, since the renderer filter narrows them.
* fix(session-history): serve scope-only from a cached full list and NFC-fold bucket names
All and Project send the same paths, so a cached All list answers Project without a rescan. Bucket names and scope prefixes are compared NFC-folded, since CodeBuddy and Pi keep the cwd's own Unicode form.
* fix(session-history): match NFD-named buckets by encoding both Unicode forms
Claude replaces each non-alphanumeric code unit with a dash, so normalizing an encoded name can't recover an NFD cwd. Encode the NFD spelling of each scope path too, and drop the post-encoding NFC fold.
* refactor(session-history): build the scope matcher only for scope-only scans and tighten comments
* fix(runtime): move the local RPC socket to a short path when userData is too long
A long userData path made the local RPC socket path exceed the Unix
sun_path limit (104 bytes on macOS, 108 on Linux), so listen failed with
EINVAL and the CLI could not reach the runtime. Reuse the terminal
daemon's relocation: resolveDaemonUnixSocketPath moves the socket to a
private /tmp/.orca-daemon-<uid>/<hash> dir, the server creates and
verifies that dir before listening, and the orphan sweep covers it.
The CLI and the browser sidecar check the dir is private to this user
before they send the auth token, as the daemon client does.
* fix(runtime): verify the relocated socket dir before sweeping it; probe relocated holder sockets
Check that the relocated /tmp/.orca-daemon-<uid>/<hash> dir is private to
this user before the orphan sweep lists or unlinks anything in it, and skip
that dir when the check fails. The orcad stale-lock reclaim now also scans
the relocated dir for the holder's runtime socket, so a live holder there
is probed and its lock is not reclaimed.
* fix(runtime): ship the socket-dir check with the packaged CLI; keep main sync fs flat
The CLI imports daemon-socket-endpoint-path, but electron-vite replaces
out/main, so packaging lost the module and the installed CLI crashed.
Add it to the CLI main entries and unpack it with its mode constants.
The lifecycle sweep and the stale-lock reclaim now use async fs for the
relocated dir, so the main sync-fs count stays at its baseline.
---------
Co-authored-by: m4air <m4air@m4airs-MacBook-Air.local>
The deferred focus('start') in autoFocusRichEditor ran even after the user
had already clicked or typed in the editor. In hidden or busy windows the
frame lands late (hidden windows paint at 1 Hz), so text typed into a new
Markdown file was split around a caret jump to the start, and a click
selection in a freshly opened file snapped back to the first line.
Skip the deferred focus when the editor is already focused and its doc or
selection changed since the focus was scheduled.
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
When dom-ready fired while webview.getWebContentsId() threw, the
registration callback bailed out on the ownership fence (ownsGuest(null)
is always false), so validateAfterResume never ran and the page stayed
unregistered until some unrelated caller happened to read the ID. Fence an
unidentified guest by webview ownership only, so validation retries until
the ID reads.
The recovery spec's registered-page oracle now ignores tab list rows with
loaded: false: since #35563 tab list also reports tab-bar pages that have
no registered guest, so unregistered pages no longer drop out of it.
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
- setup-script-import: imported setups are saved from the Review setup
script dialog since #37937.
- github-url-smart-input-transition: the GitLab source lists through
gitlab:listWorkItems since #32005, so stub that channel.
- structured-chat-tabs-open-close: the Claude catalog probe also sends an
initialize request for sign-in discovery since #37191.
- golden-core-flows: onboarding launches the chosen agent in the fresh ~
workspace (#37898), whose first launch asks the per-repo agent folder
trust question (#38946); answer it before adding a project.
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
* fix(claude): ask before matching Claude Code's theme in every profile
New profiles turned the sync on by default and wrote custom:orca into the
global ~/.claude/settings.json, so a fresh dev build, test copy or second
profile restyled Claude Code for an Orca whose toggle was off, and that Orca
could not restore it. Every profile now starts off and gets the one-time offer.
* docs(claude): the theme sync offer now reaches every profile
Session, remote layout and worktree metadata domains are stored one row per entry, so a
save rewrites only the entries that changed instead of the whole multi-megabyte document.
Readers reassemble the exact original JSON. The schema version is unchanged, so older
builds keep reading the full-document row, which is refreshed when the writer starts, at
most every five minutes while it runs (including quiet periods), at graceful close, in
published backups, and after profile transfers.