# GitHub Copilot (Agent Plugins 1.0 marketplace bundle)

GitHub Copilot (Agent Plugins 1.0 marketplace bundle) and chock: install methods and steps, what it can enforce, and the evidence behind it.

Install methods: plugin. Agentseam tier unadapted, grade none before a tool runs.

> Ask the user before running any command on this page: each one changes how their agent or repository behaves.

## Install methods

- Plugin: `chock install --client copilot` (ask the user before running it)
- Not wired: agentseam records this agent but has no adapter for its hooks, so chock has nothing to wire.

## Note

This is the Copilot plugin. Copilot's repo hooks are the GitHub Copilot (VS Code agent mode / CLI) row. (Source: Agentseam matrix notes for copilot)

## Install steps

### GitHub Copilot (copilot)

State: tested.

The command (ask the user before running it: it builds a plugin of hooks that change how their agent behaves):

    chock install --selection <code> --client copilot --apply

With --apply, chock runs these steps for GitHub Copilot:

    copilot plugin marketplace add ~/.chock/marketplace/copilot

    copilot plugin install chock-guardrails@chock-local

VS Code finds plugins the Copilot CLI installed. Without the CLI, add the plugin folder to your VS Code user settings yourself:

    {
      "chat.pluginLocations": {
        "~/.chock/marketplace/copilot/claude/chock-guardrails": true
      }
    }

## What it can enforce

- Tier: unadapted
- Grade before a tool runs: none
- Fail mode before a tool runs: n/a
- Basis: vendor-docs
- Recorded: 2026-08-29

## Ask support

The engine records no ask claim for this agent.

## Hook timeout

The engine records no timeout for this agent.

## Test status

- Plugin (copilot): tested.
- Through the plugin install, at hook point plugin-hook: GitHub Copilot CLI 1.0.94, Windows, 2026-10-11. live probe of the chock plugin. `pin-github-actions` refused a create write at preToolUse, before the file landed. `chock-guardrails-protect` refused a shell write to `.chock/guardrails.json` at preToolUse. Not covered: VS Code agent mode, a toggle-file write through the edit tool, and a delete-only apply_patch (org-plan witness/results/witness-copilot-2026-10-11.md, 83f636d)

## Known limits

TIER_UNADAPTED and events={} are deliberate, not a placeholder for an adapter that has not been written yet: a real adapter under this name would claim every payload vscode_copilot already claims (the wire dialect is documented as identical), and adapters.detect() treats a payload two adapters both claim as unidentified -- registering one here would silently stop dispatch working for every existing VS Code/Copilot CLI user. A hook that ships inside a copilot-format bundle is dispatched through the vscode_copilot adapter at runtime; 'copilot' exists only as packaging_data.PACKAGING's identity for the Agent Plugins 1.0 marketplace bundle FORMAT, a genuinely different artifact from vscode_copilot's repo-local .github/hooks/agentseam.json (own manifest, own namespaced paths, published to a marketplace rather than committed to a repo). The honest capability answer is NOT 'none': see EVIDENCE['copilot'] for what was found -- VS Code documents plugin hooks as firing alongside workspace hooks, and documents Copilot CLI and the Copilot app as reading the same com.github.copilot namespace; Copilot CLI's own hooks-reference.md separately lists installed-plugin hooks as one of its combined, executed sources. Recorded here as docs-basis evidence, not a live capability claim, because nothing here was run against a live build.


---

Built from engine [5a4b6287a46e](https://github.com/open-coder-ai/chock/commit/5a4b6287a46e07f9f856d9bbe10622bd1ff2e021) and catalog [1e60d211c1bb](https://github.com/open-coder-ai/chock-catalog/commit/1e60d211c1bb767152c6ab0167932da06ab3a10f).