GitHub Copilot has introduced two new large‑language‑model options, added a content‑exclusion safeguard, and made the Copilot harness generally available for JetBrains IDEs; at the same time VS Code 1.136 brings a public‑preview Agent Merge capability, experimental multi‑root agent sessions, and UI tweaks for chat.
Model choice and content protection in Copilot
Copilot now surfaces Claude Fable 5.1 for Pro+, Max, Business, and Enterprise tiers, and begins rolling out Gemini 3.8 Flash to the same subscription levels. The addition of these models gives engineers a broader palette of inference characteristics without changing the surrounding integration points. In parallel, the Copilot desktop app and the CLI respect a new content‑exclusion list, preventing files marked as sensitive from being sent to the model during any agentic operation. This behavior applies uniformly across the UI and command‑line workflows.
VS Code 1.136 agent workflow enhancements
The VS Code update adds a public‑preview Agent Merge feature that can automatically resolve review comments, failed checks, and merge conflicts to prepare a pull request for merging. Multi‑root workspaces are now marked experimental, allowing Copilot and Claude agent sessions to run independently in each folder of a workspace. UI‑level changes include experimental chat backgrounds and a hierarchical view that groups related chat sessions and flags those needing attention.
Implications for architecture and operations
Choosing between Claude Fable 5.1 and Gemini 3.8 Flash may affect latency, token usage, and output style, so teams should benchmark the models against their workload constraints. Content exclusions reduce the risk of inadvertently exposing proprietary code to remote inference services, but they also require careful configuration of the exclusion list to avoid unintentionally omitting useful context. Agent Merge can be inserted into CI/CD pipelines to automate PR finalization, yet its preview status means teams should test its behavior before relying on it for production merges. Multi‑root session support changes the way workspace state is partitioned; architects may need to adjust workspace definitions or extension settings to ensure each folder receives the appropriate agent context. The new chat UI features are primarily ergonomic, but the hierarchical session view can help SREs track long‑running debugging conversations.
Related CloudNinjas coverage: AI engineering.
What This Means For Practitioners
- Evaluate Claude Fable 5.1 and Gemini 3.8 Flash in a staging environment to understand cost and performance trade‑offs.
- Define and enforce a content‑exclusion policy for Copilot app and CLI to keep sensitive assets out of model prompts.
- Prototype Agent Merge in a non‑critical branch to verify conflict‑resolution logic before enabling it in production pipelines.
- Test multi‑root workspace configurations to confirm that each folder receives the intended agent session without cross‑contamination.
- Monitor the preview status of Agent Merge and multi‑root support for breaking changes in upcoming VS Code releases.
