VS Code bundles Copilot, debug logs

Visual Studio Code 1.116, released April 15, folds GitHub Copilot into the editor by default and adds disk-persisted logs for failed agent sessions. (code.visualstudio.com) Microsoft says users no longer need to install the GitHub Copilot Chat extension to start using Copilot in Visual Studio Code 1.116. The release notes list “GitHub Copilot built-in” as a headline change alongside new agent tools. (code.visualstudio.com) The same release adds Agent Debug Logs that store previous session logs locally on disk, so developers can reopen a failed chat or agent run after the session ends. Microsoft ties the feature to the setting `github.copilot.chat.agentDebugLog.fileLogging.enabled`. (code.visualstudio.com) In plain terms, an agent is the part of Copilot that can plan steps, call tools, and work through a coding task instead of only answering one prompt. Visual Studio Code’s documentation says those agents can run locally in the editor, through Copilot Command Line Interface sessions on a machine, or in cloud-backed workflows. (code.visualstudio.com) The new log panel is meant to show what the agent actually did: a time-ordered record of prompts, tool calls, errors, and sub-agent activity. Microsoft’s debug-view documentation says the panel also includes a flow chart and a summary with counts for tool calls, tokens, errors, and duration. (code.visualstudio.com) That gives developers a way to inspect why an automated coding session stalled, picked the wrong tool, or failed on a customization. Microsoft has been expanding those controls for months, including agent troubleshooting in version 1.111 and longer-running agent workflows in version 1.110. (code.visualstudio.com, code.visualstudio.com) The shift also changes where artificial intelligence shows up in the product. Visual Studio Code’s home page now describes the editor as an “AI code editor,” and recent releases have added browser debugging for agents, sandboxing for local Model Context Protocol servers, and controls for Copilot Command Line Interface autonomy. (code.visualstudio.com, code.visualstudio.com) Microsoft has also been tightening Copilot’s place inside the editor after shipping security fixes for the GitHub Copilot Chat extension in version 1.110.1 on March 4, 2026. Moving Copilot into the core product reduces one installation step, but it also makes the editor’s default setup more dependent on built-in artificial intelligence features and their logging controls. (code.visualstudio.com) For developers updating today, the practical change is simple: Copilot is already there when Visual Studio Code opens, and failed agent runs can leave a local paper trail instead of disappearing with the chat tab. (code.visualstudio.com)