Copilot CLI: Configure everything from one place with /settings
Quick Answer
GitHub Copilot CLI introduces a unified /settings command for streamlined configuration, integrating previously scattered commands into a single interface.
Quick Take
GitHub Copilot CLI introduces a unified /settings command for streamlined configuration, integrating previously scattered commands into a single interface. Users can now easily adjust settings through a guided UI, inline commands, or scripted changes, enhancing usability and reducing errors in configuration.
Key Points
- /settings command allows browsing and editing all user settings in one place.
- Supports inline setting changes and resetting to defaults with simple commands.
- Provides a searchable dialog with dedicated editors for different setting types.
- Changes apply live upon saving, ensuring immediate feedback on configuration.
- Update the CLI by running 'copilot update' in the terminal.
📖 Reader Mode
~2 min readGitHub Copilot CLI now has a unified, schema-driven home for configuration. The new /settings slash command combines the scattered commands like /theme, /streamer-mode, and /experimental with options that previously required manually editing your settings file into a single, discoverable surface.
One command, three ways to use it
/settings works whether you want a guided UI, a quick one-liner, or a scripted change in a copilot -p invocation:
/settingsopens a full-screen, sectioned dialog where you can browse and edit every user setting./settingssets a value inline (e.g.,/settings autoUpdate true,/settings sessionSync.level full)./settings resetrestores the default for a setting.
Keys are dotted paths into the CLI’s settings schema, and tab completion surfaces every available key — along with the description and the allowed values for booleans, enums, and enum-or-string unions — right next to your prompt. No more guessing key names or types.
A dialog that fits each setting
Open /settings with no arguments and you get a searchable, alt-screen dialog with editors built for each setting type:
- Boolean toggles, enum pickers, and enum-or-string union pickers.
- Free-form string and number editors, with a multi-line editor for prose.
- Dedicated editors for string and number arrays and generic records.
- A
$EDITORfallback for complex JSON containers. Your settings file is only written after the new value parses and passes schema validation, so a typo can’t silently break your next session.
Press / to search, Ctrl+R to reset the focused setting to its default, and Ctrl+E to open the active settings file in your editor. Setting changes that have side effects (like colorMode or streamerMode) apply live the moment you save, whether you toggled them inline, reset them, or edited the file directly.
Want to jump straight to a specific setting? /settings and /settings reset open the dialog focused on that key.
Get the update
Update GitHub Copilot CLI by running copilot update in your terminal, then run /settings to take it for a spin. Share feedback with the /feedback command in a CLI session, or open an issue in our public repository.
— Originally published at github.blog
Want this in your inbox every morning?
Daily brief at your local 8am — bilingual EN/中文, free.
More from GitHub Copilot Changelog
See more →Copilot usage metrics now include more of your active users
GitHub Copilot now enhances usage metrics by incorporating server-side telemetry, revealing previously unreported active users. This update increases daily active user counts and improves report consistency, addressing gaps caused by client-side telemetry failures.