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
refactor: frame .plugin as vendor-neutral Open Plugin, not VS Code
`.plugin/plugin.json` is the Open Plugin format, which any agent host can
consume — VS Code is just its first consumer. Verified against VS Code
1.128.1: it only auto-detects three shared manifests (.plugin, .claude-plugin,
bare plugin.json) and has no VS Code-only manifest path.
- Rename agents/vscode/ -> agents/open-plugin/ and set X-Source-Name to
`open-plugin` (was `vscode-plugin`), since the header is part of a neutral
format rather than a VS Code-specific surface.
- Neutralize the .plugin manifest description.
- VS Code installs remain attributable server-side via the MCP `clientInfo`
(`vscode_agent_host`) sent on initialize.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: .plugin/plugin.json
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
{
2
2
"name": "supabase",
3
3
"version": "0.1.12",
4
-
"description": "Supabase tools for VS Code agent plugins — MCP server for managing your Supabase projects and skills to guide you through every stage of building with Supabase.",
4
+
"description": "Official Supabase plugin in the vendor-neutral Open Plugin format with bundled Supabase skills and MCP access for project management, database work, auth, storage, and Postgres best practices.",
Copy file name to clipboardExpand all lines: AGENTS.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,8 +10,8 @@ Keep this repository focused on the shared multi-vendor plugin layout:
10
10
-`.cursor-plugin/plugin.json` defines the Cursor plugin surface
11
11
-`.codex-plugin/plugin.json` defines the Codex plugin surface
12
12
-`.github/plugin/plugin.json` defines the GitHub Copilot plugin surface
13
-
-`.plugin/plugin.json` defines the vendor-neutral open-plugin surface that VS Code auto-detects (see below)
14
-
-`agents/claude/.mcp.json`, `agents/cursor/mcp.json`, `agents/codex/.app.json`, `agents/copilot/.mcp.json`, and `agents/vscode/.mcp.json` hold agent-specific MCP config files
13
+
-`.plugin/plugin.json` defines the vendor-neutral [Open Plugin](https://open-plugins.com/) surface (consumed by VS Code today, and by any other Open Plugin host)
14
+
-`agents/claude/.mcp.json`, `agents/cursor/mcp.json`, `agents/codex/.app.json`, `agents/copilot/.mcp.json`, and `agents/open-plugin/.mcp.json` hold agent-specific MCP config files
15
15
-`gemini-extension.json` defines the Gemini extension manifest
16
16
-`skills/` contains the shipped, real skill files consumed by the supported plugin surfaces
17
17
@@ -53,9 +53,10 @@ Known vendor documentation pages:
-Auto-detects `.plugin/plugin.json`first; uses the vendor-neutral open-pluginmanifest pointing at `agents/vscode/.mcp.json`. Installable via **Chat: Install Plugin From Source**.
59
+
-`.plugin/plugin.json`is the vendor-neutral Open Plugin manifest, not a VS Code-specific format. VS Code (verified against `1.128.1`) only auto-detects three shared manifests — `.plugin/plugin.json`, then `.claude-plugin/plugin.json`, then a bare `plugin.json` — and has no VS Code-only manifest path. Because the format is neutral, its MCP config (`agents/open-plugin/.mcp.json`) uses `X-Source-Name: open-plugin`. VS Code installs are still distinguishable server-side: VS Code sends `clientInfo.name: "vscode_agent_host"` in the MCP `initialize` handshake. Installable via **Chat: Install Plugin From Source**.
59
60
60
61
For vendors listed above, read the official documentation pages for the vendor you are working on and follow the plugin structure required by those docs.
0 commit comments