Repository navigation
Antigravity Marketplace in Extensions, with chat sign-in - #1064
Conversation
|
This PR changes the test suite by +95 test cases (browser +16, unit +6, server +73). New browser test files: Keep tests that would fail for a real reason, and test logic below the UI where it can be. See Testing. |
|
Review of 800f88d (from the Discover/#1061 thread; I'll merge once this is ready and these are settled). I checked each finding against the code. Should fix before merge
Lower priority (fine as follow-ups, your call)
Web and service model: no problems found. When I rebase #1061 onto this, I'll merge |
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Other scenariosAll 64 scenario measurements match All 64 scenario measurements
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
|
Re-checked at 968f8ba. All four should-fix items are fixed: every text update is scrubbed (whole messages, compaction summaries, terminal output per terminal); notices are keyed by session; Claude polls its status for 5 min before asking for a paste; the lock key uses the same home folder the Antigravity CLI uses. Your reason for declining the version check holds, since the archive is tied to its catalog entry by SHA-256. Before merge: Test 3 ( |
…server Scient's installer and its setup actions now accept either kind of catalog release. The agy CLI counts as newer than every paired release, so a paired install is offered the CLI as its update, while an installed CLI is never offered a paired release, not even as a repair. The update says the user signs in to Google again: the CLI keeps its own sign-in. Running paired sessions keep their leased copy until they exit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
On Scient's ACP targets the managed runtime is now the agy CLI that Scient's catalog lists under `antigravity`, which runs `agy acp` and loads the user's full Antigravity plugins. Only a CLI from 1.5.12 on qualifies; earlier ones, including the bundled 1.1.x floor, cannot serve ACP. Where no qualified CLI is listed (offline before the first catalog check, musl Linux) the paired release stays the floor. Intel Macs keep the legacy backend. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The agy CLI loads plugins itself from the user's ~/.gemini, whatever GEMINI_HOME says, so a profile launched with it skips the skills-only projection and loses the `config/plugins` link only when Scient made that link to one of its generations. User folders and other links stay, and generations stay for paired sessions still running. The paired projection now also leaves out plugins `agy plugin disable` turned off in the user's config. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
`agy plugin disable` records the switch in the user's ~/.gemini/config/config.json, not the instance profile, so a disabled plugin's skills still surfaced through the picker's global scan. The scan now honors those switches, matched by folder or manifest name, and a stale paired projection cannot bring the plugin back. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Help says Scient installs Google's Antigravity CLI, which runs the user's Antigravity plugins, and that updating from the paired runtime asks for one more Google sign-in. Internals record the selection, why a paired sign-in is not converted (same OAuth client, narrower scopes), where the CLI keeps plugins and their switches, and the remaining projection. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A plugin that needs a sign-in fails its tool call with a card and a loopback sign-in link. The Antigravity adapter now takes that challenge only from the tool's result, validates the page strictly, keeps it in an expiring registry tied to the live agent process, scrubs it from tool output and streamed text, and raises a system notice carrying pluginSignIn. scient.pluginSignIn.open returns the page to the thread that showed the notice, under the provider management grant. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A pluginSignIn notice shows "Sign in to <plugin>" in the timeline's action slot. A click asks the environment for the page and opens it in the user's browser; the running agent receives the callback itself. It then reads "Signed in" once the plugin's next call works or the user says so, asks for a new attempt when the sign-in has ended, and offers nothing on a client that is not on the agent's computer. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… local When the browser runs on the agent's computer, Codex receives the OAuth callback itself and reports mcpServer/oauthLogin/completed, but the sign-in dialog still asked for the landing address. complete now accepts no address and then waits, bounded to five minutes, for the agent's own success report. The dialog starts that wait when it opens the sign-in page and closes with "Signed in"; pasting stays for remote setups. Claude reports no finished sign-in, so without an address it only succeeds when the server already shows as connected. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The agent stores the credential itself, so the Extensions page kept showing the server as needing a sign-in. A chat sign-in that finishes, or finds the server already signed in, now refreshes that provider instance in the background. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Help explains signing in to an Antigravity plugin from its notice and that a local Codex MCP sign-in finishes without pasting. The Extensions internals record the challenge trust rules, the Codex home finding for chat sign-ins under shadow homes, and UPSTREAM.md records the #39921 divergence. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…tion
- ProviderStoreEntry.kind gains "antigravity"; optional publisherType
("google" | "third-party") says which catalog listed the entry, and optional
installationStateKnown=false marks entries whose installed state could not be read.
- Existing Claude and Codex fields are unchanged.
- Store audiences name Antigravity for its entries.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Browse Google's two public catalogs (official and partners) with fixed gstatic addresses: bounded, schema-decoded, cached per catalog with shared in-flight reads, and a failed catalog reported in sourceFailures while the other stays listed. - Add downloads the catalog's archive (gstatic only, no redirects, 64 MB cap), checks its SHA-256 before opening it, unpacks it without links, special files, escaping or colliding names, keeps executable bits, checks plugin.json's name and version, then runs `agy plugin install <staging-dir>` with fixed argv, a neutral cwd and a minimal environment; staging is removed on every outcome. - A small receipt under Scient state records name, catalog, version and digest, so a same-name plugin from another source never shows as installed from the catalog and cannot be removed through the catalog entry. - Installed list, enable/disable and Remove use `agy plugin list --json`, `enable|disable` and `uninstall`; a malformed listing is unknown, never empty. - The Antigravity driver attaches these actions through the same agy it resolves, and explains why when the instance is not the agy CLI. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…curated items - Every plugin in both Antigravity catalogs (97 on 2026-11-21) has a reviewed Discover category list (science plugins under Papers, Biology and Chemistry, Workspace under Files and Communication, partner tools under Code, Projects, Figures or Data); new plugins fall back to the feed's category and keywords. Most used stays Scient's picks. - Curated items name their Antigravity Marketplace entry in agentStores.antigravity (Notion, Linear, Canva, Atlassian, Supabase, Sentry and others), so Discover links them instead of repeating the store row. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Discover gets a "From the Antigravity Marketplace" shelf per Antigravity agent, its own searchable store page, and a "From Antigravity's store" section on category pages; Most used stays Scient's picks. - "Add to Antigravity" installs; a partner plugin shows a third-party developer notice before either Add (list row or detail page) and on its page, which also names its catalog. Details work from the catalog alone. - Removing an Antigravity plugin says it leaves the user's Antigravity on the computer Scient runs on, including the Antigravity app. - Curated items with an Antigravity entry link to it under Also available and hide the duplicate store row. - Strings translated in every locale catalog. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Internals: catalogs, archive checks, receipts and failure behavior. - User guide: where Antigravity plugins appear, the partner notice and what Remove affects. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…d plugins - ProviderStoreEntry gains optional storeUnavailable; the Antigravity store sets it when the instance is not the agy CLI, so clients can leave out Add rows instead of parsing disabledReason. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Account services name exact Antigravity Marketplace entries in stores.antigravity (Gmail, Google Drive, Google Calendar; ChatGPT apps such as Google Docs/Sheets/Slides, Dropbox, Notion, Linear, Figma, Canva, Atlassian, monday.com, ClickUp, Zapier, Stripe by exact name). - accountServiceRoutes adds an "antigravity" family for each available Antigravity agent whose store can add plugins: add, added, off or checking. Added never counts as connected (sign-in happens in a chat); audiences, the next ChatGPT/claude.ai step and Installed services are unchanged. - The service page's Your agents shows that row: Add to Antigravity in place (with the partner notice), "Added · signs in the first time a chat uses it", Off in Antigravity with Turn on, or Checking. - The Discover shelf leaves out entries a service page offers; the full store keeps them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Installed Antigravity plugins (Canva and other partners) declare their MCP servers in mcp_config.json, which the bounded local reader did not read, so their detail pages left the servers out. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
agy has no no-replace install and overwrites a same-name plugin folder. Add now downloads, verifies and unpacks into staging first, then re-reads `agy plugin list --json` immediately before `agy plugin install` and stops, replacing nothing, if a same-name plugin appeared meanwhile (for example from the Antigravity app during the download). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…copy A receipt matched on name, folder and (optionally) version, so after the plugin was removed and another copy installed in the Antigravity app, an old receipt could still make Marketplace Remove target the replacement. - Receipts now record agy's native source and an installation identity: the installed folder's device, inode and birth time plus its plugin.json digest. - A listed plugin is the catalog entry only when name, folder, version (a missing native version never matches), source and identity all match; otherwise it is a local plugin with its own id, which Marketplace Remove does not target. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
agy installs plugins per OS user, so Add, Remove or enable/disable through one Antigravity instance changes what every instance with the same home sees, but only the acting instance republished its list. - Each instance registers under its resolved plugin folder (<home>/.gemini/config/plugins); after any change every live instance there publishes its verified list, without a workspace key. - Remove and enable/disable refuse a workspace-scoped request: these plugins belong to the user account, not a workspace. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… own CLI Redaction no longer depends on a recognized attempt. Any URL whose redirect_uri is loopback is scrubbed from tool snapshots and from every streamed channel, including a tool's first content chunk. A stream holds a possible partial URL, secret or card, bounded, until that stream ends: a tool's output ends with the call, a reply when a tool call or the prompt ends. Interleaved updates no longer release half of a page, and a challenge that arrives only as streamed chunks is found when its call ends. A challenge earns a notice only from a plain shell run of a CLI that the installed plugin's auth.json declares (~/.gemini/config/plugins), whose plugin.json name matches the card, and whose page matches that manifest's authorizeUrl and clientId. Anything else stays redacted with no notice. Only the fields Scient checks are decoded from auth.json. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…nnection A browser opened against a Scient server on another machine took that server for its own computer: the Antigravity action opened a page whose loopback callback its agent never hears, and the Codex dialog waited for the agent's own callback. Only the desktop app talking to its managed backend, or to the background service sharing its home, now counts as the same computer. Elsewhere Antigravity says to sign in on the agent's computer and Codex keeps only the paste path. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Extensions internals describe redaction before projection, the installed-manifest checks a plugin challenge must pass, and the desktop-only same-computer rule. Help says plugin and no-paste MCP sign-ins work from the desktop app on the agent's computer. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A plugin agy installed from its own marketplace showed as "from another source" because only Scient's install receipt counted. Origin now comes from agy's own record first, then Scient's receipt, then, for copies installed before agy recorded origins, the installed plugin.json matching the catalog's repository, author or description. Add uses agy's own marketplace install when agy is signed in, so agy records the origin and keeps the plugin updated; the checked archive stays the fallback. A service row for a plugin Scient can't add explains why and links to Installed instead of showing a disabled Add. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…n-in The Gmail, Calendar and Drive pages said agents reach them through a ChatGPT or Claude account; Antigravity reaches them through its own plugin and Google sign-in. Also translates "Open Installed". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- A tool update no longer flushes the reply or thought stream, so a status between two reply chunks can't release half a sign-in link. - Add reads agy's raw list after the named install whatever it reported, falls back only when the name is absent, and refuses another source's copy. The archive route's last read before installing is agy's raw list, and a receipt is written only for the copy whose plugin.json equals the staged one. - Writes to one plugin folder share one permit across instances. - A copy recognised only by its manifest shows as added but keeps its own id, so Marketplace Remove never acts on it; service rows follow the store's installed state. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Pages for ChatGPT apps that also have an Antigravity plugin use the provider-neutral sentence. Records why the plugin's command name is enough evidence for the sign-in action: agy hands the token on that. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… older copies An archive receipt now also needs the installed folder to be born after the install began, besides the staged plugin.json. A service row for a copy recognised only by its manifest finds it by name, so a disabled one offers Turn on for its own id. Documents the archive route's remaining moment without a no-replace install. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Whole agent messages and thoughts, compaction summaries and terminal output (base64, decoded across chunk boundaries) now pass through the same sign-in scrub as message chunks before projection. Plugin sign-in notices are keyed by ACP session and tool call, since tool call ids are unique only within one session. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude reports a sign-in finished on its own page only as the server's status, so without a pasted address its complete step now watches that status for up to five minutes instead of failing at once. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- The plugin-folder lock uses the same user home the runtime resolves (USERPROFILE, then HOMEDRIVE+HOMEPATH on Windows), compared case-insensitively on Windows. - Receipts are replaced per installed folder, so another plugin home's receipt for the same name survives. - Archives refuse Windows device names as path segments. - A catalog entry that names its MCP servers by a single path still shows that it includes MCP servers. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…oice changes antigravityRuntimeRelease.ts now decides which managed release the installer picks, so a change to it on main must void a qualification run. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
5d59668 to
4f47844
Compare
Scient runs `agy acp --gemini-dir <profile>`, and with that flag agy reads plugins, their sign-ins and their switches from the profile, not from ~/.gemini. The CLI branch only removed Scient's projection link, so chats saw plugin skills through other folders but agy never offered a plugin's sign-in (found in the live test: the Gmail CLI ran with no credentials). The profile's config/plugins now links to ~/.gemini/config/plugins, the folder Antigravity and the Extensions store install into, replacing only Scient's own link, and the user's plugin switches are copied into the profile's config.json beside Scient's keys. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ns in The live test showed agy loads a plugin MCP server that needs a sign-in (Canva's) only after its interactive /plugin manager signs it in, which neither `agy acp` nor `agy -p` does. An installed Antigravity plugin that lists MCP servers now says so on its page and its service row, instead of implying the connection works in Scient chats; its skills still do. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Re-checked 62d4b0f and 49306ed.
Merging once CI is green. |
Adds an Antigravity Marketplace to Extensions, with Add, Remove and sign-in. Antigravity gets the same store experience as Claude, Codex and Scient Agent: Google's official and partner plugin catalogs, plus their sign-in inside the chat. It also adapts upstream's chat MCP sign-in (#39921) for the desktop.
Design, live checks and the three Codex reviews are in
reviews/antigravity-plugins-20261121/in the ScientFactory workspace.What changes for users
agy acp), the runtime T3 upstream already uses.agy plugin install <name>@<catalog>. agy records the origin, keeps the plugin updated, and refuses a folder that another source holds (checked live).agy plugin install <dir>;sourcenames the catalog, or when a receipt matches that exact copy.plugin.jsonmatches the catalog. They keep their own id, so only Installed removes them.<plugin-card>and a sign-in link served by the agy process itself on this computer.pluginSignInnotice offers Sign in to Gmail, but only for a plain run of a CLI that the installed plugin'sauth.jsondeclares, with its client and authorize URL pinned.Platforms
agy acpsessions loading plugins, the sign-in card, and the store in a dev app.agy.exe, junction removal, folder identity may report inode 0.Known limits, recorded in
docs/internals/scient-extensions.md/plugin. Scient says so, and their skills work.Tests
Live test (dev app, macOS, agy 1.5.12, Gemini 4 Hydrogen)
agy acp --gemini-dir <profile>reads plugins and their sign-ins from the profile, so the profile'sconfig/pluginsnow links to~/.gemini/config/plugins, and the user's plugin switches are copied into it.agy acporagy -p. agy signs them in only in its interactive/plugin. Installed plugins with MCP servers now say so, and their skills still work.🤖 Generated with Claude Code