🧵It's ship city in Copilot + VS Code. Can now clearly see multi-file progress as edits stream in. W/the editor overlay controls, can easily cycle through all changes and accept or discard them.

🧵Instead of applying individual code blocks, can now move chat session to multi-file to apply all code suggestions from the session.

🧵To help add relevant files to the working set, for a Git repo, Copilot multi-file can now suggest additional files based on the files you've already added. Also: Copilot shows suggested files alongside the Add Files button in the wking set. Can also select Add Files and then select Related Files to choose from a list of suggested files.

🧵Mentioned above: can add files to your Copilot multi-file wking set with the new Add File to Copilot Edits context menu action for search results in the Search view and for files in the Explorer view.

🧵 Time for sum debuggin' 🐛 Introducing a new copilot-debug terminal command to help you debug your programs using VS Code. Can use it by prefixing the command that you would normally run with copilot-debug.

🧵were feelin symbolic. Symbols can now easily be added to Copilot Chat and Copilot multi-file by dragging and dropping them from the Outline View or Breadcrumbs into the Chat view.🍞

🧵We’ve also introduced symbol completion in the chat input. By typing # followed by the symbol name, you’ll see suggestions for symbols from files you've recently worked on.

🧵To reference symbols across your entire project, you can use #sym to open a global symbols picker.

🧵folder time, folks. Folders can now be added as context by dragging them from the Explorer, Breadcrumbs, or other views into Copilot Chat📁

🧵When a folder is dragged into Copilot multi-file, all files within the folder are included in the working set.

🧵It's getting graphic 📈VS Code extensions can use the VS Code API to build on the capabilities of Copilot. You can now see a graph of an extension's Copilot usage in the Runtime Status view.

🧵Ok, let's get chatty. 😼 Inline Chat: we made the progress reporting more subtle, while streaming in changes squiggles are disabled, and detected commands are rendered more nicely. Also, we have continued to improve our pseudo-code detection and now show a hint that you can continue with Inline Chat when a line is mostly natural language. This functionality lets you type pseudo code in the editor, which is then used as a prompt for Inline Chat. You can also trigger this flow by pressing ⌘I.

🧵paint it up paint it up, watch it all fall down🎨 Terminal Inline Chat has a fresh coat of paint that brings the look and feel much closer to editor Inline Chat.

🧵We're getting both custom and instructional. Can now use the setting to either specify the custom instructions or specify a file from your workspace that contains the custom instructions. These instructions are appended to the prompt that is used to generate the commit message.

🧵Finally, @workspace (an agent command not to be confused w/Copilot Workspace) got an upgrade. Here's a small novel to cap it off 📒 When you use @workspace to ask Copilot about your currently opened workspace, we first need to narrow the workspace down into a set of relevant code snippets that we can hand off to Copilot as context. If your workspaces is backed by a GitHub repo, we can find these relevant snippets quickly by using Github code search. However, as the code search index tracks the main branch of your repository, we couldn't rely on it for local changes or when on a branch. This milestone, we've worked bring the speed benefits of Github search to branches and pull requests. This means that we now search both the remote index based on your repo's main branch, along with searching any locally changed files. We then merge these results together, giving Copilot a fast and up to date set of snippets to work with.