You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Antigravity does not expose the installed plugins #28116
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.
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.
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.
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).
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:
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.
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.
Confirming this also reproduces on macOS (darwin arm64) with official Antigravity Google plugins (gcalendar0.0.8, gmail0.0.7, gdrive0.0.11 from antigravity-plugins-official):
Environment
T3 Code:0.1.11-nightly.20261118.4877 (macOS arm64)
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:
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).
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.
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.
Activity
fcakyon commentedon Nov 3, 2026
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.
chrisjian commentedon Nov 10, 2026
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
ChristianGonper commentedon Nov 11, 2026
@fcakyon It also occurs with MCP configured in the .gemini folder
raihan0x1 commentedon Nov 15, 2026
Same here. Plugins I installed in Antigravity work fine in the Antigravity app and in the
agyCLI, 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.agyCLI: 1.5.8~/.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.
raihan0x1 commentedon Nov 15, 2026
Follow-up with a concrete check (T3 Code 0.1.9,
agy1.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.~/.gemini/config/plugins/are available, e.g.antislop(+5 sub-skills),chrome-devtools(+5),ctx-doctor/ctx-stats,modern-web-guidance,chrome-extensions,ponytail.context-mode/mcp_config.jsonisn't loaded either. The only MCP tools present are T3 Code's ownt3-codeserver.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.p4cs-974 commentedon Nov 19, 2026
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, becausediscoverAntigravitySkillsonly scansconfig/skills,antigravity-cli/skillsand the project skill folders, neverconfig/plugins/*/skills. Making it scan~/.gemini/config/plugins/*/skillsas well would also cover the skill-discovery part of this issue.aka-cronos commentedon Nov 20, 2026
Confirming this still reproduces on the latest nightly with a partner connector plugin that bundles a remote MCP server (
figma).Environment
0.1.11-nightly.20261120.4969(Desktop on macOS, commitdb51b671)darwinarm64, 27.2.0)1.5.12(oauth-personal)figma(2.2.208-agy.82ddeba0, fromantigravity-plugins-partners) in~/.gemini/config/plugins/figma— 17 skills + 1 remote Streamable HTTP MCP server (https://mcp.figma.com/mcp)Evidence
figmaplugin is active and exposes its 46 MCP tools (cached under~/.gemini/antigravity/mcp/figma_figma).~/.t3/userdata/providers/antigravity/<instance-hash>/config/) only symlinksskills -> ~/.gemini/config/skillsvialinkAntigravityUserSkillsinapps/server/src/provider/antigravityAuthSupport.ts.config/pluginsnor the plugin's MCP server is exposed toantigravity acp --gemini-dir <profile> --app-data-dir antigravity-acp, so only thet3-codeMCP server is available inside the thread.Workaround
Manually symlinking
~/.gemini/config/pluginsinto~/.t3/userdata/providers/antigravity/<instance-hash>/config/pluginsand restarting T3 Code. Looking forward to #39084 / #39082 landing.Drafted via T3 Code triage using Gemini 4 Neon (Antigravity).
Realauster commentedon Nov 20, 2026
Still reproduces on Linux with
0.1.11-nightly.20261120.4979(AppImage) and the T3-managedantigravityCLI 1.5.13. Two details that may help #39082 / #39084:skillsdoes not survive a restart.linkAntigravityUserConfigtreats<profile>/config/skillsas its own link. When~/.gemini/config/skillsdoes not exist, it removes any symlink at<profile>/config/skillson the next launch. So pointing that link at a plugin'sskills/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.antigravity acp --gemini-dir <profile> --app-data-dir antigravity-acpsends every plugin skill inavailable_commands_updateonsession/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 plusdiscoverAntigravitySkills, 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-inmigrate-agent-settingsskill). None of them showed in T3's/menu until I linkedconfig/pluginsinto the instance profile.smnbss commentedon Nov 20, 2026
Confirming this also reproduces on macOS (
darwinarm64) with official Antigravity Google plugins (gcalendar0.0.8,gmail0.0.7,gdrive0.0.11fromantigravity-plugins-official):Environment
0.1.11-nightly.20261118.4877(macOS arm64)1.5.12(oauth-personal)Additional detail for #39082 / #39084:
plugin_data(CLI binaries & OAuthtoken.json)Linking
~/.gemini/config/pluginsinto<profile>/config/pluginssolves plugin/skill discovery, but official CLI-backed plugins (gcalendar,gmail,gdrive) have a second dependency onANTIGRAVITY_APP_DATA_DIR:skills/<tool>/scripts/<tool>) resolves:token.json) and downloaded binaries live in~/.gemini/antigravity/plugin_data/<plugin>/(e.g.~/.gemini/antigravity/plugin_data/gcalendar/token.json).ANTIGRAVITY_APP_DATA_DIR=<profile>/antigravity-acp(which has noplugin_data/), even onceconfig/pluginsis 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 theirtoken.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) alongsideconfig/pluginswould make officialgcalendar/gmail/gdriveplugins work out of the box too.viktorce commentedon Nov 20, 2026
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
agy1.5.13.1.0.0-agy.4dbbe23f. Itsmcp_config.jsondeclares one server,https://mcp.linear.app/mcp. I had signed in to Linear from the Antigravity app earlier.<profile>/config/pluginslinked to a folder that holds the Linear plugin.agy acp --gemini-dir <profile> --app-data-dir antigravity-acpwithGEMINI_HOME=<profile>, driven by a small ACP client. None of this went through T3.1. The Linear sign-in carries over
The Linear server connected with no sign-in prompt.
agywrote 70 tool schemas to<profile>/antigravity-acp/mcp/linear_linear/, and awhoamitool 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 readplugin_data/<plugin>/token.json.Not tested: 0.1.11 and
mainlaunch Google-account instances withSSH_CONNECTIONset, 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/newreturns before the plugin's MCP server has loadedIn 15 new sessions,
agywrote the Linear tool schemas 178 to 504 ms aftersession/newreturned.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
agystored in<profile>/antigravity-acp/conversations/<id>.db:<mcp_servers>withlinear_linearsession/newreturnedA 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/newreturns, 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,isAntigravityTextGenerationAvailablestill checks only<profile>/config/hooks.jsonand<profile>/config/mcp_config.json. Onceconfig/pluginsis linked,agyconnects 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.mdsays helpers reject such profiles before launch.#39082 already covers this. Its guard also reads
hooks.jsonandmcp_config.jsonat the root of each enabled plugin. #39084 needs the same check if it is the one that merges.feat(agents): link Antigravity plugins into T3 Code profiles