Replace .copilot/config.json references with .copilot/settings.json (#60921)

Co-authored-by: hubwriter <hubwriter@github.com>

Author: tpope

content/copilot/how-tos/copilot-cli/manage-pull-requests.md

@@ -156,7 +156,7 @@ When resolving conflicts, {% data variables.copilot.copilot_cli_short %} needs t
 
 To set a default merge strategy so that you are not prompted each time, add the `mergeStrategy` setting to your configuration file. You can set this in your personal user settings for {% data variables.product.prodname_copilot_short %}, or in the repository settings.
 
-* **User settings**: Add `"mergeStrategy": "rebase"` or `"mergeStrategy": "merge"` to your user-level configuration file (typically `~/.copilot/config.json`).
+* **User settings**: Add `"mergeStrategy": "rebase"` or `"mergeStrategy": "merge"` to your user-level configuration file (typically `~/.copilot/settings.json`).
 * **Repository settings**: Add the same setting to `.github/copilot/settings.json` in your repository root.
 
 ## Fixing CI failures

content/copilot/how-tos/copilot-cli/set-up-copilot-cli/authenticate-copilot-cli.md

@@ -67,7 +67,7 @@ By default, the CLI stores your OAuth token in your operating system's keychain
 | Windows | Credential Manager |
 | Linux | libsecret (GNOME Keyring, KWallet) |
 
-If the system keychain is unavailable—for example, on a headless Linux server without `libsecret` installed—the CLI prompts you to store the token in a plaintext configuration file at `~/.copilot/config.json`.
+If the system keychain is unavailable—for example, on a headless Linux server without `libsecret` installed—the CLI prompts you to store the token in a plaintext configuration file at `~/.copilot/settings.json`.
 
 When you run a command, {% data variables.copilot.copilot_cli_short %} checks for credentials in the following order:
 

content/copilot/how-tos/copilot-cli/set-up-copilot-cli/configure-copilot-cli.md

@@ -41,10 +41,10 @@ If you choose to trust the directory for future sessions, the trusted directory
 
 You can edit the list of permanently trusted directories.
 
-1. Open the CLI’s `config.json` file. By default, it’s stored in a `.copilot` folder under your home directory:
+1. Open the CLI’s `settings.json` file. By default, it’s stored in a `.copilot` folder under your home directory:
 
-   * **macOS/Linux**: `~/.copilot/config.json`
-   * **Windows**: `$HOME\.copilot\config.json`
+   * **macOS/Linux**: `~/.copilot/settings.json`
+   * **Windows**: `$HOME\.copilot\settings.json`
 
   You can change the config location by setting the `COPILOT_HOME` environment variable.
 

content/copilot/how-tos/copilot-cli/steer-remotely.md

@@ -58,7 +58,7 @@ Details for accessing the session remotely are displayed when the interactive se
 
 ### Configuring remote access to always be enabled
 
-If you always want your interactive CLI sessions to be remotely accessible, add the following to your {% data variables.product.prodname_copilot_short %} configuration file (typically located at `~/.copilot/config.json`):
+If you always want your interactive CLI sessions to be remotely accessible, add the following to your {% data variables.product.prodname_copilot_short %} configuration file (typically located at `~/.copilot/settings.json`):
 
 ```json copy
 {

content/copilot/how-tos/copilot-cli/use-copilot-cli-agents/overview.md

@@ -271,7 +271,7 @@ For additional information use one of the following commands in your terminal:
 
   `copilot help config`
 
-  You can adjust the configuration settings by editing the `config.json` file, which is located, by default, in the `~/.copilot` directory. This location can be changed by setting the `COPILOT_HOME` environment variable.
+  You can adjust the configuration settings by editing the `settings.json` file, which is located, by default, in the `~/.copilot` directory. This location can be changed by setting the `COPILOT_HOME` environment variable.
 
 * **Environment variables** that affect {% data variables.copilot.copilot_cli_short %}:
 

content/copilot/reference/copilot-cli-reference/cli-command-reference.md

@@ -23,7 +23,7 @@ The `~/.copilot` directory contains the following top-level items.
 
 | Path | Type | Description |
 |------|------|-------------|
-| `config.json` | File | Your personal configuration settings |
+| `settings.json` | File | Your personal configuration settings |
 | `copilot-instructions.md` | File | Personal custom instructions (applied to all sessions) |
 | `instructions/` | Directory | Additional personal `*.instructions.md` files |
 | `mcp-config.json` | File | User-level MCP server definitions |
@@ -46,10 +46,13 @@ The `~/.copilot` directory contains the following top-level items.
 
 The following files are designed to be edited by you directly, or managed through CLI commands.
 
-### `config.json`
+### `settings.json`
 
 This is the primary configuration file for {% data variables.copilot.copilot_cli_short %}. You can edit it directly in a text editor, or use interactive commands like `/model` and `/theme` to change specific values from within a session. The file supports JSON with comments (JSONC).
 
+> [!NOTE]
+> The configuration file was renamed from `config.json` to `settings.json`. Existing settings are automatically migrated from `~/.copilot/config.json` on startup.
+
 For the full list of settings and how they interact with repository-level configuration, see [Configuration file settings](#configuration-file-settings) later in this article.
 
 > [!TIP]
@@ -91,7 +94,7 @@ For more information, see [AUTOTITLE](/copilot/how-tos/copilot-cli/customize-cop
 
 ### `hooks/`
 
-Store user-level hook scripts here. These hooks apply to all your sessions. You can also define hooks inline in `config.json` using the `hooks` key. Repository-level hooks (in `.github/hooks/`) are loaded alongside user-level hooks.
+Store user-level hook scripts here. These hooks apply to all your sessions. You can also define hooks inline in your user configuration file (`~/.copilot/config.json`) using the `hooks` key. Repository-level hooks (in `.github/hooks/`) are loaded alongside user-level hooks.
 
 For more information, see [AUTOTITLE](/copilot/how-tos/copilot-cli/customize-copilot/use-hooks).
 
@@ -168,29 +171,29 @@ The `--config-dir` option takes precedence over `COPILOT_HOME`, which in turn ta
 
 | Item | Safe to delete? | Effect |
 |------|-----------------|--------|
+| `agents/`, `skills/`, `hooks/` | Not recommended | You will lose your personal customizations. Back up first. |
+| `copilot-instructions.md`, `instructions/` | Not recommended | You will lose your personal custom instructions. Back up first. |
+| `installed-plugins/` | Not recommended | Use `copilot plugin uninstall` instead, to ensure plugin metadata in `settings.json` stays consistent. |
 | `logs/` | Yes | Log files are re-created each session. Deleting them has no functional impact. |
+| `lsp-config.json` | Not recommended | You will lose your user-level LSP server definitions. Back up first. |
+| `mcp-config.json` | Not recommended | You will lose your user-level MCP server definitions. Back up first. |
+| `permissions-config.json` | With caution | Resets all saved permissions. The CLI will prompt you again for tool and directory approvals. |
 | `plugin-data/` | Yes | Plugin persistent data is re-created as needed. |
 | `session-state/` | With caution | Deleting removes session history. You will no longer be able to resume past sessions. |
 | `session-store.db` | With caution | Deleting removes cross-session data. The file is re-created automatically. |
-| `config.json` | With caution | Resets all configuration to defaults. You will need to reconfigure your preferences and re-authenticate. |
-| `permissions-config.json` | With caution | Resets all saved permissions. The CLI will prompt you again for tool and directory approvals. |
-| `installed-plugins/` | Not recommended | Use `copilot plugin uninstall` instead, to ensure plugin metadata in `config.json` stays consistent. |
-| `mcp-config.json` | Not recommended | You will lose your user-level MCP server definitions. Back up first. |
-| `lsp-config.json` | Not recommended | You will lose your user-level LSP server definitions. Back up first. |
-| `copilot-instructions.md`, `instructions/` | Not recommended | You will lose your personal custom instructions. Back up first. |
-| `agents/`, `skills/`, `hooks/` | Not recommended | You will lose your personal customizations. Back up first. |
+| `settings.json` | With caution | Resets all configuration to defaults. You will need to reconfigure your preferences and re-authenticate. |
 
 ## Configuration file settings
 
 Settings cascade from user to repository to local, with more specific scopes overriding more general ones. Command-line options and environment variables always take the highest precedence.
 
 | Scope | Location | Purpose |
 |-------|----------|---------|
-| User | `~/.copilot/config.json` | Global defaults for all repositories. Use the `COPILOT_HOME` environment variable to specify an alternative path. |
+| User | `~/.copilot/settings.json` | Global defaults for all repositories. Use the `COPILOT_HOME` environment variable to specify an alternative path. |
 | Repository | `.github/copilot/settings.json` | Shared repository configuration (committed to the repository). |
 | Local | `.github/copilot/settings.local.json` | Personal overrides (add this to `.gitignore`). |
 
-### User settings (`~/.copilot/config.json`)
+### User settings (`~/.copilot/settings.json`)
 
 These settings apply across all your sessions and repositories. You can edit this file directly, or use slash commands to update individual values.
 

content/copilot/reference/copilot-cli-reference/cli-config-dir-reference.md

@@ -119,12 +119,12 @@ copilot -p "Fix the race condition in the worker pool" \
 
 Alternatively, you can set the `COPILOT_MODEL` environment variable to specify a model for the duration of the shell session.
 
-To persist a model selection across shell sessions, you can set the `model` key in the CLI configuration file. This file is located at `~/.copilot/config.json` (or `$COPILOT_HOME/.copilot/config.json` if you have set the `COPILOT_HOME` environment variable). Some models also allow you to set a reasoning effort level, which controls how much time the model spends thinking before responding.
+To persist a model selection across shell sessions, you can set the `model` key in the CLI configuration file. This file is located at `~/.copilot/settings.json` (or `$COPILOT_HOME/settings.json` if you have set the `COPILOT_HOME` environment variable). Some models also allow you to set a reasoning effort level, which controls how much time the model spends thinking before responding.
 
 ```json copy
 {
   "model": "gpt-5.3-codex",
-  "reasoning_effort": "low"
+  "effortLevel": "low"
 }
 ```
 
@@ -138,7 +138,7 @@ When determining which model to use for a given prompt, the CLI checks for model
 * Where a custom agent is used: the model specified in the custom agent definition (if any).
 * The `--model` command line option.
 * The `COPILOT_MODEL` environment variable.
-* The `model` key in the configuration file (`~/.copilot/config.json` or `$COPILOT_HOME/.copilot/config.json`).
+* The `model` key in the configuration file (`~/.copilot/settings.json` or `$COPILOT_HOME/settings.json`).
 * The CLI's default model.
 
 ## Using custom agents