The Windows helper checked an agent's --window-id against Process.MainWindowHandle, a z-order guess that moves to a tooltip or another window of the same app. The window id is now the target: a live, visible top-level window of the target process, carried through the tree read, frame, screenshot, raise, keyboard input and the observe after the action.
Co-authored-by: toodeceptive <137078450+toodeceptive@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
v1.4.260 moved mobile/src/worktree/agent-row-display.ts under agent-lineage/
and was the first release to keep native chats in SQLite behind worker threads.
- Archive both phone row reader locations as optional paths and resolve moved
modules under mobile/src through releaseModuleLocation().
- Bundle each SQL-backed release's own journal worker/reader entries and mock
its worker-bundle fixture to point at them; read those releases' chats with
their own readTestJournalSnapshot instead of journal.snapshot().
* feat(jira): reorder the Tasks board lanes by dragging their headers
Jira's board configuration decided the lane order and there was no way to change it in Orca. Column headers are now drag handles, with ArrowLeft/ArrowRight as the keyboard equivalent, and the resulting order is saved per board on the device. Jira's Agile API exposes board column order read-only, so this is an Orca view preference and never edits the Jira board.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix(jira): make the saved lane order survive Jira column inserts and filtered lanes
Review follow-up. Board column keys were derived from the column index, so inserting a column in Jira orphaned every saved lane position; they now come from the column's status ids, which Jira keeps stable across config edits. Saving a reorder also replaced the stored order with only the lanes currently on screen, dropping the saved position of any lane a filter had hidden; the new order is merged into the saved one instead. A keyboard move now restores focus to the lane it moved, and the rendered probe asserts two arrow presses in a row land.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix(jira): tell screen readers a lane's issue count and its arrow-key move
Review follow-up. The lane header's aria-label replaced the visible header text, so assistive technology no longer heard how many issues the lane held, and nothing said the header moves with the Left and Right arrow keys. Both now ride on aria-description, translated in every catalog including the newly added Portuguese one, which also gains the existing reorder label.
Also registers the lane-order storage module in the WSL-move localStorage inventory, as the sibling view-mode change did, and follows the jira-types move on main.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(jira): keep the saved lane order across a runtime reconnect
Review follow-up. The lane order was stored under the status-order cache key, which ends in the provider runtime session generation. That counter restarts at zero on every launch and moves on every runtime focus change and remote session start, so a reconnect or a relaunch read the order back under a different key and silently fell back to Jira's order.
The storage key is now built from the task source, the owner's identity without the generation, and the Jira project. The generation-free identity is split out of getEnvironmentRuntimeContextKey rather than duplicated, and the status-order cache keeps its generation.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Neil <neil@stably.ai>
* feat(notifications): mute notifications per worktree
Add a per-worktree notification mute, toggled from the worktree context
menu. Muting silences the interruptions for that worktree (OS banner,
notification sound, mobile push, tray attention dot) while keeping the
passive unread indicators, and shows a small bell-off icon on the card.
The flag is stored in PersistedUIState as notificationsMutedByWorktree
(opt-in entries only), riding the same rails as showDotfilesByWorktree:
debounced writer baseline, hydration sanitizer, paired-client UiUpdate
schema, worktree delete cleanup, folder-rename re-keying, repo removal
pruning, and profile transfer.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* docs(notifications): document the touched per-worktree flag helpers
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* fix(notifications): adapt the mute gate to the attention-sink and WSL-move ledgers
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: Neil <neil@stably.ai>
* 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
* fix(plugins): show only what an update adds in its review
The update review compared Before and After columns that mostly repeated what the user had already
approved, and labelled new custom editors, hooks, settings pages and status bar items with the
vague "Features that act for you". It now lists just the additions, naming each one (a new editor
names the file types it opens), and says so plainly when Orca couldn't compare the versions,
opening the full access list.
* fix(plugins): keep a failed comparison and every grant visible in the update review
- Says Orca couldn't compare whenever main sent no comparison, even when the source also moved, and
opens the full access list then.
- Lists every new grant main asks about, not only the ones this plugin type can use.
- Names editor growth per editor id: new file types, files it now opens by default, else a generic
line; waits for the installed manifest so the line doesn't change under the reader.
- "Adds panels" and "Reacts to more Orca events" replace "Panels" and "More events".
* feat(plugins): approve held updates from the toast, open the review anywhere, group approvals
- The review and the toast name each plugin's publisher ("Official · stablyai", "Community · …").
- The held-update toast lists each plugin with what it adds and the not-official warning when one
applies, and approves in place when every update was compared and can install; otherwise, or
for more than three plugins, "Details" opens the review.
- The review opens over the app instead of sending the user to Settings → Plugins.
- Several updates that need approval are one grouped review with a checkbox each and one
"Approve & update", instead of a separate Review per plugin.
* fix(plugins): offer approval only once every addition is shown, keep late notices
- The toast and the review read the installed manifest with the preview, so "Approve & update"
exists only once every line it approves is on screen; the toast also needs the installed entry.
- A notice that arrives while the toast installs stays on screen; a newer version of a plugin
reloads its details instead of showing the old ones.
- Retrying in the toast skips the updates that already landed; an update whose bytes changed
after review says it waits in Settings → Plugins instead of reporting success.
- In "Update all…", approvals beside plain updates start unticked; the not-official warning sits
under its plugin's name and names the catalog owner.
- The toast e2e covers Details and approving in place.
* fix(plugins): a compact community badge and a history link in the update review
- "Community plugin · owner" with the warning icon replaces the not-official banner in the review
and the toast; the trust advice shows on hover or focus.
- The version text links to the plugin's history on GitHub at the reviewed commit, and a moved
repository is one short line instead of two URLs.
* refactor(plugins): share update loading and installing, keep the toast out of the store
- One loadUpdate and one installUpdates serve the review and the toast; both now say when an
update's bytes changed after review.
- The notice store holds data only; PluginUpdateReviewHost renders the toast and the dialog.
- The update lines users approve are protected copy; the version link sits outside the checkbox
label; a community plugin that runs no code gets the same "Community plugin" label, unmarked.
- Tests for notice merging and for approving only the reviewed fingerprint.
* fix(plugins): a warning Badge variant for the community badge; tests without casts
* feat(tab-bar): customizable icon row for the + menu's create actions (#40359)
The + menu's New Terminal/Browser/Markdown/Open Markdown/Mobile Emulator rows become one
row of icons. A gear at its end opens a customizer to reorder (drag or Alt+Up/Down), hide,
and assign shortcuts to each item; the icon strip scrolls sideways when plugin file types
overfill it. A turned-off Mobile Emulator shows under Hidden and can be turned back on from
there, and the intro callout's Hide now only removes it from the menu (with Undo).
Shortcut validation and saving move into useKeybindingActionEditor, shared with the
Settings shortcuts pane.
* fix(tab-bar): address review on the + menu icon row
- Move Reset Order and All Keyboard Shortcuts into a ⋮ menu in the customizer header.
- Give the floating panel its own layout and no emulator Off item (newTabMenuSurface).
- Escape closes the menu while an icon tooltip is shown; recording ends once focus leaves it.
- Row is labelled as a whole with aria-activedescendant on the chosen icon; e2e selectors
target the icon buttons.
- Don't persist a turned-off emulator as hidden; normalize layouts on settings load.
- Reuse tab-strip resize/wheel helpers, share the recorder-focus hook, split the icon strip,
use ShortcutKeyCombo in tooltips and an allowed elevation for dragged rows.
* fix(tab-bar): keep the create row React Compiler-clean and stop swallowing wheel when it fits
* fix(tab-bar): address CodeRabbit review on the + menu icon row
- Return both layouts in the paired-client settings projection.
- Keep unavailable items at their saved slot when re-saving a layout.
- Ignore shortcut saves that finish after a newer recording session started.
- Make the customizer scrollable; announce the chosen icon via a live region.
- Confirm the intro's Hide only after the write succeeds.
- Render compact recorder chips with ShortcutKeyCombo.
* test(tabs): reproduce drops landing in the other split beside a scrolled strip
* fix(tabs): resolve tab drops against visible tabs in the split under the pointer
* test(tabs): size the e2e strips so the gap and mid-drag scroll cases have room
* test(tabs): drop the mid-drag scroll e2e; it passes without the fix
* fix(tabs): read the drag geometry inside the collision callback, not during render
* fix(sidebar): let a row click hand typing to the opened terminal again
Since 1.4.259 a plain click on a workspace row parked keyboard focus on the
sidebar list and marked it as keyboard navigation, so terminal and chat focus
requests yielded and typing went nowhere until a second click (STA-15458).
The same stale mark also swallowed explicit focus requests such as
`orca terminal switch`, which reported success (STA-15415).
- Only a modifier click (multi-select) claims list focus; a plain click
hands keys to the opened workspace's terminal or chat.
- Any pointer press ends list keyboard navigation again, so a click after
arrow keys or a modifier click, and agent-row clicks, also hand focus off.
- The focus-list shortcut marks keyboard navigation so a terminal that
finishes mounting afterwards cannot take the keys back.
- Explicit pane focus requests (CLI/notification focus, agent rows) end
sidebar list navigation before focusing.
The delete shortcut still acts only on sidebar-selected rows while the list
has keyboard focus, and never on a hovered row.
Co-authored-by: Pr1p <48266347+Pr1p@users.noreply.github.com>
Co-authored-by: Pranav Tomar <43115768+Mystery01092000@users.noreply.github.com>
* test: give the sidebar focus fixture rows aria-selected
* fix(sidebar): re-clicking the open workspace row hands its terminal the keys
---------
Co-authored-by: Pr1p <48266347+Pr1p@users.noreply.github.com>
Co-authored-by: Pranav Tomar <43115768+Mystery01092000@users.noreply.github.com>
The browser tab's phone banner only offered Take back. Add a ghost Take back all next to it that restores every phone-held terminal and browser tab, sharing the logic with the terminal banner.
Co-authored-by: Aleksei Tcelishchev <1243074+casualuser@users.noreply.github.com>
Take back all only restored the PTYs the phone held, so a browser tab the phone was driving stayed locked at phone size. Reclaim every mobile-driven browser page alongside the terminals; held-fit Restore all still only resizes.
Co-authored-by: Aleksei Tcelishchev <1243074+casualuser@users.noreply.github.com>
* 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>
* Bound retained desktop browser guests by idle page count
* Type the browser guest retention regression fixtures
* Update document visibility after React commits
* Preserve current page recency and private document audio protection
* Avoid observer handshakes on child-frame load completion
* Complete the browser certificate replay WebContents fixture
* test(browser): complete guest protection fixture contracts
* fix(browser): retain the saved page catalog after guest reclamation
* fix(browser): preserve inventory ownership and global tab order
* fix(browser): scope inventory ownership work to browser workspaces
* Complete browser cleanup mocks after main sync
* fix(browser): retain edited documents and earlier history
* test(browser): complete document guest history fixture
* test(browser): assert history transition publication
* Restore reclaimed browser pages before commands and retain active owners
* Fix native idle-page eligibility and retain canonical reclaim order
* Keep browser inventory recovery fixtures faithful to saved pages
* fix(browser): retry eligible guests and avoid default debugger acquisition
* fix(browser): publish owner protection before discard retries
* test(browser): isolate protection acquisition before release
* test(browser): keep preview input fixture native-shaped
* Fix browser lifecycle fixture typecheck coverage
* fix(browser): finish guest discard admission before replying
* fix(browser): retire only the hidden page surplus
* fix(browser): retain cold recovery and modal ownership boundaries
* test(browser): complete successful native load before stopping
* Preserve browser page ownership across profile replacement
* Typecheck connected browser profile fixtures in their owning project
* Import browser disposal operations from their owning module
* WIP: interrupted command-target repair (stopped 11-14 for Brennan's no-cap ruling)
* Keep browser commands on the selected page after idle discard
* Limit page-close routing cleanup to its current references
* Guard page close against unrelated routing work
* Type the routing retention probe by its owner
* Add a Memory Saver setting for idle browser pages
Settings > Browser gets a Memory Saver switch (on by default, kept under the
existing kill-switch key) and an "Unviewed for" hours field (1-168, default 4).
Main re-keys idle deadlines live from when each page hid, so turning it off
stops pending frees and changing the hours applies without a restart.
* Let main alone gate Memory Saver and key idle deadlines by hide time
Changing the hours no longer walks every tracked page: the heap is keyed by
when each page hid and the shared offset is applied at the head. The renderer
no longer vetoes on the setting or reinstalls its listener on toggle, so a
toggle sends no visibility replay and can't strand an in-flight page.
* Document the fixture casts in the browser inventory publication test
* Await the now-async window graph sync in browser inventory tests
---------
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* refactor: group process and platform modules by ownership
* refactor: preserve moved module workflow routing
* refactor: preserve native loader and embedded bundle origins