Skip to content

Antigravity Marketplace in Extensions, with chat sign-in - #1064

Merged
yaacovcorcos merged 36 commits into
mainfrom
claude/antigravity-plugins-20261121
Nov 22, 2026
Merged

yaacovcorcos merged 36 commits into
mainfrom
claude/antigravity-plugins-20261121

Conversation

@yaacovcorcos

@yaacovcorcos yaacovcorcos commented Nov 21, 2026 •

Copy link
Copy Markdown
Contributor

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

  • Runtime. Managed Antigravity installs move from the paired ACP runtime to the agy CLI (agy acp), the runtime T3 upstream already uses.
    • Live check: the paired runtime (1.5.2) cannot load full plugins. It got skills only, through Scient's projection.
    • Existing installs are offered the CLI through the usual Update Antigravity flow. The paired runtime stays as the offline fallback.
    • Users signed in with Google sign in once after the switch. Converting the old sign-in is not safe, because the CLI asks for more permissions.
  • Store.
    • Two public gstatic catalogs: 27 official and 70 partner plugins.
    • Discover category sections: "From Antigravity's store".
    • Curated links to Antigravity entries.
    • An Antigravity row on account-service pages such as Gmail and Drive, with states add / added / off / checking.
    • Partner plugins show a third-party notice before Add.
  • Add.
    • First uses agy's own agy plugin install <name>@<catalog>. agy records the origin, keeps the plugin updated, and refuses a folder that another source holds (checked live).
    • When agy is not signed in, it falls back to the catalog's archive:
      • the SHA-256 is checked before opening;
      • the archive is unpacked safely and the name and version checked;
      • agy's own list is re-read as the last step before agy plugin install <dir>;
      • a receipt is written only when the installed copy is exactly the one Scient staged.
  • Origin.
    • An installed copy counts as the catalog entry when agy's source names the catalog, or when a receipt matches that exact copy.
    • Older copies with no recorded origin show as added when their plugin.json matches the catalog. They keep their own id, so only Installed removes them.
  • Chat sign-in. When a plugin needs a sign-in, agy's tool output holds a <plugin-card> and a sign-in link served by the agy process itself on this computer.
    • Every such link is scrubbed from the transcript, including links split across streams.
    • A typed pluginSignIn notice offers Sign in to Gmail, but only for a plain run of a CLI that the installed plugin's auth.json declares, with its client and authorize URL pinned.
    • The URL is handed out only on a click from the agent's own computer.
  • Upstream #39921 on the desktop.
    • Codex MCP sign-ins from chat finish without pasting the address when the browser is on the same computer.
    • The provider's plugin list refreshes after a chat sign-in.

Platforms

  • macOS: all live checks: catalogs, archive install, named install refusing a same-name folder, agy acp sessions loading plugins, the sign-in card, and the store in a dev app.
  • Windows and Linux: covered by unit tests and mocks only.
    • Windows: agy.exe, junction removal, folder identity may report inode 0.
    • Linux: birth time may be missing, in which case only the manifest digest ties a receipt to its copy.

Known limits, recorded in docs/internals/scient-extensions.md

  • Archive fallback overwrite window: agy has no no-replace directory install. The fallback can still replace a same-name plugin that another program installs in the moment between its last list read and the install. The named route has no such window.
  • Sign-in button and command name: the button trusts the plugin's command name, the same evidence agy uses to hand the plugin its token.
  • Partner MCP plugins (e.g. Canva): their connection signs in only in agy's own /plugin. Scient says so, and their skills work.

Tests

  • Server: 944 tests across the 17 changed and adjacent files pass.
  • Web: the whole unit project passes (12,199), and so do the extensions, Antigravity and MCP sign-in browser tests (107).
  • Contracts: 557 pass.
  • Checks: root typecheck, lint, i18n check, seam check and upstream provenance pass.

Live test (dev app, macOS, agy 1.5.12, Gemini 4 Hydrogen)

  • Gmail, end to end: pass.
    • The chat showed "Gmail needs a sign-in… Sign in to Gmail", and the button opened Google's consent page in the default browser.
    • After consent, a "Signed in" notice appeared and the chat listed the 3 latest email subjects.
    • Only the read scope (gmail.modify) was granted.
    • No sign-in link or card text reached the transcript.
  • Found and fixed during the test:
    1. agy acp --gemini-dir <profile> reads plugins and their sign-ins from the profile, so the profile's config/plugins now links to ~/.gemini/config/plugins, and the user's plugin switches are copied into it.
    2. Plugin MCP servers that need a sign-in (Canva) don't load in agy acp or agy -p. agy signs them in only in its interactive /plugin. Installed plugins with MCP servers now say so, and their skills still work.
  • Existing chat after restarting the app: resumes. A paired-runtime chat resuming on the CLI was not tested; the dev app never ran the paired runtime.

🤖 Generated with Claude Code

@github-actions github-actions Bot added vouch:trusted Author is trusted by repo permissions or the VOUCHED list. size:XXL labels Nov 21, 2026
@github-actions

github-actions Bot commented Nov 21, 2026 •

Copy link
Copy Markdown
Contributor

This PR changes the test suite by +95 test cases (browser +16, unit +6, server +73).

New browser test files: apps/web/src/components/chat/McpSignInAction.scient.browser.test.tsx, apps/web/src/scient/antigravity/PluginSignInAction.browser.test.tsx.
Each browser test file costs CI seconds of module loading before its first test runs; a unit test costs milliseconds.

Keep tests that would fail for a real reason, and test logic below the UI where it can be. See Testing.

@yaacovcorcos

Copy link
Copy Markdown
Contributor Author

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

  1. Text-bearing ACP updates skip the redactor. pluginSignIn.ts observe (around line 549) scrubs only agent_message_chunk/agent_thought_chunk text and tool_call_content_chunk. Everything else passes unchanged, yet the ACP adapter projects and persists agent_message, agent_thought, terminal_output_chunk and compaction_summary_chunk (provider-acp/src/server/adapter.ts lines 208–215 and 2044–2058). A sign-in URL arriving on any of those reaches the event store, which breaks the PR's own rule that every sign-in URL is scrubbed before projection. Fix: route every displayable text update through streamChunk, or a one-shot scrub for complete messages, with per-terminal channels for terminal output.
  2. pendingNotices is keyed by toolCallId only (pluginSignIn.ts, around line 396). tools and redactors are session-scoped, but tool-call ids are only unique within an ACP session, so two Antigravity sessions can overwrite or take each other's notice. Fix: key by ${sessionId}:${toolCallId}, as trackTool does.
  3. Claude never finishes on its own. McpSignInAction.awaitBrowser calls complete right after openExternal. Claude's complete (ClaudeAdapterV2.ts, around line 15918) checks the status once, then fails with "Paste the address…" because callbackUrl is undefined. The client ignores that failure and won't wait again for this attempt. The automatic finish on the same computer therefore never happens for Claude (pasting still works). Fix: poll Claude's status for a bounded time, or skip awaitBrowser for Claude.
  4. On Windows, instances sharing a plugin folder can use different lock keys (AntigravityProviderStore.ts, around line 833). The lock key comes from HOME ?? USERPROFILE, while resolveAntigravityUserHome prefers USERPROFILE and falls back to HOMEDRIVE+HOMEPATH. Two instances can then write the same folder under different keys. Fix: pass the driver's resolved user home and canonicalise it.

Lower priority (fine as follow-ups, your call)

  • Receipts live in one server-wide file, and installing the same plugin name in another plugin home deletes the first home's receipt (around lines 629–635). Key receipts by plugin home, or include the home in their identity.
  • The archive validator accepts Windows device names (CON, NUL, COM1, LPT1, with or without an extension) as path segments (AntigravityPluginArchive.ts lines 113–120).
  • When the catalog gives a version and plugin.json has none, the version check is skipped (AntigravityPluginArchive.ts lines 230–236).
  • componentNames ignores a single string path ("mcpServers": "./mcp_config.json", as in arize-skills), so those entries list no MCP servers before install (AntigravityPluginCatalog.ts lines 151–160).
  • Not an issue: the reviewer flagged the musl check. Alpine ships /lib/libc.musl-*.so.1 as a link to ld-musl-*, the same check T3 uses, so I'm not counting it.

Web and service model: no problems found. When I rebase #1061 onto this, I'll merge AntigravityServiceRow into #1061's generic store route (storeRoute / useStoreInstall) and keep your third-party notice, storeUnavailable, installationStateKnown and the lookup of older copies by name. Nothing to change here for that.

@github-actions

github-actions Bot commented Nov 21, 2026 •

Copy link
Copy Markdown
Contributor

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider Metric Main baseline This PR Impact PR ceiling
Codex Total thread wire 5.5 KiB 5.5 KiB 0 B (0.0%) 6.8 KiB ✅
Codex Thread snapshot wire 4.2 KiB 4.2 KiB 0 B (0.0%) 4.9 KiB ✅
Codex Live turn WebSocket wire 1.3 KiB 1.3 KiB 0 B (0.0%) 2.0 KiB ✅
Codex Live turn WebSocket decoded 22.3 KiB 22.3 KiB 0 B (0.0%) 24.4 KiB ✅
Codex Live turn messages 1 1 0 (0.0%) 8 ✅
Claude Total thread wire 5.5 KiB 5.5 KiB 0 B (0.0%) 6.8 KiB ✅
Claude Thread snapshot wire 4.2 KiB 4.2 KiB 0 B (0.0%) 4.9 KiB ✅
Claude Live turn WebSocket wire 1.3 KiB 1.3 KiB 0 B (0.0%) 2.0 KiB ✅
Claude Live turn WebSocket decoded 22.7 KiB 22.7 KiB 0 B (0.0%) 24.4 KiB ✅
Claude Live turn messages 1 1 0 (0.0%) 8 ✅

Other scenarios

All 64 scenario measurements match main.

All 64 scenario measurements
Provider Scenario Metric Main baseline This PR Impact PR ceiling
Codex short turn resume WebSocket decoded 12.0 KiB 12.0 KiB 0 B (0.0%) 12.7 KiB ✅
Codex short turn resume WebSocket messages 2 2 0 (0.0%) 2 ✅
Codex long turn running, cold open HTTP decoded 281.7 KiB 281.7 KiB 0 B (0.0%) 302.7 KiB ✅
Codex long turn running, cold open rows 75 75 0 (0.0%) 75 ✅
Codex long turn running, history page HTTP decoded 92.4 KiB 92.4 KiB 0 B (0.0%) 107.4 KiB ✅
Codex long turn running, history page rows 75 75 0 (0.0%) 75 ✅
Codex long turn finished, cold open HTTP decoded 381.5 KiB 381.5 KiB 0 B (0.0%) 410.2 KiB ✅
Codex long turn finished, cold open rows 151 151 0 (0.0%) 151 ✅
Codex long turn finished, socket cold open WebSocket decoded 381.6 KiB 381.6 KiB 0 B (0.0%) 410.2 KiB ✅
Codex long turn finished, socket cold open WebSocket messages 2 2 0 (0.0%) 2 ✅
Codex long turn finished, socket cold open rows 151 151 0 (0.0%) 151 ✅
Codex long turn finished, work page HTTP decoded 186.2 KiB 186.2 KiB 0 B (0.0%) 200.2 KiB ✅
Codex long turn finished, work page rows 150 150 0 (0.0%) 150 ✅
Codex idle thread resume WebSocket decoded 65 B 65 B 0 B (0.0%) 200 B ✅
Codex idle thread resume WebSocket messages 1 1 0 (0.0%) 1 ✅
Codex fleet shell snapshot HTTP decoded 45.5 KiB 45.5 KiB 0 B (0.0%) 53.7 KiB ✅
Codex fleet shell snapshot rows 27 27 0 (0.0%) 27 ✅
Codex fleet shell subscribe WebSocket decoded 65 B 65 B 0 B (0.0%) 200 B ✅
Codex fleet shell subscribe WebSocket messages 1 1 0 (0.0%) 1 ✅
Codex fleet shell resume check HTTP decoded 18 B 18 B 0 B (0.0%) 100 B ✅
Codex fleet shell resume check rows 0 0 0 0 ✅
Codex stale shell reload HTTP decoded 45.5 KiB 45.5 KiB 0 B (0.0%) 53.7 KiB ✅
Codex stale shell reload rows 27 27 0 (0.0%) 27 ✅
Codex stale shell resume WebSocket decoded 140 B 140 B 0 B (0.0%) 400 B ✅
Codex stale shell resume WebSocket messages 2 2 0 (0.0%) 2 ✅
Codex stale todo list cold open HTTP decoded 72.4 KiB 72.4 KiB 0 B (0.0%) 83.0 KiB ✅
Codex stale todo list cold open rows 75 75 0 (0.0%) 75 ✅
Codex stale todo list cold open nodes 2 2 0 (0.0%) 4 ✅
Codex stale todo list cold open subagents 2 2 0 (0.0%) 4 ✅
Codex stale todo list cold open plans 1 1 0 (0.0%) 2 ✅
Codex stale todo list cold open providerTurns 1 1 0 (0.0%) 2 ✅
Codex stale todo list cold open checkpoints 1 1 0 (0.0%) 2 ✅
Claude short turn resume WebSocket decoded 12.2 KiB 12.2 KiB 0 B (0.0%) 12.7 KiB ✅
Claude short turn resume WebSocket messages 2 2 0 (0.0%) 2 ✅
Claude long turn running, cold open HTTP decoded 283.3 KiB 283.3 KiB 0 B (0.0%) 302.7 KiB ✅
Claude long turn running, cold open rows 75 75 0 (0.0%) 75 ✅
Claude long turn running, history page HTTP decoded 93.4 KiB 93.4 KiB 0 B (0.0%) 107.4 KiB ✅
Claude long turn running, history page rows 75 75 0 (0.0%) 75 ✅
Claude long turn finished, cold open HTTP decoded 384.1 KiB 384.1 KiB 0 B (0.0%) 410.2 KiB ✅
Claude long turn finished, cold open rows 151 151 0 (0.0%) 151 ✅
Claude long turn finished, socket cold open WebSocket decoded 384.3 KiB 384.3 KiB 0 B (0.0%) 410.2 KiB ✅
Claude long turn finished, socket cold open WebSocket messages 2 2 0 (0.0%) 2 ✅
Claude long turn finished, socket cold open rows 151 151 0 (0.0%) 151 ✅
Claude long turn finished, work page HTTP decoded 188.1 KiB 188.1 KiB 0 B (0.0%) 200.2 KiB ✅
Claude long turn finished, work page rows 150 150 0 (0.0%) 150 ✅
Claude idle thread resume WebSocket decoded 66 B 66 B 0 B (0.0%) 200 B ✅
Claude idle thread resume WebSocket messages 1 1 0 (0.0%) 1 ✅
Claude fleet shell snapshot HTTP decoded 46.1 KiB 46.1 KiB 0 B (0.0%) 53.7 KiB ✅
Claude fleet shell snapshot rows 27 27 0 (0.0%) 27 ✅
Claude fleet shell subscribe WebSocket decoded 66 B 66 B 0 B (0.0%) 200 B ✅
Claude fleet shell subscribe WebSocket messages 1 1 0 (0.0%) 1 ✅
Claude fleet shell resume check HTTP decoded 18 B 18 B 0 B (0.0%) 100 B ✅
Claude fleet shell resume check rows 0 0 0 0 ✅
Claude stale shell reload HTTP decoded 46.1 KiB 46.1 KiB 0 B (0.0%) 53.7 KiB ✅
Claude stale shell reload rows 27 27 0 (0.0%) 27 ✅
Claude stale shell resume WebSocket decoded 140 B 140 B 0 B (0.0%) 400 B ✅
Claude stale shell resume WebSocket messages 2 2 0 (0.0%) 2 ✅
Claude stale todo list cold open HTTP decoded 73.4 KiB 73.4 KiB 0 B (0.0%) 83.0 KiB ✅
Claude stale todo list cold open rows 75 75 0 (0.0%) 75 ✅
Claude stale todo list cold open nodes 2 2 0 (0.0%) 4 ✅
Claude stale todo list cold open subagents 2 2 0 (0.0%) 4 ✅
Claude stale todo list cold open plans 1 1 0 (0.0%) 2 ✅
Claude stale todo list cold open providerTurns 1 1 0 (0.0%) 2 ✅
Claude stale todo list cold open checkpoints 1 1 0 (0.0%) 2 ✅

Baseline: 71f81cf · PR result: 49306ed · Source CI: success

Scenario and decoded snapshot size

10 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.
Bounded compact HTTP snapshot with live cursor.

  • Codex decoded thread snapshot: 88.2 KiB
  • Claude decoded thread snapshot: 88.4 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

@yaacovcorcos

Copy link
Copy Markdown
Contributor Author

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 (managed-provider-runtime-workflow.test.ts › 'voids antigravityAcp publication…') still fails on this head, and Test Web 12 looks flaky. I'll merge once CI is green, the live sign-in run has passed, and the PR is marked ready.

yaacovcorcos and others added 24 commits November 22, 2026 01:28
…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>
yaacovcorcos and others added 10 commits November 22, 2026 01:28
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>
@yaacovcorcos
yaacovcorcos force-pushed the claude/antigravity-plugins-20261121 branch from 5d59668 to 4f47844 Compare November 21, 2026 23:30
yaacovcorcos and others added 2 commits November 22, 2026 01:49
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>
@yaacovcorcos
yaacovcorcos marked this pull request as ready for review November 22, 2026 00:05
@yaacovcorcos

Copy link
Copy Markdown
Contributor Author

Re-checked 62d4b0f and 49306ed.

  • 62d4b0f, profile link: correct. Production profiles today have Scient's projection link (checked on this machine), and linkAntigravityUserPlugins replaces it with the link to ~/.gemini/config/plugins. A real folder or someone else's link is left alone. Windows uses a junction, and config.json is written atomically with mode 0600. Nit: a profile where agy already created an empty config/plugins folder (only possible on dev builds of this branch) never gets linked. Fine to leave. Note that the switches only sync one way, from ~/.gemini into the profile, so a toggle made inside an Antigravity chat's own /plugin is overwritten on the next prepare.
  • 49306ed, MCP sign-in note: right call. Since agy can't sign a plugin's MCP server in from acp, the Antigravity routes for partner services built on MCP (Notion, Linear, Figma, Canva…) should not be offered as working routes on service pages. I'll do that in Discover: one entry per service, official first, every agent connected from one page #1061's fold-in, which owns the service model: Google's own auth.json plugins (Gmail, Calendar, Drive, Docs, Sheets, Slides) stay as routes, and MCP partner plugins stay in the store with your note, shown before Add too.
  • Not live-tested: resuming a chat started on the paired runtime after the switch. That's accepted as a known risk; worth keeping in the PR body.

Merging once CI is green.

@yaacovcorcos
yaacovcorcos added this pull request to the merge queue Nov 22, 2026
Merged via the queue into main with commit 73947a2 Nov 22, 2026
78 of 80 checks passed
@yaacovcorcos
yaacovcorcos deleted the claude/antigravity-plugins-20261121 branch November 22, 2026 00:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:XXL vouch:trusted Author is trusted by repo permissions or the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant