GitHub Copilot weekly releases — August 31
This week, GitHub Copilot expands model choice and content protections, while VS Code adds new ways to manage agent sessions and get pull requests merge-ready.
By Dillip Chowdary • Sep 05, 2026 • Source: GitHub Changelog
What happened
GitHub has expanded the capabilities of GitHub Copilot by introducing broader model selection and enhanced content protections for users. At the same time, the integration with VS Code has been updated to provide developers with new mechanisms to manage active agent sessions and prepare pull requests for merging. These changes, released for the week of August 31, aim to give builders more control over their AI-assisted workflows and improve security during the development lifecycle.
How it works
This
Advertisement
Tech Pulse Daily
Get tomorrow's pulse first
Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.
Why it matters
Back to changelog This week, GitHub Copilot expands model choice and content protections, while VS Code adds new ways to manage agent sessions and get pull requests merge-ready. GitHub Copilot, general Claude Fable 5.1 is available to Copilot Pro+, Max, Business, and Enterprise users.
Who is affected
Gemini 3.8 Flash is rolling out to Copilot Pro, Pro+, Max, Business, and Enterprise users. GitHub Copilot app and Copilot CLI Copilot app and CLI now honor content exclusions, keeping sensitive code out of context across agentic workflows.
What to watch next
GitHub Copilot in JetBrains The GitHub Copilot harness is now generally available in Copilot for JetBrains, providing faster feature delivery and better code quality. See the full write-up from GitHub Changelog via the source link for quotes and complete context.
Developer Action Items
- ☐ Diff the official changelog for Claude / Gemini / GitHub 5.1 before you bump — APIs, defaults, and removed flags only.
- ☐ Install through the vendor's documented channel in staging; keep a one-command rollback and time-box the canary.
- ☐ Grep your repo for old flag names, lockfile pins, and plugin versions that the notes mark as breaking.
- ☐ Prefer the first patch cut over the day-zero tag unless you have a reason to be on the leading edge.
- ☐ If GitHub Changelog did not name a region, plan, or SKU, screenshot the official availability line before you promise it to users.
Author
Dillip Chowdary
Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.
Related on Tech Bytes
Advertisement