Skip to content

[Bug]: Antigravity does not expose the installed plugins #28116

Open

Description

@ChristianGonper

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.

Area

Not sure

Steps to reproduce

  1. Install a plugin in Antigravity App or agy CLI
  2. Autenthicate and try it so it works
  3. Open T3 Code and ask a Gemini model working in Antigravity to use a plugin (/gdocs for example)
  4. See that it says it does not exist
  5. Ask it why, and it says that t3-code MCP does not expose these tools that are implemented as CLI skills managed by agy in .gemini/config/plugins

Expected behavior

It should use the native plugins installed to the the task with the proper tools

Actual behavior

The AI wants to create a custom API integration with Google Cloud for the task

Impact

Blocks work completely

Version or commit

Version 0.1.6

Environment

Antigravity, Windows 11

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround

Use agy CLI in the terminal

Activity

  1. added
    bugSomething is broken or behaving incorrectly.
    needs-triageIssue needs maintainer review and initial categorization.
    on Oct 31, 2026
  2. fcakyon commented on Nov 3, 2026

    @fcakyon
    Contributor

    This is a big limitation and feature parity issue considering plugin dirs supported for claude code and codex. I'm working on a PR to fix this issue.

  3. chrisjian commented on Nov 10, 2026

    @chrisjian

    I have the same problem, after I import a plugin to agy from claude code, I can use the plugin in agy cli, but it doesn't show in t3 code

  4. ChristianGonper commented on Nov 11, 2026

    @ChristianGonper
    Author

    @fcakyon It also occurs with MCP configured in the .gemini folder

  5. raihan0x1 commented on Nov 15, 2026

    @raihan0x1

    Same here. Plugins I installed in Antigravity work fine in the Antigravity app and in the agy CLI, but none of them show up in T3 Code on the Antigravity provider: they're missing from the / and $ pickers, and the agent says they don't exist. Plugins installed for Claude Code show up in T3 Code right away, so for now Antigravity can't do what Claude can here.

    • T3 Code: 0.1.9 (Beta)
    • OS: macOS 27.2.1
    • Antigravity app: 2.32.1, agy CLI: 1.5.8
    • Plugins in ~/.gemini/config/plugins: antislop, chrome-devtools-plugin, context-mode, modern-web-guidance, ponytail. Several of these are also installed for Claude Code, and they show up there.

    Looking forward to #30476 landing. Happy to test it.

  6. raihan0x1 commented on Nov 15, 2026

    @raihan0x1

    Follow-up with a concrete check (T3 Code 0.1.9, agy 1.5.8, Gemini 3.8 Flash on the Antigravity provider). I asked the agent in a T3 thread to list only what was in its own context, without reading files:

    • impeccable, a standalone skill in ~/.gemini/skills/, is available.
    • None of the skills that come from plugins in ~/.gemini/config/plugins/ are available, e.g. antislop (+5 sub-skills), chrome-devtools (+5), ctx-doctor/ctx-stats, modern-web-guidance, chrome-extensions, ponytail.
    • The MCP server declared in context-mode/mcp_config.json isn't loaded either. The only MCP tools present are T3 Code's own t3-code server.

    So the standalone skills directory gets loaded, but nothing under config/plugins/ does: neither the plugins' skills nor their MCP servers. That matches what #30476 addresses for skills. The plugins' MCP servers may need separate handling.

  7. p4cs-974 commented on Nov 19, 2026

    @p4cs-974

    I filed #38925 for a narrower case of this. With the plugin in T3's own Antigravity profile (<profile>/config/plugins/<name>/), Antigravity does load it in T3 threads: the hook runs, its skills can be read, and the ACP server advertises them as slash commands. T3's skills list still leaves them out, because discoverAntigravitySkills only scans config/skills, antigravity-cli/skills and the project skill folders, never config/plugins/*/skills. Making it scan ~/.gemini/config/plugins/*/skills as well would also cover the skill-discovery part of this issue.

  8. aka-cronos commented on Nov 20, 2026

    @aka-cronos

    Confirming this still reproduces on the latest nightly with a partner connector plugin that bundles a remote MCP server (figma).

    Environment

    • T3 Code: 0.1.11-nightly.20261120.4969 (Desktop on macOS, commit db51b671)
    • OS: macOS (darwin arm64, 27.2.0)
    • Antigravity runtime: T3-managed Antigravity CLI 1.5.12 (oauth-personal)
    • Installed plugin: figma (2.2.208-agy.82ddeba0, from antigravity-plugins-partners) in ~/.gemini/config/plugins/figma — 17 skills + 1 remote Streamable HTTP MCP server (https://mcp.figma.com/mcp)

    Evidence

    • In the Antigravity desktop app, the figma plugin is active and exposes its 46 MCP tools (cached under ~/.gemini/antigravity/mcp/figma_figma).
    • In T3 Code Antigravity threads, the isolated profile (~/.t3/userdata/providers/antigravity/<instance-hash>/config/) only symlinks skills -> ~/.gemini/config/skills via linkAntigravityUserSkills in apps/server/src/provider/antigravityAuthSupport.ts.
    • Neither config/plugins nor the plugin's MCP server is exposed to antigravity acp --gemini-dir <profile> --app-data-dir antigravity-acp, so only the t3-code MCP server is available inside the thread.

    Workaround

    Manually symlinking ~/.gemini/config/plugins into ~/.t3/userdata/providers/antigravity/<instance-hash>/config/plugins and restarting T3 Code. Looking forward to #39084 / #39082 landing.


    Drafted via T3 Code triage using Gemini 4 Neon (Antigravity).

  9. Realauster commented on Nov 20, 2026

    @Realauster

    Still reproduces on Linux with 0.1.11-nightly.20261120.4979 (AppImage) and the T3-managed antigravity CLI 1.5.13. Two details that may help #39082 / #39084:

    1. Linking only skills does not survive a restart. linkAntigravityUserConfig treats <profile>/config/skills as its own link. When ~/.gemini/config/skills does not exist, it removes any symlink at <profile>/config/skills on the next launch. So pointing that link at a plugin's skills/ folder works until T3 restarts. Linking <profile>/config/plugins -> ~/.gemini/config/plugins (the workaround above) is the one that sticks, because nothing manages that path.
    2. The agent already advertises the skills, and only the composer misses them. With the plugins link in place, antigravity acp --gemini-dir <profile> --app-data-dir antigravity-acp sends every plugin skill in available_commands_update on session/new. The / menu in a new thread still shows the old list. That list comes from the workspace snapshot of the last session in that cwd plus discoverAntigravitySkills, which does not scan ~/.gemini/config/plugins/*/skills. The menu catches up only after T3 restarts or an Antigravity session runs in that folder.

    My setup has 13 skills in ~/.gemini/config/plugins/migrated-settings/skills/ (made by the built-in migrate-agent-settings skill). None of them showed in T3's / menu until I linked config/plugins into the instance profile.

  10. smnbss commented on Nov 20, 2026

    @smnbss

    Confirming this also reproduces on macOS (darwin arm64) with official Antigravity Google plugins (gcalendar 0.0.8, gmail 0.0.7, gdrive 0.0.11 from antigravity-plugins-official):

    Environment

    • T3 Code: 0.1.11-nightly.20261118.4877 (macOS arm64)
    • Antigravity runtime: 1.5.12 (oauth-personal)

    Additional detail for #39082 / #39084: plugin_data (CLI binaries & OAuth token.json)

    Linking ~/.gemini/config/plugins into <profile>/config/plugins solves plugin/skill discovery, but official CLI-backed plugins (gcalendar, gmail, gdrive) have a second dependency on ANTIGRAVITY_APP_DATA_DIR:

    • Their wrapper script (skills/<tool>/scripts/<tool>) resolves:
      BIN_DIR="$ANTIGRAVITY_APP_DATA_DIR/plugin_data/$PLUGIN_DIR_NAME/bin"
      SHIM="$ANTIGRAVITY_APP_DATA_DIR/bin/$TOOL"
    • When authenticated in the standalone Antigravity app, OAuth credentials (token.json) and downloaded binaries live in ~/.gemini/antigravity/plugin_data/<plugin>/ (e.g. ~/.gemini/antigravity/plugin_data/gcalendar/token.json).
    • Because T3 Code sets ANTIGRAVITY_APP_DATA_DIR=<profile>/antigravity-acp (which has no plugin_data/), even once config/plugins is linked by fix(server): link enabled global Antigravity plugins into instance profiles #39082 / fix(server): Antigravity threads load plugins installed in ~/.gemini #39084, official plugins already signed into in Antigravity still won't find their token.json (and T3 Code doesn't surface Antigravity's plugin Sign-in card).

    Sharing or linking plugin_data (or supporting plugin auth in T3's profile) alongside config/plugins would make official gcalendar / gmail / gdrive plugins work out of the box too.

  11. viktorce commented on Nov 20, 2026

    @viktorce
    Contributor

    I tested a plugin whose MCP server is hosted and needs its own sign-in. The evidence on #39082 and #39084 uses synthetic plugins, so this case was open. Three results may help both PRs.

    Setup

    • macOS 27.2.1 arm64, agy 1.5.13.
    • Linear plugin 1.0.0-agy.4dbbe23f. Its mcp_config.json declares one server, https://mcp.linear.app/mcp. I had signed in to Linear from the Antigravity app earlier.
    • A throwaway profile laid out like a T3 instance profile, with <profile>/config/plugins linked to a folder that holds the Linear plugin.
    • agy acp --gemini-dir <profile> --app-data-dir antigravity-acp with GEMINI_HOME=<profile>, driven by a small ACP client. None of this went through T3.
    • The Google sign-in came from the OS keyring, which is how 0.1.10 launches the agent.

    1. The Linear sign-in carries over

    The Linear server connected with no sign-in prompt. agy wrote 70 tool schemas to <profile>/antigravity-acp/mcp/linear_linear/, and a whoami tool call returned my user.

    The OAuth token is not in the profile. It sits in the macOS keychain under service antigravity.plugins, account <user id>/mcp-oauth:linear:https://mcp.linear.app/mcp. So a hosted MCP plugin needed only the plugins link here. That differs from the CLI-backed plugins in smnbss's comment above, which read plugin_data/<plugin>/token.json.

    Not tested: 0.1.11 and main launch Google-account instances with SSH_CONNECTION set, so the Google sign-in is stored in the profile. The keychain account name starts with a per-user id, and I can't say whether a profile signed in that way finds the same entry. T3 does not show Antigravity's plugin sign-in card, so a hosted plugin deserves one check in that mode before either PR merges.

    2. session/new returns before the plugin's MCP server has loaded

    In 15 new sessions, agy wrote the Linear tool schemas 178 to 504 ms after session/new returned.

    A prompt sent in that gap does not get the tools. I ran 10 sessions with one prompt each and read the system prompt that agy stored in <profile>/antigravity-acp/conversations/<id>.db:

    First prompt sent Sessions System prompt has <mcp_servers> with linear_linear
    Right after session/new returned 5 0 of 5
    3 seconds later 5 5 of 5

    A later prompt in the same session gets the tools once the server has loaded.

    If T3 sends a new thread's first message as soon as session/new returns, that message runs without the plugin's hosted MCP tools, and the next message has them. I have not run this through T3, where the timing may differ.

    3. #39084 leaves the text-generation helpers unguarded

    At b8e8932, isAntigravityTextGenerationAvailable still checks only <profile>/config/hooks.json and <profile>/config/mcp_config.json. Once config/plugins is linked, agy connects each plugin's MCP servers in every session on that profile. In the sessions above it had connected to Linear and listed its tools before I sent any prompt. Helper sessions use the same profile, so generating a thread title would start those servers too. docs/internals/providers.md says helpers reject such profiles before launch.

    #39082 already covers this. Its guard also reads hooks.json and mcp_config.json at the root of each enabled plugin. #39084 needs the same check if it is the one that merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething is broken or behaving incorrectly.needs-triageIssue needs maintainer review and initial categorization.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions