* refactor: organize renderer store and agent status modules
* test: remove global timer counting from coordinator cleanup
* test: retire queued quit timing case and preserve main graph coverage
* refactor(renderer): group browser and terminal modules by owner
* refactor: consolidate floating workspace type imports
* test: mark worktree card introduction seen in completed profiles
* refactor(renderer): place upstream terminal sleep owners with tab lifecycle
* fix: clarify session history search copy
* fix: keep paired-client notice in session search enable prompt
Restore the notice that authenticated paired clients can search the
index, since the prompt's Enable button turns indexing on directly.
Update the panel search e2e spec for the new prompt and empty-state
copy, drop a unit test that did not fail when the copy change was
reverted, and remove the retired consent key that the rebase brought
back in the ja and zh catalogs.
* fix: localize session search prompt copy and use paired devices wording
Use the reviewed wording "Paired devices can search them too." for the
enable prompt, and add translations for the three new Session History
strings in every shipped locale so the consent stays readable outside
English.
* refactor(ipc): group handlers and PTY support by owner
* chore(test): prune retired IPC timeout baseline
* fix(types): include worktree path settings in web project
Plugin workers now get GIT_TERMINAL_PROMPT=0 so git fails cleanly instead of
prompting. The full-access warning and the authoring docs now say a worker can
use saved logins and SSH keys and that the environment filter is not a sandbox.
Adds tests for dropped code-loading variables and Windows case folding.
* refactor(main): organize agent session and tab lifecycle owners
* fix(ci): carry moved backend test and mobile routing metadata
* test: retire copy assertions in headless notification test
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