GitHub Copilot CLI unifies configuration with /settings command
GitHub Copilot CLI introduces a new /settings slash command, consolidating scattered configuration options into a single, schema-driven interface. This provides a discoverable and validated way to manage settings, improving user experience by reducing guesswork and preventing configuration errors. The feature is available now via the `copilot update` command for all Copilot CLI users.
- →Unified /settings command for Copilot CLI configuration
- →Multiple ways to interact with /settings
- →Interactive and validated settings configuration
Features (2) ›
- Unified /settings command for Copilot CLI configuration
The GitHub Copilot CLI now offers a unified /settings slash command to manage all configurations, replacing scattered commands and manual file editing. This command provides a discoverable interface with tab completion for setting keys and types, ensuring that users can easily find and correctly modify their settings.
- Multiple ways to interact with /settings
Users can interact with /settings via a guided UI, a quick inline command (e.g., `/settings autoUpdate true`), or a reset command (`/settings reset`) to restore defaults. The command also supports focusing on specific settings directly.
Enhancements (1) ›
- Interactive and validated settings configuration
The /settings command opens a full-screen dialog with type-specific editors for various settings, including booleans, enums, strings, numbers, and arrays. Settings are only written after passing schema validation, preventing typos from breaking sessions, and changes are applied live.
https://github.blog/changelog/2026-06-11-copilot-cli-configure-everything-from-one-place-with-settings