fix(antigravity): improve runtime surfaces, usage discovery, and settings - #655
Merged
Conversation
The machine selector labelled an offline remote machine with an "Offline" caption but still let it be picked, scoping the Agents pages to a machine that cannot answer. List it disabled instead — its server status dot already says why — and drop the caption. The pill floats over the scroll area at `bottom-4`, so the area needs more than `pb-8` to keep its last rows clear of it. Reserve the space only while the bar actually renders (a second machine exists). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…ises Antigravity's two runtimes name the same postures differently: `agy` says `yolo`, and ACP's `yolo` mode normalizes to `never`. The Chat capabilities declared neither `defaultApprovalPolicy` nor `bypassPermissions`, and `capabilitiesForPresentation` only overwrites the keys an override brings — so the CLI's `yolo` leaked onto a surface that never advertised it. Three symptoms, one cause: - a fresh Chat draft opened with no permission selected, - picking Auto Edit reverted to bypass on the started thread, - the chip rendered the raw `yolo` id instead of a label. Chat now derives its own default and bypass posture from the advertised modes (YOLO, matching the provider's declared stance), `resolveApprovalPolicyValue` falls back to that default rather than "" when a saved id is not on offer, and the composer dropdown resolves its value against the current options so no surface can render an unadvertised id. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…alled `subagentExecutionPreference` returned `one-shot` for every machine with `agy` detected, so Crossagents advertised Antigravity as a one-shot child even after its first-class ACP runtime landed. `agy -p` streams stdout and exits: no incremental tool calls, no permission forwarding, no steering. Track the ACP runtime's detected state alongside the CLI's and prefer the structured lane whenever Chat is available, keeping the CLI one-shot as the fallback for a machine that only has `agy`. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Antigravity was the only provider rendering a "Runtime" card above its environment rows, and that card carried no install action — a machine with `agy` but no ACP artifact showed "Antigravity ACP: Not installed" with no way to fix it from the page. The background auto-install is best-effort and silent, so a failed sweep left chat unavailable indefinitely. Report both runtimes through the same row every other provider uses: the version chip becomes `CLI v1.1.22 · ACP not installed`, a missing runtime gets an inline install action (registry artifact or shell installer, per the provider's declared slots), and the combined update takes the row's existing Update affordance. Providers whose settings panel already owns the install rows (Cursor) keep their own grouping. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The first-class ACP sweep marked each agent+environment as attempted before running, so once its two attempts were spent the artifact was never fetched again for the rest of the session. A machine that was offline at launch, or whose probe failed once, stayed without a chat runtime until the app was restarted — with nothing said about it beyond a console warning. Record sweeps as unresolved on failure and allow a later status query to try again after a 15-minute cooldown, settling the entry only on success or on an explicit opt-out. The exhausted-attempts warning now names the retry window and points at the manual install on the agent's settings page. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tickets: None