GitHub published the June update for GitHub Copilot in Visual Studio on July 14, 2026. The release is less about another code-suggestion tweak and more about putting usage visibility, MCP tool trust, and agent execution into the same IDE workflow.
The Copilot Usage window now reflects real-time updates for usage-based billing and can alert developers when they are approaching a limit, have reached it, or have entered overage. Developers can open it from the Copilot badge menu and adjust the warning threshold so they see the boundary before a workflow is interrupted or becomes more expensive.
On the security side, Visual Studio compares an MCP server's configuration and asset fingerprint with a trusted baseline at startup. If the contents have changed, the default trust dialog asks the user to review and approve the change before the server runs. That creates a clear human decision point for an agent that can call external tools.
The update also moves the GitHub Copilot modernization agent for C++ into general availability for MSVC upgrade scenarios. Developers can use Automated mode for end-to-end upgrades or Guided mode to inspect the assessment, plan, and execution before each step.
Pull requests now fit more directly into Copilot Chat and the IDE review flow. Developers can add a pull request's description, changed files, and comments as context, then browse, comment on, approve, and complete GitHub or Azure DevOps pull requests without leaving Visual Studio. Long-distance next edit suggestions can also propose follow-up changes farther away in the active file.
GitHub says the update is available across Copilot Free, Student, Pro, Pro+, Max, Business, and Enterprise. The larger shift is that an agent is now operating across code, tools, usage, and review. Trust dialogs, usage alerts, and Guided mode are therefore part of the daily control surface, not just settings to revisit after an incident.
