You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,15 @@
1
1
# Docs changelog
2
2
3
+
**26 March 2026**
4
+
5
+
If you use both Copilot CLI and VS Code, when you start the CLI it will automatically connect to a currently open VS Code workspace that matches the directory in which you're using the CLI. You can also manually connect to VS Code by using the `/ide` slash command.
6
+
7
+
This new article documents this feature and outlines the benefits of sharing context, trust settings, and output between Copilot CLI and VS Code:
8
+
9
+
[Connecting GitHub Copilot CLI to VS Code](https://docs.github.com/en/copilot/how-tos/copilot-cli/connecting-vs-code)
10
+
11
+
<hr>
12
+
3
13
**23 March 2026**
4
14
5
15
We've added an article with details of the various command-line options for allowing/denying tools that Copilot CLI can use.
0 commit comments