* Launch provider CLIs without a per-chat runtime supervisor
* Initialize process-owner fixtures with an isolated app environment
* Retire provider output transports and failed ownership drafts
* Finish provider stops when the session group empties
* Complete native cleanup from verified watcher exit and cancel held launches
* Let native watcher finish one-shot provider exits
* Retire late ownership records after canceled provider launches settle
* Reap each provider subtree in an isolated native parent
* Preserve provider outcomes and compatibility with native parents
* Publish actual provider identities and retire native parent observers
* Retire numeric writer PIDs when their group is proven absent
* Retire provider transports and accept proven group absence
* Fence retired process identities across asynchronous cleanup
* Use native timer types and readonly process fixtures
* Reuse bounded timeout for compatibility output drain
* Release launch scopes held by late transport error handlers
* Keep processless launch failures out of watcher waits
* Align lifecycle validation with final ownership contracts
* Remove duplicate helper preparation from the dev launcher
* Keep legacy fallback in place and simplify native ownership handoff
* Defer background provider maintenance until the first window
* Release startup hook maintenance for terminal launches
* Use relocated artifact module in native prebuild scripts
* Preserve agent failure outcomes and clean tools before ownership is lost
* Budget ownership capture for its bounded identity reads
* Keep lifecycle regressions at their behavior-owning seam
* Explain the fake-clock process-read fixture
* Capture tool ownership before restart recovery removes the CLI
* Skip descendant inventories for absent provider roots
* Make final output drain regression test deterministic
* Keep output drain fixture assertions type-safe with IPC
* Use existing provider fixtures across Node and Bun
* Prepare native provider helper for Codex contract CI
* Verify provider ownership using its recorded start precision
* Preserve exact provider ownership through reader failures
* Retire exhausted recovery records without blocking watcher cleanup
* Distinguish exited descendants from unreaped zombies
* Preserve group retirement without trusting an exited root
* Keep CLI input owned through native parent loss
* Keep watcher cleanup proof through lost-parent retirement
* Guard retirement against late watcher cleanup proof
* Contain provider launches that fail before stdio setup
* fix(claude): preserve startup diagnostics after input pipe failures
* fix(provider): capture lost outcomes before native completion cleanup
* fix(provider): retire speculative captures after a valid outcome
* fix(provider): share spawn absence classification through its existing boundary
Add 361 desktop and 633 mobile translations for English keys that still
fell back to English: workspace cleanup, the MCP server panel and sign-in
requests, subagent views, automation runs, worktree cards, Memory Saver,
account rename, PR updates and the freeze report on desktop, and most of
the mobile pull request, source control, tasks, agents and session screens.
Mobile code often calls a plural key literally as t('key_one') when the
count is 1, and i18next looks that key up as written, so zh showed English
for a single item. Add the explicitly called _one keys, each equal to its
_other value.
Also correct two browser search keywords that rendered cookies as 曲奇饼,
and entries that called archive scripts 存档 where the catalog says 归档.
The worktree cards "New" badge keeps 新功能 via a key override, mobile
"Start workspace" matches the desktop wording, and an automation's Active
status and list group read 已启用 (paired with 已暂停) instead of 当前.
Co-authored-by: x-Ai <5061489+x-Ai@users.noreply.github.com>
Co-authored-by: Neil <neil@stably.ai>
* Share Codex account history through folder links into ~/.codex
Each Codex account home keeps its login; its history folders become folder
links (junctions on Windows) into the user's ~/.codex, and Codex's databases
follow through a sqlite_home line in the account's own config. Migration is
automatic before the next launch in each home; the store's copy wins a name
conflict and the account's copy is kept beside it. The per-file history bridge,
its link pass and the WSL bridge are removed. Claude's merge-then-link moves to
a shared async module both providers use.
* Make account history moves safe under concurrency and keep the DB with the folders
Files move by link-then-unlink so a move never replaces an existing name, host
passes run one at a time per store, index markers are written before a move,
account-only folders are shared, lock folders are moved rather than deleted,
and sqlite_home is written only once a home's sessions are linked.
* Let the history pass own sqlite_home, link locks first, and index per store
The pass that links a home's folders now writes and removes its sqlite_home
line; the config mirror only carries it forward. thread-writer-locks is linked
before any history, index markers are kept once per store (hard-linked
duplicates included), WSL links the launched home before Codex starts, passes
queue per home in request order, and re-sharing after off then on works with
earlier conflicts still kept.
* Never overwrite on move, gate indexing on moves, and read the shared DB for backfill
Files move by link or exclusive copy; repeat conflicts get their own pending folder; secrets and
sandbox setup stay per home; the sqlite_home write retries against a concurrent mirror; indexing
waits until no move is running; backfill checks read the DB where sqlite_home puts it.
* Keep live writers' files, require both history links, and keep unmoved history on removal
Files move only by a new name for their inode; a home is shared only when sessions and
archived_sessions both link; reverted-thread rollouts get index markers; settled homes skip
repeat passes in either mode; account removal keeps a real history folder.
* Give resume test runtime-home mocks the account history step
* Keep unmoved WSL history on removal, prepare the launched home, and retry incomplete work
WSL account removal keeps real sessions/archived_sessions; a launch prepares the account it
returns even if the selection changed meanwhile; an incomplete unshare and a failed WSL index
pass stay eligible for a later launch; the guest helper rechecks the distro before each step.
* Keep pinned resumes reachable, finish interrupted unshares, and keep index work from racing moves
A pinned resume only shares; a launch re-prepares when the selection or setting changed; Orca's
sqlite_home line is read only at the config root; a writer-lock link elsewhere keeps the home
private; an unshare finishes its database move on retry; indexing keeps markers a newer move
recorded, retries an incomplete run on a later launch, and merges WSL marker lists.
* Move account history into a store one pass at a time and retry incomplete moves
Two homes merging into one store at once raced on its folders and stranded the second home's
history in its merge folder. Passes now run one at a time per store (host) and per distro (WSL),
a folder that appears mid-move is merged into, and a share with failed moves is not settled.
* Keep one rollout form in ~/.codex, record what sharing left behind, and guard Windows homes from older builds
- A rollout present as .jsonl and .jsonl.zst lands in the store in one form only; the other form moves to the home's .orca-set-aside-rollouts, never deleted.
- Each account home gets a versioned cleanup manifest: set-aside databases, left-behind rollouts with a background content check against the store, store twin pairs, and the shared streak.
- Native Windows homes get a renamed ownership marker before their first junction, so older builds refuse to use or delete them.
- Account removal keeps the set-aside rollouts and the manifest.
* Set a rollout form aside only beside its twin in the store, inventory leftovers off the launch path, and keep account databases on removal
- The .zst moves first and a form is kept out only when the store already holds its twin, so a failed move never leaves the store with neither form.
- The rollout inventory and store twin walk run in the detached check, not the awaited pass; manifest writes are serialized per home and a check applies only to unchanged files; checkpoints are time-spaced.
- A WSL check that runs out of budget resumes on a later launch instead of looping.
- The ownership check reads either marker in one step and the marker rename retries on Windows.
- Account removal keeps the account's Codex databases for the later cleanup release.
* Read the cleanup manifest through a type guard
* Read the cleanup manifest through a type guard over unknown
* Settle only a check's own request, skip queued WSL passes after quit, and validate manifest entries
- A pass finishing during a check keeps its new check request on host and WSL.
- A WSL pass queued before quit no longer starts guest work.
- Manifest rollouts must carry a path, size and mtime to be read.
- The store twin scan reuses the twin module's folder walk.
* Walk the store outside the manifest write and keep databases on removal only for shared homes
- The inventory writes only its own fields onto a freshly read manifest, so it never undoes a streak reset from another process and a launch never waits behind the walk.
- Account removal keeps the home's Codex databases only when the cleanup manifest shows the home was shared.
* Lock the cleanup manifest across processes and validate every field later passes read
- Manifest writes take a file lock, so a WSL check helper can't publish over another helper's streak reset.
- The guard also checks storePath, the content check's store facts, database entries and sharedPasses; anything else is rebuilt from disk.
* fix(mobile): run chat report scripts in an isolated shell frame
* fix(mobile): theme chat visuals at handoff and pin the iOS frame to Android's
* test(mobile): probe the page origin by absolute URL from the visual
Gesture handler 3 defaults enableContextMenu to false on web, so the
transcript's pinch detector cancelled every contextmenu event. Android
WebView shows the selection's Copy / Select all menu through that event,
so long-pressing transcript text left bare selection handles with no way
to copy. Gesture handler 2 attached no listener when the flag was unset.
Opt the detector into the browser context menu, next to the existing
touch-action override, and pin it in the transcript render check.
Fixes#42939
* fix(test): exit vitest workers when their runner dies
Bun fork workers outlived a killed Vitest main process for hours at ~1GB each.
A preload in every worker polls the parent and exits once it is gone; the
node-runtime worker's disconnect listener moves into it because Bun stops
delivering Vitest's IPC messages once a 'disconnect' listener exists.
* fix(test): probe the worker's parent with the real process.kill
Tests that mock process.kill made the parent probe exit the worker.
Let users name, rename and reset labels for saved Claude and Codex accounts without changing credentials or restarting agents. Keep the sign-in email visible across Settings, account switchers, chat usage, CLI and phone surfaces, and identify the account in removal confirmations.
Tracked in #21182.
Co-authored-by: Wooseong Kim <innocarpe@gmail.com>
* fix(git): retire native process groups after abnormal stops
* fix(git): drain worker output after group retirement
* test: retain descendant cleanup until liveness assertion passes
* Remove finished-agent retention and keep sleeping status with panes
* Fix legacy pane projection and sleeping-agent regression fixtures
* Cover sleeping display-only status in parked terminal coverage
* Keep pane conversation identity only across continuous agent observations
* Remove duplicate import and keep sleep fixtures type checked
* Preserve conversation boundaries across replays and inherited clocks
* Cover conversation map stability across a large status batch
* Bound conversation capacity work to changed pane owners
* Pass capacity classifiers their layout input directly
* Finalize conversation provenance once per status batch
* Keep paired snapshot tests focused on observable outcomes
* Type the conversation provenance test fixtures explicitly
* Consolidate agent session imports after main merge
* Preserve provider replacement evidence when resetting conversation continuity
* Separate retention deletion from sleeping agent display
* Restore migration row bucket comparison
* Skip unusable pane identities before title ownership lookups
* Refresh conversation titles when their owning pane changes
* Update completion test sound mock after module move
* Keep finished agent status with sleeping panes and update agents by key
* Forward sleeping pane status and scope paired tab updates
* Preserve keyed selectors and compiler invalidation through final checks
* Keep bound store hooks visible to the compiler and measure published links
* Install provenance measurement before factory capture
* Use a static store hook and name presentation metadata once
* Preserve keyed freshness and atomic agent status publication
* Preserve remote folder dashboard regression after suite retirement
* Model pane wake before live identity reobservation in regression
* Share keyed row transactions and finish main integration
* Align runtime fixtures with keyed agent status reads
* Keep status projections addressed and activity summaries current
* Retire empty workspace status summaries after their source leaves
* Use the standard store fixture for parked terminal graph tests
* Align status fixtures with app types and a fixed test clock
* test: capture stored terminal render failure details
* Read terminal titles and completion prompts from keyed agent status
* Compose foreground agent state in worktree test stores
* test: complete lineage list agent state fixture
* Keep sleeping completion when retiring process authority
* Run durable agent-hook status tests with Node SQLite
* Preserve sleeping Done when renderer retires its process
* Update terminal fixtures for process retirement
* Read sleeping pane resume sources by key
* Bind sleep capture fixture to its live panes
* Pass the pane tree to the sleep capture fixture graph
* Preserve accepted completion identity through sleep
* Pass a nullable title to the status classifier
* Resolve accepted host status once and preserve delivery order
* Drop published sleep status when its host owner retires
* Use the supported remote completion test envelope
* Preserve published activity when filling completed status
* Update imports for main module moves
* Remove an unreachable native chat owner comparison
* Read host and unread card inputs by address instead of per root
A host-scoped sidebar card re-read every root's row and acknowledgement on
any store write, so one card with many sleeping roots paid for other
workspaces' updates. Card host filtering, the summary pill's unread state
and the workspace unread gate now first compare the workspace's projected
row revision and the changed keys of the tab-keyed layout/PTY maps and
the acknowledgement record. Only an addressed change re-reads the roots.
Acknowledge and unacknowledge annotate their writes so readers can skip
keys they don't show.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* Correct sleeping pane test imports after module moves
* Combine duplicate subscription test imports
* Record addressed acknowledgement deletions on row drops
* Type subscription fixture key set for string readers
* Keep accepted updates complete after observer failures
* Seed the send picker with its SSH terminal identity
* perf(layout): skip unused normalization reports in pane commands (#42615)
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Clarify cleanup pinning and ignored-file protection (#42616)
* test: remove 55 low-value suites and assertion driver (#42605)
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
* fix(skills): skip Claude sync scratch folders during skill discovery (#42610)
Claude Code parks replaced skill copies in `.trash` and in-progress syncs
in `.staging` under its skills roots. Discovery walked into both, so each
synced skill showed up as duplicates. Prune those directory names in the
native file walk and in the generated WSL `find` command.
Co-authored-by: Neil <4138956+nwparker@users.noreply.github.com>
* test: remove 78 low-value suites and trim redundant cases (#42621)
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
* Keep a host card's unchanged agent rows after filtering out another host's pane
Re-lineage clones every row once a host-scoped card filters a row out, so an unrelated pane's status write rebuilt the card's row array and re-ran its signal and rollup memos. Reuse unchanged rows as main's sidebar row selector does.
* Seed the Copy Session ID shortcut test through keyed agent status
* Seed the graph payload partition test through keyed agent status
---------
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-authored-by: Jinjing <6427696+AmethystLiang@users.noreply.github.com>
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Co-authored-by: OrcaWin <alpha-eng@stably.ai>
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
Co-authored-by: BingZ <zzb@gxsmjx.com>
Co-authored-by: Neil <4138956+nwparker@users.noreply.github.com>
Align the Windows update harness docs and CLI help with the implemented
cold-restore/survival profiles, document the daemon-log reader, drop
links to unavailable plan/postmortem docs, and fix relocated script and
source paths in freeze-repro, process-host, and crash-survival docs.
Remove stale French Windows RC claims in favor of the stable latest asset.
Fixes#42765
Co-authored-by: Neil <4138956+nwparker@users.noreply.github.com>