GitHub Copilot CLI vv0.0.340
Summary
- Removed the "Windows support is experimental" warning -- we've made some big strides in improving Windows support the last two weeks! Please continue to report any issues/feedback - Improved debu...
Release Notes
- Removed the "Windows support is experimental" warning -- we've made some big strides in improving Windows support the last two weeks! Please continue to report any issues/feedback - Improved debugging by including the Copilot API request ID for model calls errors and stack traces for client errors - Fixed an issue where consecutive orphaned tool calls led to a "Each tooluse block must have a corresponding toolresult block in the next message" message (fixes https://github.com/github/copilot-cli/issues/102) - Added a prompt to approve new paths in -p mode. Also added --allow-all-paths argument that approves access to all paths. - Changed parsing of environment variables in MCP server configuration to treat the value of the env section as literal values (fixes https://github.com/github/copilot-cli/issues/26). Customers who have configured MCP Servers for use with the CLI will need to make a slight modification to their ~/.copilot/mcp-config.json. For any servers they have added with an env section, they will need to go add a $ to the start of the "value" pair of the key value pair of each entry in the env-block, so to have the values treated as references to environment variables. For example: Before: json { "env": { "GITHUBACCESSTOKEN": "GITHUBTOKEN" } } Before this change, the CLI would read the value of GITHUBTOKEN from the environment of the CLI and set the environment varaible named GITHUBACCESSTOKEN in the MCP process to that value. With this change, GITHUBACCESSTOKEN would now be set to the literal value GITHUBTOKEN. To get the old behavior, change to this: json { "env": { "GITHUBACCESSTOKEN": "${GITHUBTOKEN}" } } Run npm install -g @github/copilot@latest to update!