Finding and installing plugins for GitHub Copilot CLI

Extend Copilot by installing plugins created by the community or your organization.

In this article

Plugins are packages that extend the functionality of Copilot CLI. You can install a plugin from a marketplace that you have registered with the CLI.

For an overview, see Plugins for GitHub Copilot.

Note

You can find help on using plugins by entering copilot plugin [SUBCOMMAND] --help in the terminal.

Find plugins

Plugins are collected in marketplaces. A marketplace is a registry of plugins that you can browse and install. Copilot CLI includes the awesome-copilot marketplace by default.

To list registered marketplaces, enter:

Shell
copilot plugin marketplace list

In an interactive session, enter:

Copilot prompt
/plugin marketplace list

To browse plugins in a registered marketplace, enter:

Shell
copilot plugin marketplace browse MARKETPLACE-NAME

Replace MARKETPLACE-NAME with the marketplace name.

In an interactive session, enter:

Copilot prompt
/plugin marketplace browse MARKETPLACE-NAME

Install plugins

To install a plugin from a registered marketplace, enter:

Shell
copilot plugin install PLUGIN-NAME@MARKETPLACE-NAME

For example, to install database-data-management from awesome-copilot, enter:

Shell
copilot plugin install database-data-management@awesome-copilot

In an interactive session, enter:

Copilot prompt
/plugin install PLUGIN-NAME@MARKETPLACE-NAME

You can also install a plugin from a GitHub repository, a Git URL, a repository subdirectory, or a local path. For accepted formats, see Plugin specification for the install command.

Manage installed plugins

Use these commands to manage installed plugins:

Shell
copilot plugin list
copilot plugin update PLUGIN-NAME
copilot plugin uninstall PLUGIN-NAME
copilot plugin disable PLUGIN-NAME
copilot plugin enable PLUGIN-NAME

disable turns off a plugin without uninstalling it. uninstall removes it. For all commands and options, see GitHub Copilot CLI plugin reference.

Add a marketplace

To register a marketplace hosted in a GitHub repository, enter:

Shell
copilot plugin marketplace add OWNER/REPOSITORY

Replace OWNER/REPOSITORY with the repository that hosts the marketplace. For example:

Shell
copilot plugin marketplace add anthropics/claude-code

In an interactive session, enter:

Copilot prompt
/plugin marketplace add OWNER/REPOSITORY

You can also add a marketplace from a local directory or from a Git repository hosted elsewhere. Use the marketplace directory path for a local source:

Shell
copilot plugin marketplace add /PATH/TO/MARKETPLACE-DIRECTORY

For a Git repository hosted elsewhere, use its Git URL:

Shell
copilot plugin marketplace add https://gitlab.com/OWNER/REPO.git

For guidance on publishing a GitHub-hosted marketplace, see Creating and sharing a plugin marketplace on GitHub.

Remove a marketplace

To unregister a marketplace, enter:

Shell
copilot plugin marketplace remove MARKETPLACE-NAME

In an interactive session, enter:

Copilot prompt
/plugin marketplace remove MARKETPLACE-NAME

When adding a marketplace, you identify it by its source. When removing it, use the marketplace name shown in the marketplace list. The command fails if plugins from the marketplace are still installed. Add --force to also uninstall those plugins.

Turn off a repository default

Repository defaults are optional. To turn off a plugin enabled by repository settings, add a false entry to enabledPlugins in .github/copilot/settings.local.json:

JSON
{
  "enabledPlugins": {
    "PLUGIN-NAME@MARKETPLACE-NAME": false
  }
}

Replace the identifier with the plugin's name and marketplace name. Save the file and start a new session. To turn the plugin back on, set the entry to true.

Do not commit this local settings file. Enterprise managed settings take precedence over repository defaults and local overrides. For details, see GitHub Copilot CLI configuration directory.

Further reading