Browse GitHub Copilot Roundups (13)

GitHub Copilot Fusion is now generally available on all Copilot plans, automatically selecting and orchestrating models for individual task steps with configurable effort levels and enterprise model restrictions. Copilot Projects entered public preview for coordinating agents across repositories and connected tools, while VS Code's Agent Host Protocol 1.0 separates agent sessions from editor windows and lets cloud sessions continue across clients. Copilot Memory reached general availability on paid plans, and shared Copilot Automations began rolling out as repository-owned workflows that persist when their creators leave. GitHub Enterprise Cloud customers working with an account team can now receive Copilot access for every licensed user, but that access includes no monthly AI credits, while new permission and plugin controls give administrators more control over agent execution. Together, these releases extend Copilot from individual coding assistance toward persistent, shared agent w

GitHub made the Copilot model policy API generally available and began rolling out one-time global defaults for unconfigured features, giving administrators programmatic policy controls without changing explicit feature choices. Six model retirements require developers to update workflows to supported alternatives, which enterprise administrators may need to enable. Visual Studio now supports attached pull request investigation and agent-assisted NuGet vulnerability fixes, while bring-your-own-model support moves to Agent (Preview) and requires users to re-add Ollama models. The consolidated GitHub app in Microsoft Teams adds coding actions to repository conversations, and Copilot app sessions can transfer their task context and worktree to VS Code for local development and validation. Expanded usage reports add client-level activity and named customizations, pairing broader agent workflows with more detailed administrative controls and reporting.

Welcome to this week's GitHub Copilot roundup, where model choice and agent workflows both became more concrete. Gemini 4 Argon reached general availability, HydraFusion picked up a refreshed pool plus a new HydraFusion Max mode, and GitHub flagged upcoming model deprecations that make policy-driven model governance a practical requirement. On the workflow side, agentic autofix for CodeQL alerts hit GA, VS Code 1.142 brought canvases and a more prominent model picker, and Copilot expanded beyond the IDE with multi-repo chat in Slack and Teams plus terminal-first agent shipping in Copilot CLI. Enterprise teams also got stronger telemetry controls, stricter managed settings enforcement, and clearer cost visibility with My AI Usage Canvas.

Welcome to this week's GitHub Copilot roundup, where the main story is Copilot getting more practical in enterprise settings through on-device models, intelligent routing between local and cloud inference, and generally available local sandboxing powered by Microsoft eXecution Container (MXC). Model choice expanded across Copilot surfaces with Claude Haiku 5.5 going GA and Copilot CLI adding local model discovery via Ollama, making it easier to standardize speed, cost, and privacy defaults across teams. On the governance side, GitHub introduced a purpose-built secret detection model that spans GitHub and Copilot, and added org-level billing and policy controls for Copilot code review so spend and eligibility are easier to manage.

This week's Weekly GitHub Copilot Roundup is about Copilot growing up operationally: more models (GPT-6.1 Sol and Claude Sonnet 5.5), clearer routing with HydraFusion patterns, and more reasons to treat model choice as a governed dependency. Agents kept expanding beyond the IDE with dynamic workflows, scheduled automations, and a new "computer use" preview that brings desktop apps into scope (and into security reviews). Code review automation moved forward with API triggers and a new default effort level, while MCP-based extensibility matured with hosted skills, shared canvases, and managed automation patterns that emphasize evidence, auditability, and controlled execution.

This week's GitHub Copilot updates tightened the feedback loop from pull request review to merge, with a refreshed review experience that tracks findings across pushes and makes resolution behavior easier to understand. On the governance side, admins got new levers for model lifecycle planning (including mid-October deprecations), Auto model selection tiers, and a cleaner workflow for budget increase requests. Agent workflows continued to expand across the Copilot app, VS Code, and the CLI, with more emphasis on portable sessions, safer tool calling via MCP, and stronger measurement through new usage and engagement breakdowns. Under the hood, deep dives on the Rust runtime migration and the new Inline Suggestions model show how GitHub is making agentic changes faster to run and easier to review.

This week's GitHub Copilot updates pushed agentic workflows from "use at your own risk" toward something admins can govern and teams can run every day. Enterprise managed permissions for agent operations and JetBrains sandbox controls make it possible to enforce runtime guardrails (block, allow, or require approval) across common risk areas like shell access, files, and outbound domains. On the workflow side, the Copilot app, VS Code Agents, and CLI routing updates reduced friction in multi-step work, while code review and Code Quality autofix features moved PRs and static analysis closer to an "agent-assisted" default. Rounding it out, new usage metrics for VS Code Agents, a MAI-Code-1-Flash deprecation, and more guidance on MCP and BYOK setups give platform teams clearer levers for rollout, measurement, and cost control.

This week in the Weekly GitHub Copilot Roundup, the model lineup expanded (GPT-6 Astra GA, plus Gemini 3.8 Flash and Claude Fable 5.1) while deprecations and policy updates made it clear that model choice is now an admin and billing decision as much as a developer preference. At the same time, Project HydraFusion signaled a shift from picking one model to routing work across multiple models, with early experiments showing how orchestration can balance quality, latency, and spend. Governance also tightened across agent workflows, with content exclusions reaching the Copilot app and CLI, clearer identity constraints for cloud agents in Actions, and new budget expiration controls. On the workflow side, VS Code kept making agent sessions more reviewable, and Copilot code review entered a new phase with optional approvals that can satisfy branch protection rules if you choose to enable them.

This week's GitHub Copilot updates center on governance that admins can actually operate: unified policies across chat and cloud agents, clearer seat and usage billing behavior, and GA model controls that affect compliance and cost attribution. On the workflow side, the Copilot app's Customize tab is now the place to standardize MCP servers, plugins, and shared tools, while shared agent sessions in Slack and Microsoft Teams push Copilot work into auditable team spaces. Code review expands eligibility (including bot and cloud agent PRs) and adds better lifecycle tracking, and the IDE story keeps evolving with Visual Studio and VS Code adding practical model selection, effort controls, BYOM options, and even persistent agent sessions via Agent Host and AHP.

This week's GitHub Copilot updates focus on making agent work more collaborative, tool-aware, and governable. Shared agent sessions are now in public preview for Microsoft Teams and Slack, keeping conversations tied to secure sandboxes and pull requests so teams can review what changed and why. MCP momentum continued with hosted connector setup, practical tool servers (Playwright and SQL), and a portable Agent Plugins 1.0 packaging story that supports repeatable workflows across clients. Alongside new managed settings for JetBrains and more hands-on guidance for tokens and budgets, the thread running through the week is clear: scale Copilot usage by pairing better workflows with stronger controls.

This week's GitHub Copilot roundup is about operational reality: more models in the picker, more places Copilot runs, and better tools to understand what it costs. New options like Gemini 3.7 Flash, Grok 4.6, Kimi K3, and MAI-Code-1.1-Flash push model selection into normal platform governance, while improved token visibility and per-model usage reporting make spend easier to attribute. On the agent side, Agent Plugins 1.0 GA and smoother MCP setup make portable, tool-driven workflows more practical, with clearer patterns for guardrails like allowlists, least privilege, and PR-based review. Across IDEs and enterprise environments (including GHES 3.22 RC), the message is consistent: treat Copilot like part of your toolchain, with policies, instructions, and review paths that keep outputs safe and repeatable.

This week's GitHub Copilot updates were about making agent workflows portable, governable, and easier to operate. MCP and the Agent Plugins 1.0 spec continued to solidify a shared integration layer, while Azure DevOps added a hosted, Entra ID-authenticated Remote MCP Server that reduces local setup. On the operations side, Kimi K3 reached GA, September model deprecations got a clear timeline, and billing and ROI reporting moved further into first-party GitHub dashboards. Rounding it out, enterprise controls (MCP allow/deny lists, team-specialized managed settings, and third-party agent usage reporting) and day-to-day UX tweaks (review effort levels, comment-triggered automations, and better session visibility in VS Code) made Copilot feel more predictable in real team workflows.