openHttpLink, openOwnedHttpLink and openAppHttpLink now return whether
the link opened in Orca's browser, the system browser, or nowhere.
Callers that ignore the value are unchanged. The modifier routing
helper moves to its own module to keep the router under the line cap.
* fix(i18n): update permission and mobile task translations
* fix(i18n): retain community Portuguese pagination copy
Adopt the matching translations from #39124, also carried by #40456.
Co-authored-by: marlico77 <marlonssoficial@gmail.com>
---------
Co-authored-by: marlico77 <marlonssoficial@gmail.com>
* fix: retain prepared checkout cleanup ownership after timeout
* test: retain capacity for unregistered preparation leftovers
* fix: keep expired cleanup admission outside retry budget
* fix: verify original preparation registration before removal
* Retain preparation authority through bounded capacity recovery
* Exercise preparation cleanup failures through real filesystem fixtures
* Inject root mkdir failure without obstructing checkout absence proof
* Match the host filesystem path in preparation failure coverage
* Align preparation fixtures with physical cleanup ownership
* Await owned recovery in the fleet cleanup control
* Release abandoned preparation cleanup maintenance leases
* Match cleanup test identity paths on Windows
* Wait for completed preparation disposal in maintenance regression
* Await final cleanup state in maintenance controls
* feat(settings): group Voice settings like the other panes and fold the setup card into its rows
The setup card is gone. Its switch is the first row (Dictation), and its
messages move to the rows they are about: download progress and updates in
the model list, a missing microphone under Input. The model list is a table
with a one-line description per model, a plain quality word and equal-width
buttons aligned to the card edge.
* fix(settings): keep the delete button's hover reveal off the Button itself
* fix(settings): line up the Voice model table and make the language and repo-hint rows read plainly
* fix(settings): wait for the catalog before the Dictation status, and open the tab that shows the recommended model
* refactor(settings): share the Voice download check, order keep-loaded choices at the source, count model languages from the catalog
The copy / fork / scroll-up row hung 20px into the gap below it in every case, so an
agent's card, a notice, a tool run or the turn's own diff rollup and PR card sat flush
under it. Decide once per slot whether the actions may hang: only when the row draws
nothing after its message and what follows is the person's own bubble or nothing.
Otherwise they keep their own height and the row's estimate is charged for it.
* refactor(orchestration): isolate the legacy remote-attachment code behind one entry per side
Move today's remote-attachment (federation) code, unchanged, into
orchestration/legacy-remote/ (worker server) and
orchestration/legacy-remote-home/ (Run home). Code outside each folder
imports it only through legacy-remote.ts / legacy-remote-home.ts; a test
pins that. No behaviour change.
* refactor(orchestration): keep the legacy entry modules out of import cycles
The DB layer reaches each legacy folder through a DB-only module, and the
federation method arrays are spread where they were before, so no module
loads differently from main when imported first.
* test(orchestration): only the DB layer may use the legacy DB-only modules
* refactor(orchestration): let the two legacy folders import each other directly
They are one frozen unit; going through the other folder's entry module
made the Run-home half load the whole worker-server half.
* refactor(orchestration): import the pinned-server lookup from its legacy sibling
* refactor(orchestration): remove the import cycles the Run-home entry module created
Keep the pinned-server lookup at its original path (shared worker code calls it)
and let the worker list import the fleet snapshot directly; import/no-cycle is
clean again.
* feat(cmd-j): add an extra-results seam for non-workspace palette sources
Sources register through usePaletteExtraSources (empty here, so the palette is
unchanged). Each supplies a section label, rows ranked with the shared match
engine, an empty-query cap, a tie preference, and a placement hint relative
to Workspaces. A source may also hide workspaces it represents from the
Workspaces list while their tabs stay in Open Tabs and recents.
* fix(cmd-j): make extra-result rows keyboard-selectable
Selection skipped the new row type, so Enter could not reach a leading
extra row.
* fix(cmd-j): count extra-result rows in the announced result count
The live region counted only the built-in result kinds, so a query that
matched only extra rows announced zero results.
* perf(mobile): let newer phone shells fetch the language catalog from the desktop instead of downloading all of them
* fix(mobile): hash only the buildId fields so phone readers can recompute it
* fix(mobile): use the catalog chunk when the generation still has it
* fix(desktop): give catalog reads their own read-slot budget
They reopen the WAL-backed dismissal row cache read-only after a
simulated restart, which Bun on macOS cannot, so the restarted store
reads no history.
* fix(review): keep the active review linked through a rebase
A detached HEAD (rebase, bisect, checkout of a commit) is no longer treated
as a branch switch. Only an attached observation can clear the active
review and push target, judged against the branch that last proved
ownership: the in-session branch before the detach, else the owning host's
rebase verdict from the listing, else unknown (never cleared). linkedItems
are never cleared.
- shared rule (hosted-review-branch-ownership) used by the renderer writer
and the runtime WorkspaceGitIdentity
- readRebaseOperation: spawn-free, fail-closed owner-side verdict; git am is
not a rebase
- listings annotate detached rows with the verdict
- explicit push-target pushes refuse while a rebase is active or unverifiable
- opt-in verifyRebaseOperation status verdict gates review AI launches at
the action boundary
* fix(review): gate mobile review actions and bound the rebase listing probe
- mobile fix-checks, resolve-comments and hosted conflict launches require a
fresh owner-side rebase verdict after agent resolution; local conflict
recovery and generic launches are unchanged
- the listing's detached-row rebase probe has a 2s budget; unread rows stay
unknown, and a checkout whose read outlived its budget gets no new one
until it settles
- an empty or malformed HEAD is unverifiable, not a proven detach
- the apply-backend real-Git test is gated on Git 2.26
* fix(mobile): let folder repo review actions launch without a Git verdict
Repo-backed folder workspaces have repo::path ids, so the mobile review-action
gate sent git.status for them and refused the launch. The gate now reuses the
repo the launch context already resolved and, like desktop's isFolderRepo
check, skips the verdict for folder repos; Git workspaces still need a fresh
'none'.
* fix(review): reconcile detached ownership per host and selection
* Fix review action rebase checks for the selected workspace
- Read fresh rebase state from the owning host without a full status scan.
- Rotate detached worktree probes so later worktrees receive checks.
- Avoid reopening the composer when a rebase check refuses launch.
* refactor(review): scope rebase fix to branch ownership
Preserve review associations through detached HEAD using the last confirmed attached branch. Keep unknown ownership conservative and retain host isolation and relink race protection.
Remove the background rebase scanner, rebase-verdict transport, and launch/push gating from this change. Keep the deferred gating work separately and replace the real-Git pipeline tests with focused metadata regressions.
Refreshing a managed Claude profile copied the personal ~/.claude.json
groveChoiceSeenAt map over the profile's map, dropping the profile
account's Consumer Terms confirmation. Every new terminal then made
Claude wait on a network check before starting.
Merge groveChoiceSeenAt per account like projects and mcpServers, and
keep whichever timestamp is newer for accounts present on both sides.
Fixes#40380
Co-authored-by: Neil <neil@stably.ai>
Commands render before skills in the slash menu, so typing an exact skill
name could leave a fuzzy command highlighted and Enter would pick the wrong
item. After each edit or caret move the picker now highlights the row whose
name ranks best against the query. Arrow-key navigation still owns the
highlight between edits, and a catalog refresh keeps the row the user
arrowed to (by id) instead of jumping.
Co-authored-by: Neil <neil@stably.ai>
A stray github.com or bitbucket.org entry in glab's config made the failed
`glab auth status --hostname <host>` probe print a status block headed by a
bare hostname, which the configured-host parser accepted as evidence. The
known-host inventory could likewise list github.com. Because GitLab has
precedence among forge providers, GitHub and Bitbucket repos were offered
GitLab merge requests and GitLab login prompts.
Before trusting any glab evidence, resolveProjectRefForRemote now returns null
when the remote's real host (aliases folded via normalizeForgeWebHost) is
github.com or bitbucket.org. Scp remotes on an SSH alias named e.g. `github`
are unaffected.
Fixes#40386
Co-authored-by: Neil <4138956+nwparker@users.noreply.github.com>
Download progress counted inflated asset bytes, so the caption read
"x of 12.9 MB" while about 4.3 MB of brotli copies travelled. Progress now
counts what the reader moves: each brotli copy where one is read, raw bytes
otherwise, and nothing for reused assets. The first total before any
progress uses the same rule.
The watcher deduped on the public payload (branch, displayName, terminals),
so moving focus between two workspaces that project to the same payload was
dropped. Dedupe on the focused worktree id as well; the emitted payload still
omits that id because it can embed a provider path.
Fixes#40502
Co-authored-by: Neil <neil@stably.ai>
* fix(chat): collapse orchestration notices and keep the rail human-only
* test(chat): assert human-only rail previews
* test(mobile): inspect compact orchestration mail through its disclosure
* test(mobile): keep orchestration coverage in a focused suite
* test: retain the agent source type used by message cases
* fix(chat): keep rail reply previews while ticks skip agent-written inputs
Restores the hover card's reply line (the issue asks to keep the existing
preview), drops the shared test fixture and folds the authorship cases
into the rail and outline tests.
* fix(chat): stop rereading an older host's outline as the history window moves
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Kelvin Amoaba <97001695+AmoabaKelvin@users.noreply.github.com>
The "Update shared content" button inherited Button's whitespace-nowrap and
fixed h-8, so long translations (e.g. Russian) ran past the button edge in
the w-80 share popover. Let the label wrap, and stack the idle and
"Updating…" labels in one grid cell so the button keeps its height while
publishing instead of resizing the popover mid-update.
Fixes#40202
Co-authored-by: Neil <neil@stably.ai>
Chat message tables inherited the shared document renderer's fixed
text-[13px], so they ignored the chat Text size setting. Add a chat-only
0.9285714286em (13/14) override so tables stay 13px at the default 14px
size and scale with the message like the heading overrides do.
Fixes#40389
Feed only listed agents waiting on you, so a phone with agents busy on the
desktop showed none of them. The section now lists agents that need you
first, then working ones, still capped at three with a link to the Agents
tab.
On the phone, Codex's Standard/Fast speed was a Speed row opening a
list while Claude's Fast mode was a switch. A Fast-only speed now uses
the same switch row; more speeds, or a lone Flex, keep the list. The
lone-Fast rule moves to shared code so desktop and mobile follow one
rule.
Shared workers (#40067) keep native addons such as the Windows process tree
and ConPTY loaded across files. Windows workers then exit with 0xC0000374
(STATUS_HEAP_CORRUPTION) in the node-server persistence lane. Production code
loads these addons lazily, so the per-file scan cannot detect them.
* fix(right-sidebar): keep the toggle while a workspace is being created
The creation surface has no titlebar strip and the floating toggle only rendered
with workspace chrome, so closing the right sidebar during creation (or on a
failed creation, which stays up until dismissed) left no button to reopen it.
The toggle button, its shortcut and the menu item now share one rule,
canToggleRightSidebar, so the shortcut also works during creation.
* fix(source-control): read the latest review provider when eligibility fails
The failure fallback read the provider through useEffectEvent, which keeps the
first render's handler inside memo components in React 19.2. A provider that
settled after the probe started was ignored. Read it from a ref refreshed in a
layout effect instead.