[
    {
        "role": "user",
        "content": "trying%20to%20setup%20copilot%20cli%20config.json%20to%20allow%20all%20shell%20commands%20without%20asking.%20what%20is%20the%20key%2Fvalue%20pair%20for%20that%3F"
    },
    {
        "role": "assistant",
        "content": "In the GitHub Copilot CLI, there isn\u2019t currently a documented config key/value pair in the `config.json` that permanently allows *all shell commands* (or tools) without asking for confirmation. However, you **can** do this via flags when launching the CLI, or via session commands. Below is what the official docs say and what works in practice.\n\n---\n\n### \ud83d\udcd6 Official Documentation\n\nFrom GitHub\u2019s docs:\n\n- You can start the CLI with `--allow-all`, or its alias `--yolo`, which will enable *all* permissions: all tools, all paths, and all URLs, without prompting you. ([docs.github.com](https://docs.github.com/en/enterprise-cloud%40latest/copilot/how-tos/copilot-cli/set-up-copilot-cli/configure-copilot-cli?utm_source=openai))  \n- There's also a flag specifically for tools: `--allow-all-tools`, which allows tool execution without approval prompts. ([docs.github.com](https://docs.github.com/en/enterprise-cloud%40latest/copilot/how-tos/copilot-cli/set-up-copilot-cli/configure-copilot-cli?utm_source=openai))  \n- For shell permissions: `--allow-all-paths` disables path verification, and `--allow-all-urls` disables URL verification. ([docs.github.com](https://docs.github.com/en/enterprise-cloud%40latest/copilot/how-tos/copilot-cli/set-up-copilot-cli/configure-copilot-cli?utm_source=openai))  \n\n---\n\n### \u26a0\ufe0f What *isn\u2019t* Available Yet\n\n- As of the latest public documentation (checked as of March 2026), there is *no** official setting in `~/.copilot/config.json` (or the repo-level config) like `\"allowAllTools\": true` or similar, which when set, will automatically enable full permissions without passing flags each time. ([docs.github.com](https://docs.github.com/en/enterprise-cloud%40latest/copilot/reference/cli-command-reference?utm_source=openai))  \n- There is mention of a `permissions.json` in a GitHub issue proposing a possible future config structure that includes an `allowAllTools` boolean. But that issue is still under discussion (not yet released or documented as supported). ([github.com](https://github.com/github/copilot-cli/issues/307?utm_source=openai))  \n\n---\n\n### \u2705 What You Can Do Right Now\n\nSince there is no stable, officially supported config key for \u201calways allow all commands\u201d in the config file, here are your options:\n\n1. Use the command-line flag each time:\n\n   ```sh\n   copilot --allow-all\n   ```\n   or\n   ```sh\n   copilot --yolo\n   ```\n\n   This gives full permissions for that session. ([docs.github.com](https://docs.github.com/en/enterprise-cloud%40latest/copilot/how-tos/copilot-cli/set-up-copilot-cli/configure-copilot-cli?utm_source=openai))\n\n2. Combine more specific flags if you only want certain permissions:\n\n   ```sh\n   copilot --allow-all-tools --allow-all-paths --allow-all-urls\n   ```\n\n3. Keep an eye on upcoming releases\u2014support for placing these in `config.json` as a boolean (or similar) might land. For example, the `permissions.json` proposal would include something like:\n\n   ```json\n   {\n     \"allowAllTools\": true\n   }\n   ```\n\n   But until it is merged and released, it doesn\u2019t have effect. ([github.com](https://github.com/github/copilot-cli/issues/307?utm_source=openai))\n\n---\n\nIf you like, I can check your current version of the Copilot CLI and see if there\u2019s been a release that already supports the `config.json` option for auto-allowing tools. Would that be helpful?"
    }
]