[brennanb2025]

	Files	Added	Deleted	Net
Test	2	$\color{#1a7f37}{\Huge{\mathbf{+}}}$​56	$\color{#cf222e}{\Huge{\mathbf{−}}}$​15	$\color{#1a7f37}{\Huge{\mathbf{+}}}$​41
Prod	14	$\color{#1a7f37}{\Huge{\mathbf{+}}}$​387	$\color{#cf222e}{\Huge{\mathbf{−}}}$​119	$\color{#1a7f37}{\Huge{\mathbf{+}}}$​268

ELI5

Antigravity chats need Google's separate Antigravity chat server. An earlier version of this stack downloaded it silently the first time a chat started: about 18 seconds of "Working for Ns" with no progress and no Cancel, and every extra chat opened started another download. Now nothing downloads until the person clicks Install, which shows the size, progress and Cancel in Settings and in the new chat.

This PR adds the way back out: a "Remove" link in Antigravity's status line in Settings deletes the server Orca downloaded. It asks first, because removing it stops running Antigravity chats. It also stops showing Antigravity's install state as a separate outlined box inside its provider row: the state is now the row's grey status line, like every other agent's "Installed".

What Changed

This revision: the install state moved out of the outlined box into the provider row's status line, with its actions as text links, and the dialog wording was tightened ("there" read oddly). Remove's reply goes through the same subscription-aware store as Install (#29048), and every client sees the outcome through the host's pushed status.

• Before: the Antigravity row in Settings > Chat > Providers showed its install state in a bordered box nested inside the row (it rendered as a bright outline), offered Install, Reinstall and Update, and had no way to remove the download. Accounts > Antigravity showed the same box.
• After: Antigravity's row has the same shape as the other agents' rows: its install state is the grey status line under the name, and its actions are text links in that line, the same way "Not installed · Install" works for the others. Accounts > Antigravity shows the same line.
  • Not installed: "Not installed · 112 MB download." with a solid primary Install button at the right of the row, next to the switch, so the one thing to do stands out. Downloading: "Downloading X MB of Y MB" with a thin progress bar, then "· Cancel". Cancelled or failed: the reason, then "· Try again".
  • Installed: "Installed · Remove". A healthy install no longer offers Reinstall; a damaged copy reads "… damaged · Reinstall · Remove", and an out-of-date one "Installed · Update · Remove".
  • Remove opens "Remove the downloaded Antigravity runtime from {host}?" with "Antigravity chats that are running stop. Their history is kept." and Cancel and Remove. {host} is the paired host's name, or "this computer".
  • While the host removes it, the row says "Removing…" with no buttons. When it is done the row reads not installed again, with Install, and a new Antigravity chat shows the Install card.
  • If the host refuses (for example, a process it couldn't stop), the line shows the host's reason and keeps "Remove" so you can try again.
• Remove appears only in Settings, never in a chat, never while an install runs, and only when the host supports removal (managed-runtime.remove.v1). Whether a copy is there comes from the host's canRemove alone. New strings are translated into all six languages.
• Mechanism: the row calls managedRuntime.remove (feat(runtime): remove an agent's downloaded runtime only once nothing on the host can still run it #29139) and applies the returned status to the shared per-host install status store when it belongs to the current subscription, as Install does; every row for that host, and that host's chat Install card, then follow the host's pushed status to the outcome.

Why

Removal is rare and destructive, so it is a quiet link in Settings behind a confirmation. Showing the state as the row's own status line, with the same inline links the other agents use, removes the nested outlined box and keeps every provider row the same shape. All the safety lives on the host (#29139). The row just asks, and shows what the host reports.

Linked Issue

N/A (maintainer; part of the Antigravity Chat UI stack).

Visual Proof

Screenshots from QA round 7 on macOS, dark theme, at this PR's head 95b3e264425 (hidden dev build, throwaway profile).

Not installed, Install button (round 8)

Testing

• I manually tested these changes locally

• Automated tests added/updated, or explained why not below

• The row's label table gains the removal cases: "Removing…" with no buttons, a refused removal that keeps Remove beside the host's reason, a damaged copy that offers Reinstall and Remove, a healthy install with no Reinstall, and no Remove in a chat.

• Lint, typecheck and the full test suite run in this PR's CI.

Review

Agent skill upstream boundary

• Not applicable, or this change copies or mechanically translates no upstream skill-installer source, tests, fixtures, registry entries, path tables, comments, or documentation.

QA, round 2 (M4Air, 10-16, older build 2efa3308959 with the outlined box and the old dialog wording; Grok drove the hidden window over the Chrome DevTools Protocol only)

• The Remove dialog read "Remove the downloaded Antigravity runtime from this computer?" / "Running Antigravity chats there stop. Your sign-in and chat history are kept.". Confirming showed "Removing…", then Install again in Settings, and both open chats showed the install card in the same frame. The runtime folder was gone afterwards.

Notes

• SSH and remote hosts: the row talks to the host it belongs to. Settings > Chat > Providers is this machine only; the Accounts row follows the chosen host.
• Mixed versions: a host without managed-runtime.remove.v1 shows no Remove link.
• PR author: @BrennanKB5

Differences from the common pattern

• Intended: Remove stops this host's running Antigravity chats first (the dialog says so) instead of refusing until the person stops them; it still keeps the files if any of them can't be confirmed stopped. The common pattern's own sign-out confirmation stops running chats the same way.
• Intended: in this PR Remove stays enabled whatever else the host is doing, and a refusal from the host (for example during a sign-in) shows under the row. The sign-in row arrives in feat(settings): sign Antigravity chats in from Accounts #28705, which then disables Remove and Install while a sign-in runs, as the common pattern does.
• Intended: removal shows "Removing…" on every connected client, not only the one that clicked, because the host runs it as a reported operation (feat(runtime): remove an agent's downloaded runtime only once nothing on the host can still run it #29139) that can take seconds while chats stop.
• Intended: Remove appears only when the host supports removal, so an older paired host never gets a request it can't answer.
• Intended: the confirmation is Orca's in-app dialog rather than a native one, as every Orca settings confirmation is.

Checklist

• This PR is small and focused
• I explained what changed and why (ELI5, the user-facing before/after, the mechanism, and why over the alternatives)
• Before/after screenshots or videos attached for UI changes, or N/A with reason
• Self-reviewed for correctness, security, and performance
• Cross-platform, SSH/remote, and path/shortcut impact considered (or N/A)
• pnpm lint, pnpm typecheck, pnpm test, and pnpm build pass (or CI will cover; local preferred)

[OrcaWin]

QA (dev build of #28705 head ae28388, which includes this PR, on macOS): Remove downloaded runtime — PASS

• After install, a trash button appears with the tooltip "Remove downloaded runtime". It doesn't appear while installing (that state shows "Cancel installation").
• The confirm dialog reads "Remove Antigravity from this host?" / "Running Antigravity chats stop. Chat history is kept." Cancel keeps everything installed.
• Removing while a chat process was alive: "Removing…" showed for ~1s, the process exited 0.55–0.91s after confirm, and Settings settled at +0.99s back to "Install Antigravity". The runtime folder is deleted. The chat keeps its history and shows "Install Antigravity to start chatting." in place of the composer. Reinstalling brings the composer back.

Non-blocking: (1) while "Removing…" is showing, the Sign in button below still renders enabled for that ~1s. (2) After removing during a live turn, the chat shows "Antigravity couldn't start. Send your message to try again." even though the composer has been replaced by the install row.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: f3c6f143-d5b5-43da-aabb-7c4a40a96203

📥 Commits

Reviewing files that changed from the base of the PR and between 95b3e26 and b296a95.

📒 Files selected for processing: 5

• src/renderer/src/components/managed-runtime/ManagedRuntimeInstallRow.tsx
• src/renderer/src/components/managed-runtime/managed-runtime-install-view.test.ts
• src/renderer/src/components/managed-runtime/managed-runtime-install-view.ts
• src/renderer/src/components/settings/AntigravityAccountsSection.tsx
• src/renderer/src/components/settings/NativeChatProvidersSetting.tsx

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.

📝 Walkthrough

The managed runtime UI now reports whether a runtime can be removed and displays a confirmation dialog for eligible runtimes. Removal requests use shared operation handling with generation checks. The view model represents removal in progress and includes action labels, status, and download-size notes. The runtime status row uses an inline layout with install, cancel, and removal actions. Removal labels are added in English, Spanish, French, Japanese, Korean, and Chinese.

Priority: ⬇️ Low

Merge Risk: 🔵 Low · up to b296a

Removal remains available when the provider switch is off, but closing the confirmation can leave keyboard focus without a useful target. This is a bounded accessibility issue to address or explicitly accept before merging.

Pre-merge checks: 4 · 1

Failed checks: 1 warning

Check name	Status	Explanation	Resolution
Docstring Coverage		Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 18 functions across 10 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

Passed checks: 4 passed

Check name	Status	Explanation
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.
Title check		The title clearly and concisely describes the primary change: removing a downloaded agent runtime from its Settings row.
Description check		The description is complete and focused. It includes the required user-facing explanation, changes, rationale, testing notes, visual proof, compatibility considerations, and checklist. It also explain…

Full details: Description check

Explanation

The description is complete and focused. It includes the required user-facing explanation, changes, rationale, testing notes, visual proof, compatibility considerations, and checklist. It also explains that the PR is maintainer-owned and does not require a linked issue or AI disclosure.

• Fix all pre-merge checks with AI

✨ Finishing Touches: 💡 1

📝 Generate docstrings: 💡

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

---

ℹ️ Review info

⚙️ Run configuration

• Configuration used: Repository UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: eb68ff2d-caa3-4be2-ad3f-6d3c3f2025a2

📥 Commits

Reviewing files that changed from the base of the PR and between 6fd2172 and 0017412.

📒 Files selected for processing: 13

• src/renderer/src/components/managed-runtime/ManagedRuntimeInstallRow.tsx
• src/renderer/src/components/managed-runtime/ManagedRuntimeRemoveButton.tsx
• src/renderer/src/components/managed-runtime/managed-runtime-install-view.test.ts
• src/renderer/src/components/managed-runtime/managed-runtime-install-view.ts
• src/renderer/src/components/native-chat/NativeChatStructuredSession.launch-lifecycle.test.tsx
• src/renderer/src/i18n/locales/en.json
• src/renderer/src/i18n/locales/es.json
• src/renderer/src/i18n/locales/fr.json
• src/renderer/src/i18n/locales/ja.json
• src/renderer/src/i18n/locales/ko.json
• src/renderer/src/i18n/locales/zh.json
• src/renderer/src/runtime/managed-runtime-install-status.ts
• src/renderer/src/runtime/use-managed-runtime-install.ts

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 5 remain after this review.

[coderabbitai]

Actionable comments posted: 1

---

ℹ️ Review info

⚙️ Run configuration

• Configuration used: Repository UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: c578b16d-dc8f-4b8e-9714-11d5e088927e

📥 Commits

Reviewing files that changed from the base of the PR and between 0017412 and 95b3e26.

📒 Files selected for processing: 12

• src/renderer/src/components/managed-runtime/ManagedRuntimeInstallRow.tsx
• src/renderer/src/components/managed-runtime/ManagedRuntimeLinkButton.tsx
• src/renderer/src/components/managed-runtime/ManagedRuntimeRemoveButton.tsx
• src/renderer/src/components/managed-runtime/managed-runtime-install-view.test.ts
• src/renderer/src/components/managed-runtime/managed-runtime-install-view.ts
• src/renderer/src/components/settings/NativeChatProvidersSetting.tsx
• src/renderer/src/i18n/locales/en.json
• src/renderer/src/i18n/locales/es.json
• src/renderer/src/i18n/locales/fr.json
• src/renderer/src/i18n/locales/ja.json
• src/renderer/src/i18n/locales/ko.json
• src/renderer/src/i18n/locales/zh.json

🚧 Files skipped from review as they are similar to previous changes: 3

• src/renderer/src/i18n/locales/es.json
• src/renderer/src/i18n/locales/ja.json
• src/renderer/src/i18n/locales/ko.json

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 2 remain after this review.

[coderabbitai]

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

🔎 Supported by static analysis

🏁 Script executed:

set -eu
printf '%s\n' '--- component ---'
nl -ba src/renderer/src/components/managed-runtime/ManagedRuntimeRemoveButton.tsx
printf '%s\n' '--- dialog-related imports and definitions ---'
rg -n -F --glob '*.{ts,tsx}' -e 'ManagedRuntimeRemoveButton' -e 'DialogContent' -e 'DialogTrigger' -e 'DialogPrimitive' -e 'function Dialog' -e 'const Dialog' src/renderer/src | head -200
printf '%s\n' '--- candidate dialog files ---'
rg --files src/renderer/src | rg '(^|/)(dialog|modal|Dialog)[^/]*\.(ts|tsx)$|components/.*/(dialog|modal|Dialog)[^/]*\.(ts|tsx)$' | head -100

Repository: stablyai/orca

Length of output: 25332

---

🏁 Script executed:

set -eu
printf '%s\n' '--- dialog wrapper ---'
nl -ba src/renderer/src/components/ui/dialog.tsx
printf '%s\n' '--- Radix dialog declaration ---'
rg -n -F --glob 'package.json' -e '@radix-ui/react-dialog' -e 'radix-ui' .

Repository: stablyai/orca

Length of output: 9175

---

🌐 Web query:

Radix UI dialog v1.6.7 DialogContent onCloseAutoFocus behavior when Dialog has no DialogTrigger controlled dialog

💡 Result:

Assuming you mean **`radix-ui@1.6.7`** (the umbrella package), not `@radix-ui/react-dialog@1.6.7`: the dialog package has a different version number. The available source for the current Dialog implementation is newer, so I can’t confirm that it exactly matches the implementation bundled in `radix-ui@1.6.7`. ([central.sonatype.com](https://central.sonatype.com/artifact/org.mvnpm/radix-ui/1.6.7?utm_source=openai))

For a **modal** dialog (the default), closing invokes `onCloseAutoFocus`; Radix’s internal handler prevents the browser’s default autofocus and then tries to focus `context.triggerRef.current`. Without a `DialogTrigger`, that ref is `null`, so Radix has no trigger to return focus to. **Inference:** focus restoration is therefore effectively skipped unless you handle it yourself. ([github.com](https://github.com/radix-ui/primitives/blob/main/packages/react/dialog/src/dialog.tsx))

If you need focus restored to the element that opened a controlled dialog, capture that element when opening and focus it in `DialogContent`’s `onCloseAutoFocus`. If you only want to suppress Radix’s default close-focus behavior, call `event.preventDefault()` in your handler. The exact v1.6.7 behavior remains unverified by the sources found.

Citations:

- 1: https://central.sonatype.com/artifact/org.mvnpm/radix-ui/1.6.7?utm_source=openai
- 2: https://github.com/radix-ui/primitives/blob/main/packages/react/dialog/src/dialog.tsx

---

🏁 Script executed:

set -eu
printf '%s\n' '--- lockfiles ---'
rg --files -g 'pnpm-lock.yaml' -g 'package-lock.json' -g 'yarn.lock' -g 'bun.lockb' -g 'bun.lock' .
printf '%s\n' '--- radix lock entries ---'
rg -n -F --glob 'pnpm-lock.yaml' -e 'radix-ui@' -e 'radix-ui:' -e '@radix-ui/react-dialog' . || true

Repository: stablyai/orca

Length of output: 2312

---

🌐 Web query:

@radix-ui/react-dialog 1.1.23 dialog.tsx onCloseAutoFocus triggerRef

💡 Result:

In `@radix-ui/react-dialog` **1.1.23**, `Dialog` creates a `triggerRef`, and `Dialog.Trigger` composes its forwarded ref with that internal ref. When modal content closes, Radix’s default `onCloseAutoFocus` prevents FocusScope’s default and focuses `triggerRef.current`. (GitHub discussion 3319 in radix-ui/primitives (link omitted to avoid creating a cross-reference))

Your `Dialog.Content` `onCloseAutoFocus` runs before that default handler. If yours calls `event.preventDefault()`, the composed handler won’t run, so Radix won’t restore focus to the trigger. The published package is version 1.1.23; the source view available here is the repository’s current `main` branch, not a version-pinned 1.1.23 source file, so exact source-level equivalence to that release is not independently established. ([app.unpkg.com](https://app.unpkg.com/%40radix-ui/react-dialog%401.1.23?utm_source=openai))

Citations:

- 1: GitHub discussion 3319 in radix-ui/primitives (link omitted to avoid creating a cross-reference)
- 2: https://app.unpkg.com/%40radix-ui/react-dialog%401.1.23?utm_source=openai

---

Restore focus to the Remove control when the dialog closes.

This controlled Radix dialog has no DialogTrigger, and the project wrapper does not add an onCloseAutoFocus handler. Radix therefore has no trigger element to focus when the dialog closes. Wrap the control in DialogTrigger asChild, or restore focus explicitly with onCloseAutoFocus.

Source: Learnings