Desktop-hosted pages of remote workspaces now render the shared chrome toolbar and ⋯ menu (without profile and extension entries), the hard-reload menu, zoom and viewport chips, the favicon, the floating-split close button and a Cancel action on download toasts. Viewport presets size the page box and pan it as on a local page.
Co-authored-by: Pr1p <48266347+Pr1p@users.noreply.github.com>
Co-authored-by: oliver-mee <102673257+oliver-mee@users.noreply.github.com>
* fix(browser): disable Back/Forward on server pages with no history
Streamed server pages kept both arrows enabled because hosts used to publish
canGoBack/canGoForward as always false. Hosts now advertise
browser.tab-history-state.v1, and the toolbar and context menu follow the
published history state for them; older hosts keep both arrows enabled.
* fix(browser): publish same-address history changes and re-probe after reconnect
A pushState that keeps the address now republishes the server tab, so Back
enables. The capability answer is dropped when the client regains contact,
since a reconnect may reach an older runtime.
* test(browser): note why the replay test casts its listener
* fix(browser): stop CLI page commands waiting on a loading subframe
waitForBrowserPageReady gated on isLoading(), which stays true while only
an iframe loads, but waitForBrowserGuestLoad settles only on main-frame
did-finish-load/did-fail-load. A page that added an iframe after load made
every eval/goto/snapshot/tab show wait 30s and fail with
browser_navigation_failed. Gate on isLoadingMainFrame() instead.
Fixes#43655
* test(browser): stub isLoadingMainFrame in remaining browser guest doubles
* fix(linear): list every Linear issue and project when --limit is omitted, and report search totals
orca linear list and orca linear project list treated an omitted --limit as a 20-row cap and read one clamped page, so an agent counting a longer queue saw the first 20 rows reported as the whole list. Omitting --limit now walks Linear's cursor pages to the end, bounded by the same read budget list-issues uses; a read that stops on that budget sets truncated/hasMore instead of looking complete, and meta.limit is null. An explicit --limit keeps its existing clamp.
orca linear search stays capped by relevance but now asks Linear for searchIssues.totalCount and reports meta.total ("showing 5 of 349") when every searched workspace returned one; it never invents a total.
Carries the design of #17056 (port of #16119) onto the current multi-workspace Linear modules. Tracked in STA-5249.
* fix(linear): requeue between pages of uncapped Linear walks and keep the merged list a true prefix
An uncapped project or single-workspace issue walk held one of the four shared Linear request slots for up to the whole read budget, so other Linear reads in the app could queue behind it. Project walks now requeue between pages and single-workspace issue lists use the per-page multi-workspace path. Uncapped multi-workspace issue lists no longer re-sort everything collected before each page, and a budget-stopped walk returns only the span every unfinished workspace has covered.
* refactor(linear): move search total aggregation out of issue-context-resolution to stay under max-lines
* perf(linear): fetch summary fields for agent list walks and stop them at the read budget after queueing
orca linear list and project list fetched every Linear issue's description and labels, and every project's content, history, members and labels, then discarded them; with the full walk that waste grew with the whole collection. The agent list paths now ask Linear only for the fields they return (a $detail switch keeps the app's full queries unchanged). A continuation page that waited for a request slot past the read budget is no longer started, and the agent RPC's cancellation signal now reaches the request queue and the Linear client.
* fix(linear): pass the project-create signal through the new options, skip a project page admitted past the read budget, and stop before requeueing a satisfied capped read
* 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>