0.0.340

Author: RyanHecht

changelog.md

@@ -1,3 +1,32 @@
+## 0.0.340 - 2025-10-13
+
+- 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 `tool_use` block must have a corresponding `tool_result` 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": {
+            "GITHUB_ACCESS_TOKEN": "GITHUB_TOKEN"
+         }
+    }
+    ```
+
+    Before this change, the CLI would read the value of `GITHUB_TOKEN` from the environment of the CLI and set the environment varaible named `GITHUB_ACCESS_TOKEN` in the MCP process to that value.  With this change, `GITHUB_ACCESS_TOKEN` would now be set to the literal value `GITHUB_TOKEN`.  To get the old behavior, change to this:
+
+    ```json
+    {
+        "env": {
+            "GITHUB_ACCESS_TOKEN": "${GITHUB_TOKEN}"
+         }
+    }
+    ```
+
+
 ## 0.0.339 - 2025-10-10
 
 - Improved argument input to MCP servers in `/mcp add` -- previously, users had to use comma-separated syntax to specify arguments. Now, the "Command" field allows users to input the full command to start the server as if they were running it in a shell