Spawn the status helper directly instead of through LaunchServices, and have it re-exec itself as its own responsible process so TCC still checks the helper's grant. A timeout now stops the probe by PID, so a late LaunchServices launch can no longer leave a suspended helper behind. Startup kills suspended probes left by older builds.
Co-authored-by: Mikel Vallejo <58292517+VallejoM@users.noreply.github.com>
* Give new agents plain UUID IDs
New Orca session IDs (chats, host-launched chats, terminal agent IDs) are
plain random UUIDs minted by createOrcaSessionId; the agent stays on the
record. Remove the two readers of the agent prefix: the agent.launch
sessionId refinement and the automation Open run guard. Hosts advertise
agent.launch.plain-session-id.v1; the phone reserves a plain ID only for
hosts that advertise it and keeps the legacy spelling otherwise. A replay
an older replacement host refuses as invalid params is now uncertain, not
a definite failure. Old IDs stay valid; nothing is migrated.
* Repair plain agent ID recordings and compatibility checks
* refactor: place shared settings profiles and host contracts with owners
* fix: retire stale cleanup validation contacts
* refactor: consolidate imports from concrete owners
* refactor: bind new card fixture to profile defaults owner
* style: format rebased concrete host import
* refactor: consolidate project header color owner imports
* fix: load released phone readers after folder moves
* fix: preserve released chat readers and current owner imports
* refactor: give chat tabs ownership of composer editors
* Retain pasted-text file paths with composer undo history
* Keep composer selection ownership with its editor
* perf: suspend hidden structured chat effects with Activity
* fix: keep pending chat actions independent of view replay
* Preserve hidden chat handoff and pending host actions
* Keep autocomplete ref writes in their owning hook
* Preserve disclosure geometry and pending images across chat reveals
* Use the native Blob implementation for image lifetime coverage
* Retain sent messages while hidden chats await history
* Wait for the held send request before hiding its test pane
* Preserve pending host reconnect state across chat switches
* Reset retained outage state after a hidden host recovery
* Observe retained chat outage transitions through shared host subscriptions
* Start outage observation for initially hidden chats
* Keep chat feedback timers alive across hidden views
* Settle the retained rail while its view ref is disconnected
* Track the rail node lit by the latest wake
* Preserve the lit rail when hidden input has no view node
* refactor: give chat tabs ownership of composer editors
* Retain pasted-text file paths with composer undo history
* Keep composer selection ownership with its editor
* 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>
* feat(uninstall): add the uninstall cleanup contract shared by main and the settings UI
* feat(uninstall): remove Orca's OpenCode and Pi plugin files, also from the Windows uninstaller
Only files carrying Orca's marker are removed; OpenCode 1.x's TUI registration entry goes with them.
* feat(uninstall): main-process plan, steps and finish actions for Uninstall Orca
getPlan lists agent hooks, the orca command, orca serve units, ~/.orca/agent-hooks and SSH hosts
without changing anything; runStep removes one part and returns the updated plan.
* feat(cli): add orca uninstall, sharing the app's cleanup
* feat(uninstall): add the Uninstall Orca section to Settings → Advanced
* fix(uninstall): narrow plan agent ids with isTuiAgent instead of a cast
* fix(uninstall): show home-relative paths in the uninstall plan
* fix(uninstall): bound the SSH host sub-list with useBoundedHostRows
* fix(uninstall): async fs on the main thread and no type assertions in the cleanup
* fix(cli): bundle the uninstall cleanup modules the orca uninstall command loads
* fix(packaging): unpack the uninstall cleanup entries the packaged CLI loads
* fix(uninstall): call the orca command row the CLI on your PATH
* fix(uninstall): show hook scripts under the agents' hooks row
* fix(uninstall): remove hook scripts after the last agent retry and never show kept items as done
* fix(cli): give orca uninstall and agent hooks an app environment, and exit 1 on unfinished entries
Claude's remover resolves profile homes through it; without one the CLI reported Claude failed.
* fix(uninstall): drop Muse's Orca env-var allowlist and Claude's agent-view marker
Muse keeps names the user added. The agent-view marker only remembers opt-outs for a re-enable.
* fix(cli): bundle and unpack the node service environment orca uninstall loads
* fix(uninstall): settle the agent-view disable before deleting its marker, and report ok:false on unfinished --json runs
* feat(languages): discover and switch community language packs
Show community translations where people choose a language: in the
Settings language dropdown (with a link to the translations catalog), a
single-list language picker that pins the device-matching translation,
a Language button in onboarding, and a one-time quiet suggestion toast.
Switching back to the previous language is always available in English.
* style: format language browser imports
* fix(languages): keep the offer action hook compilable by React Compiler
* test(e2e): drive language catalog retry through the new picker
* 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(sleep): keep a workspace asleep at quit from being reopened on relaunch
* fix(sleep): don't treat running agents' resume records as sleep in the startup fallback
* fix(sleep): keep the startup fallback unchanged for sessions saved without a shutdown list
* chore: prune workspace record read baseline
* style: format
* 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