Skip to content

GitHub Copilot CLI installs Loom's MCP server and skills from the repository's Agent Plugins package - #730

Open
zlareb1 wants to merge 8 commits into
mainfrom
feat/agent-plugins-manifest
Open

zlareb1 wants to merge 8 commits into
mainfrom
feat/agent-plugins-manifest

Conversation

@zlareb1

@zlareb1 zlareb1 commented Nov 16, 2026 •

Copy link
Copy Markdown
Member

Changelog category (leave one):

  • New Feature

Changelog entry (one or two sentences a user of Loom can read without the diff; the release pull request collects these into the release notes):

copilot plugin install ClickHouse/loom installs Loom in GitHub Copilot CLI (experimental): the repository root is an Agent Plugins package that adds the loom MCP server, pointed at a single-user server on the same machine, and the loom and loom-code skills.

Why

Copilot CLI already installs from this repository, but it finds only .claude-plugin/plugin.json and installs it as loom-code-skill: the two skills and no MCP server. Copilot CLI and the Awesome Copilot marketplace read an Agent Plugins 1.0.0 package: a root plugin.json with only the spec's fields and an mcp.json next to it. Credentials may not appear in the package, so the entry is the URL a single-user server serves without a token, the default the Cursor plugin uses.

Scope and risk

Two new root files and their docs. The package ships the root skills/ as they are; no hook, op or server code changes. The version follows the server's: prepare.py pins plugin.json with the other root manifests. Claude Code, Codex, Cursor and Gemini CLI read their own manifests and do not read the new files. A user entry named loom does not replace the plugin's entry in Copilot CLI 1.0.112, so the docs send a team server to the manual entry instead (or copilot plugin uninstall clickhouse-loom first), and mark the plugin experimental: a Copilot session was not run.

Compatibility, rollout and rollback

  • Wire: none.
  • Operator steps: none.
  • Rollback: reverting removes the two files; an installed plugin keeps working until it is uninstalled.

Tests

  • tests/unit/test_agent_plugin.py: the manifest holds only Agent Plugins fields, the docs' uninstall command uses its name, and the entry is the Cursor plugin's local URL with no headers. The version is checked by test_release_prepare.py through the new pin, and the root skills by test_cursor_plugin.py.
  • The Awesome Copilot intake gates, run from that repository's scripts against this branch: Agent Plugins manifest compliance, the mcp.json check and vally lint on both skills pass.
  • Copilot CLI 1.0.112, earlier installs: a loom-code-skill install made from main becomes clickhouse-loom with the MCP server on copilot plugin update loom-code-skill; installing again without updating keeps both. With copilot plugin marketplace add on this branch, loom-code-skill@loom installs the root package, MCP server included. The docs say both.
  • Copilot CLI 1.0.112 in an empty HOME: copilot plugin install <checkout> installs clickhouse-loom 1.2.0 with two skills, and copilot mcp get loom shows the plugin's entry. The entry, with its port changed to a local Loom's, answered MCP initialize, tools/list (21 tools) and a loom_memory_set. A Copilot session needs a sign-in and was not run.
  • make format lint typecheck; the release, link, docs and agent-instruction unit tests; claude plugin validate . for the changed marketplace description.

AI assistance in the code (leave one; writing this description with AI is fine):

  • AI-generated (an agent wrote most of the diff): Claude Code. Checked: the venue's own gate scripts and a real Copilot CLI install against this branch, as listed above.

  • I can explain every line of this diff and how it interacts with the rest of Loom.

Checklist

  • make format-check, make lint, make typecheck and make test-unit pass; the integration suite passes if server behaviour changed.
  • Docs under docs/ describe the system as it now is, and this description names any operator steps and wire changes.
  • Repository text has no dates, people, host names, internal namespaces, ticket or decision numbers; the history goes in this description (tests/unit/test_public_copy.py).
  • Commits are signed off (git commit -s), as CONTRIBUTING.md asks.

🤖 Generated with Claude Code

zlareb1 and others added 8 commits November 16, 2026 07:18
…ository's Agent Plugins package

The root plugin.json and mcp.json are an Agent Plugins 1.0.0 package: the
manifest has only the spec's fields, and the entry is the URL of a
single-user server on the same machine, with no headers. The package ships
the root skills, and the release pins its version with theirs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
…cks the fixed skills directory

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
… installs, and the plugin test keeps only its own checks

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
…ry was checked

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
… lands

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
…ll and to the marketplace entry

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
…be the Agent Plugins package as it is

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
…, and the test ties the documented uninstall to its name

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant