github / github/copilot-cli

Feature Request: --disable-plugin flag for per-session plugin control

Ouverte
#3,452 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
area:plugins
Langage dominant
Shell
Étoiles
11.2k
Forks
1.9k
Merge moyen
14 h 16 min
PR mergées (30 j)
6

Description

## Summary

Currently, there is no way to start a Copilot CLI session with specific plugins disabled without fully uninstalling them. A `--disable-plugin ` startup flag would allow lightweight sessions without losing plugin configuration.

## Current behaviour

The only way to start without a plugin is to uninstall it:
```bash
copilot plugin uninstall
# ...later...
copilot plugin install
```

## Proposed change

Add a `--disable-plugin ` flag (can be used multiple times, similar to the existing `--disable-mcp-server`):

```bash
# Start a minimal session — no user plugins, only built-in tools
copilot --disable-plugin security-best-practices --disable-plugin context-engineering

# Or a blanket flag to skip all plugins for this session
copilot --no-plugins
```

This mirrors the existing pattern of `--disable-mcp-server` and `--disable-builtin-mcps` which already provide per-session MCP control.

## Use case

Power users often configure multiple plugins for different workflows. A simple alias pattern like:

```bash
alias copilot_minimal='copilot --no-plugins --disable-mcp-server playwright --disable-mcp-server postgres'
```

...would let you switch between heavy and lightweight sessions without touching installed state.

## Related

- #2714 — requests persistent `plugin enable/disable` commands (different angle: that is config-level; this is per-session flag)

## Notes

The feature gap is noticeable because MCP servers already have this per-session control (`--disable-mcp-server`) but plugins do not. Parity between the two would make the CLI much more composable for scripting and alias-based workflows.

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

Commencez par localiser les définitions existantes des options --disable-mcp-server et --disable-builtin-mcps, puis suivez la manière dont le démarrage de la session charge les plugins. Définissez le comportement des flags --disable-plugin répétés et de --no-plugins, puis ajoutez une couverture de tests montrant que les plugins désactivés sont ignorés sans modifier la configuration installée.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
shell
Domaine
cli
Type d'issue
Fonctionnalité
Difficulté
4/5
Temps estimé
3-5 jours
Activité
Calme
Clarté
Plutôt claire
Accessibilité débutants
48/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.