Browse GitHub Copilot News (205)

Stephen Toub breaks down how GitHub rewrote the Copilot agent runtime from a TypeScript/Node.js/V8 stack into a production Rust runtime, largely using Copilot agents. He explains the architectural drivers (in-process hosting, lower memory, better startup), the incremental port strategy, interop layers, regression patterns, and the measured performance gains.

Allison announces general availability of Copilot budget increase requests, letting members request additional AI credits when they hit their limit and enabling org/enterprise owners and billing managers to approve, adjust, or deny requests directly from GitHub settings under usage-based billing.

Julia Gong, Ben Liggett, and Ulugbek Abdullaev explain how GitHub Copilot’s inline suggestions in VS Code moved from three separate models (completions, next edit suggestions, and long-distance edits) to a unified “3-in-1” approach, including the diff-patch output format, training strategy, and evaluation methods used to ship it.

Allison announces a public preview feature where GitHub Copilot suggests allowed values while admins define repository custom properties, helping organizations build consistent governance metadata that can be used to scope rulesets across large fleets of repositories.

Aaron Powell shows how to baseline and then raise unit test coverage in the Interview Coach app using Visual Studio’s code coverage tooling and GitHub Copilot’s Test Agent, moving from targeted tests for a single class to solution-wide analysis and test generation.

Justin Yoo walks through a sample “Interview Coach” app that uses the GitHub Copilot SDK as an agent runtime (outside the editor) to run an interview workflow: ingest a resume, ask behavioral/technical questions, store session context, and generate end-of-interview feedback using MCP tools and Agent Framework handoffs.

Mariyaali announces the general availability of the SQL DW operations skill for Microsoft Fabric Data Warehouse, which lets teams use natural-language prompts (for example via GitHub Copilot CLI) to run bounded, read-only diagnostics and get structured findings, evidence, and recommended next steps for common warehouse incidents.

Allison announces new configuration tiers for GitHub Copilot auto model selection—efficiency, balance, and intelligence—so teams can control how Copilot trades off cost, response quality, and response time per prompt, with billing based on the model selected.

Allison announces new generally available GitHub Copilot usage metrics that track activity in the dedicated VS Code Agents window, including both aggregate (enterprise/org) and per-user fields for 1-day and 28-day reporting periods.

Allison announces improvements to GitHub Copilot code review, including automatic resolution of addressed review comments, smarter commit message suggestions when applying Copilot fixes, and deeper review analysis using Copilot SDK shell tools plus an ensemble approach for Lite reviews.

Tomoko Tanaka shows how her team turned event marketing runbooks into “ops as code” using GitHub Issues, GitHub Actions, and GitHub Copilot. The post breaks down the repo patterns (issue forms, labels, skills in Markdown, and a DRY_RUN switch) that automate setup, daily screening, and post-event reporting with guardrails.

Allison summarizes the September 7 weekly GitHub Copilot releases, including Jira integration in the Copilot app, Project HydraFusion model orchestration in Copilot CLI, new agent automations and voice mode updates in VS Code, and expanded enterprise sandbox controls for Copilot in JetBrains.

Kayla Cinnamon explains how to review agent-generated changes inside the GitHub Copilot app using three built-in panels: a diff view for inspecting edits, a terminal for running project commands, and a browser preview for validating UI changes before creating a pull request.

Allison announces the deprecation of the MAI-Code-1-Flash model across GitHub Copilot experiences and points Copilot Enterprise admins to the steps needed to enable the replacement model via Copilot model policies and settings.

Juan Montes profiles Kinaxis’ Maestro platform and how it uses Azure (including AKS, Databricks, Azure OpenAI, Cosmos DB, and Azure AI Content Safety) to run large-scale supply chain scenario modeling, forecasting, and agentic AI experiences. The piece also touches on Kinaxis’ internal use of GitHub Copilot for an agentic, PR-driven development workflow.

Allison announces generally available enterprise managed permissions for GitHub Copilot agent operations, letting admins centrally decide which actions are blocked, require human approval, or run without prompting across supported Copilot clients.

Allison announces agentic autofix for GitHub Code Quality, letting teams select up to 25 findings and assign them to GitHub Copilot in one action. Copilot applies fixes on a branch, validates the changes, and opens a pull request for review, with usage governed by existing enterprise policy and AI credits.

Waldek Mastykarz explains how to pick a “minimal viable model” for AI coding work by running your own evals instead of defaulting to the most expensive option. Using GitHub Copilot Chat in VS Code, he compares model quality scores and per-run costs across real upgrade scenarios to show why “smarter” can be worse value.

Allison announces updates to GitHub Copilot for JetBrains, including enterprise-managed sandbox policies, cross-file cursor jumps for next edit suggestions, global project context in chat, and enterprise policy diagnostics. The release also adds a preview integration that connects Copilot CLI terminal sessions to IDE context and improves reliability across MCP and agent sessions.

Allison announces GitHub Enterprise Server (GHES) 3.22 general availability, highlighting updates for enterprise administration and collaboration, including Copilot CLI support for disconnected environments, enterprise teams, improvements to repository rulesets and required reviewers, and UI enhancements for issues and pull requests.

Justin Yoo walks through a practical profiling workflow for distributed .NET apps, showing how to identify which process owns a slow user interaction, use Visual Studio CPU profiling to rule out CPU-bound work, and then measure hidden async waiting that doesn’t show up in CPU samples.

Allison’s weekly Copilot changelog highlights new model options (Claude Fable 5.1 and Gemini 3.8 Flash), stronger content protection via honored content exclusions in Copilot app/CLI, and VS Code 1.136 updates aimed at managing agent sessions and getting pull requests ready to merge.

Allison announces general availability of OpenAI’s GPT-6 Astra in GitHub Copilot, highlighting its strength on long-horizon, agentic coding tasks, how it’s billed under usage-based pricing, and where developers and admins can enable and select the model across supported IDEs and clients.

sbaynes shares a short update on HydraFusion in GitHub Copilot, highlighting a shift from picking a single model to orchestrating multiple models that plan, build, critique, and complete coding tasks, with a claim of up to 67% lower cost for comparable outcomes.

GitHub Staff introduces Project HydraFusion, a GitHub Copilot research preview that orchestrates multiple LLMs at runtime to balance quality, cost, and latency for coding tasks. The post explains HydraFusion’s execution patterns, operating principles for safe repo-level changes, and benchmark results across TerminalBench, DeepSWE, and an internal Copilot session benchmark.

Allison announces the deprecation of several AI models used across GitHub Copilot experiences on October 2, 2026, and outlines the replacement models plus the admin steps needed to enable them via Copilot model policies.

Jeremy Winter argues that getting enterprise AI into production is less about picking a single model and more about running an end-to-end system on Azure—spanning infrastructure, data, governance, security, and operations. The post highlights Microsoft AI Foundry, Fabric, Purview, and Azure databases, plus modernization workflows that include GitHub Copilot.

Allison announces that Gemini 3.8 Flash is now available as a selectable model in GitHub Copilot, including where it can be used (IDEs, CLI, and cloud agent), who gets access across Copilot plans, and how admins can control enablement via model policy.

Kayla Cinnamon explains how the GitHub Copilot app can run multiple agent sessions in parallel on the same project by isolating each session with its own Git worktree, so you can queue up tasks (like feature work, accessibility review, and tests) and review results as they complete.

Allison announces that GitHub is gradually reopening sign-ups for Copilot Business and Copilot Enterprise paid by credit card or PayPal, alongside billing and account-vetting changes that affect how seats are activated, charged, and how overage usage may require additional payment.

Cassidy Williams breaks down the new AI vocabulary showing up in developer conversations—loops, harnesses, squads, hill climbing, and model “openness”—and explains how these concepts map to practical ways teams build and improve agent-driven workflows (with GitHub Copilot as a concrete example of a “harness”).

Allison announces an update to GitHub Copilot enterprise-managed settings that lets organizations set any Copilot model as the default for new conversations, with optional per-team overrides via managed settings files.

Allison announces general availability of content exclusion support in the GitHub Copilot app and Copilot CLI, so enterprise, organization, and repository admins can prevent Copilot from using specified files as context and better protect sensitive code during agentic workflows.

Erik Kristensen explains how GitHub Copilot reduced end-to-end cost for agentic coding by optimizing whole tasks (not individual tool calls), including selective compression of noisy command output, removing wasted formatting, tightening prompts with regression tests, and batching background results to avoid extra model turns.

The Visual Studio Code Team shares Insiders updates for VS Code 1.137, focusing on Copilot-related workflow improvements such as clearer model token limits, better context handling when pasting GitHub issue/PR links, and updated new-session composer controls.

Allison announces a generally available GitHub billing update that lets admins set an expiration date on individual user budgets, so temporary budget overrides are removed automatically and users fall back to the next applicable budget.

Allison announces a public preview update to GitHub Copilot code review that adds approval assessments on pull requests and, when enabled by admins, allows Copilot to submit an approval that can count toward required-approvals rules.

Aaron Powell walks through reviewing GitHub pull requests directly inside Visual Studio, from opening the PR list and navigating diffs to leaving inline comments, approving, and merging. He also shows how to bring GitHub Copilot into the review by adding a PR as chat context using the UI or the #pullrequest: command.

Allison announces that Anthropic’s Claude Fable 5.1 is now available as a selectable model in GitHub Copilot, including details on where it’s available, how admins enable it for Business/Enterprise, how it’s billed under usage-based pricing, and the default data-retention requirement plus ZDR options for eligible enterprises.

Allison explains a GitHub Copilot change for GitHub Team plans: when a user has Copilot seats in multiple organizations, model access is now determined only by the organization that is billed for the user’s Copilot usage, aligning governance and billing.