<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>RADAR — GitHub Copilot changelog</title>
    <link>https://radar.trulysovereign.com</link>
    <atom:link href="https://radar.trulysovereign.com/feeds/source/github-copilot-changelog.xml" rel="self" type="application/rss+xml"/>
    <description>Changes RADAR detected at GitHub Copilot changelog.</description>
    <language>en</language>
    <lastBuildDate>Sat, 21 Nov 2026 19:19:18 GMT</lastBuildDate>
    <item>
      <title>Gemini 4 Neon now available in GitHub Copilot</title>
      <link>https://radar.trulysovereign.com/items/f30be171-a7cb-406e-ad6b-1428c8347e78</link>
      <guid isPermaLink="false">f30be171-a7cb-406e-ad6b-1428c8347e78</guid>
      <pubDate>Thu, 19 Nov 2026 07:29:20 GMT</pubDate>
      <category>verify_only</category>
      <source url="https://github.blog/changelog/2026-11-18-gemini-4-neon-in-github-copilot">GitHub Copilot changelog</source>
      <description>GitHub Copilot added Gemini 4 Neon as a selectable model for Pro+, Max, Business, and Enterprise users across all supported IDEs and clients. The model is billed at provider list pricing under usage-based billing. Rollout is gradual.

Why it matters: Teams using GitHub Copilot on usage-based billing will incur charges at Google's list pricing when this model is selected. Enterprise and Business administrators must review model policy settings, as new models are automatically enabled by default unless the global default is disabled or the model is explicitly blocked.

What to do: Check Copilot settings model policy to confirm whether Gemini 4 Neon should be enabled for your organization. If usage-based billing applies, review provider list pricing at the linked Models and pricing page to understand cost implications before the model becomes available to users.</description>
    </item>
    <item>
      <title>GitHub Copilot adds eight MCP connectors in public preview</title>
      <link>https://radar.trulysovereign.com/items/dea727de-c370-4d93-8802-06914ccc7ad0</link>
      <guid isPermaLink="false">dea727de-c370-4d93-8802-06914ccc7ad0</guid>
      <pubDate>Thu, 19 Nov 2026 07:29:09 GMT</pubDate>
      <category>verify_only</category>
      <source url="https://github.blog/changelog/2026-11-18-connect-supabase-box-calendly-and-more-to-copilot">GitHub Copilot changelog</source>
      <description>GitHub added eight MCP server connectors to Copilot: Box, Buildkite, Calendly, ClickUp, Mixpanel, Supabase, Webflow, and Wix. These join more than 25 existing connectors and are available in public preview across all Copilot plans. Copilot Business and Enterprise require admin enablement of the Editor preview features policy. Enterprises with individual MCP allowlists (not wildcards) must add each new connector explicitly.

Why it matters: Teams using these services can now query and act on them directly from Copilot sessions without switching contexts. Enterprises with restrictive MCP allowlists will block these connectors by default until an admin adds them, preventing developers from using the integrations even after connecting them.

What to do: If you use Copilot Business or Enterprise, verify the Editor preview features policy is enabled and check whether your MCP allowlist uses wildcards or lists connectors individually. If individual, add the eight new connector identifiers to the allowlist before developers attempt to connect them.</description>
    </item>
    <item>
      <title>GitHub Copilot adds team-level plugin defaults for Business and Enterprise</title>
      <link>https://radar.trulysovereign.com/items/07fc4a70-8e96-477d-a082-8ee87ab565d0</link>
      <guid isPermaLink="false">07fc4a70-8e96-477d-a082-8ee87ab565d0</guid>
      <pubDate>Wed, 18 Nov 2026 20:33:17 GMT</pubDate>
      <category>verify_only</category>
      <source url="https://github.blog/changelog/2026-11-18-customize-github-copilot-for-your-team">GitHub Copilot changelog</source>
      <description>Team maintainers and organization owners can now set approved Agent Plugins as defaults for organization teams through a new Customize Copilot tab. Teams can browse plugins from built-in marketplaces, enterprise marketplaces, and add marketplaces from GitHub repositories. Selected plugins are enabled by default for direct team members in VS Code, GitHub Copilot app, and Copilot CLI. Members can override team defaults where policy permits, and child teams do not inherit parent team plugin defaults.

Why it matters: Teams can standardize plugin configurations without requiring each member to perform identical setup. This reduces onboarding friction and ensures consistent tooling across team members while preserving individual override capability within policy boundaries.

What to do: If you manage GitHub Copilot for teams using Business or Enterprise, review your teams' plugin usage and determine which plugins should be team defaults. Navigate to your organization team on github.com, select the Customize Copilot tab, and configure approved plugins for each team.</description>
    </item>
    <item>
      <title>GitHub Copilot adds GPT-6.2 Astra and GPT-6.2 Sol models</title>
      <link>https://radar.trulysovereign.com/items/be722abc-6d28-4733-be1b-c590938c9581</link>
      <guid isPermaLink="false">be722abc-6d28-4733-be1b-c590938c9581</guid>
      <pubDate>Tue, 17 Nov 2026 20:58:26 GMT</pubDate>
      <category>verify_only</category>
      <source url="https://github.blog/changelog/2026-11-17-openais-gpt-6-2-astra-and-gpt-6-2-sol-now-available">GitHub Copilot changelog</source>
      <description>GitHub Copilot now offers GPT-6.2 Astra and GPT-6.2 Sol, available to Pro+, Max, Business, and Enterprise users across Visual Studio Code, Visual Studio, JetBrains IDEs, Xcode, Eclipse, Copilot CLI, GitHub Copilot coding agent, GitHub Copilot app, github.com, and GitHub Mobile. Both models are billed at provider list pricing under usage-based billing. Rollout is gradual.

Why it matters: These models are designed for agentic coding and code review with stronger coding judgment than earlier GPT-6 models. In early testing, GPT-6.2 Astra completed agentic coding tasks using noticeably fewer tokens than GPT-6 Astra, and GPT-6.2 Sol caught nearly twice as many real issues in code review as GPT-6.1 Sol while keeping findings accurate. Token efficiency affects usage-based billing costs.

What to do: Check the model picker in your IDE or Copilot interface to confirm availability. If you are a Copilot Enterprise or Business administrator, review the model policy in Copilot settings to verify whether GPT-6.2 models are enabled under your default model enablement configuration.</description>
    </item>
    <item>
      <title>GitHub Copilot adds MAI Code 2 and MAI Code 2 Flash models</title>
      <link>https://radar.trulysovereign.com/items/d8d89761-7807-4e16-be6b-1b23e4531abd</link>
      <guid isPermaLink="false">d8d89761-7807-4e16-be6b-1b23e4531abd</guid>
      <pubDate>Tue, 17 Nov 2026 20:58:17 GMT</pubDate>
      <category>verify_only</category>
      <source url="https://github.blog/changelog/2026-11-17-mai-code-2-and-mai-code-2-flash-in-github-copilot">GitHub Copilot changelog</source>
      <description>GitHub Copilot now includes two new Microsoft AI coding models: MAI Code 2 (available in Pro, Pro+, Max, Business, and Enterprise tiers) and MAI Code 2 Flash (available in Free, Student, Pro, Pro+, Max, Business, and Enterprise tiers). Both models are available to subscribers on annual plans and can be selected in the model picker across all Copilot interfaces including VS Code, Visual Studio, CLI, JetBrains, Xcode, and GitHub Mobile. Both models use usage-based billing.

Why it matters: MAI Code 2 Flash is now available in the Free tier, expanding model choice for users without paid subscriptions. The usage-based billing model means costs will vary by actual token consumption rather than flat subscription rates. Enterprise and Business administrators must manage access through model policy settings, as new models are enabled by default unless explicitly disabled.

What to do: If you are a Copilot Enterprise or Business administrator, review the model policy in Copilot settings to verify whether MAI Code 2 and MAI Code 2 Flash should be enabled for your organization under the default model enablement policy. If you use GitHub Copilot, check the usage-based billing documentation at Models and pricing for GitHub Copilot to understand how these models will affect costs.</description>
    </item>
    <item>
      <title>GitHub Copilot activity now streams to Microsoft Agent 365</title>
      <link>https://radar.trulysovereign.com/items/5e80194e-455d-46a3-9772-6dc899290ecc</link>
      <guid isPermaLink="false">5e80194e-455d-46a3-9772-6dc899290ecc</guid>
      <pubDate>Tue, 17 Nov 2026 20:58:03 GMT</pubDate>
      <category>verify_only</category>
      <source url="https://github.blog/changelog/2026-11-17-monitor-github-copilot-activity-through-microsoft-agent-365">GitHub Copilot changelog</source>
      <description>GitHub Enterprise Cloud with Enterprise Managed Users can now stream Copilot agent activity—including prompts, responses, tool calls, and usage across all Copilot clients (GitHub.com, CLI, VS Code, Visual Studio, JetBrains, Eclipse)—directly into Microsoft Agent 365 for centralized audit and review alongside other AI workloads.

Why it matters: Organizations using both GitHub Copilot and Microsoft's agent control plane can now consolidate audit data in one location and access risk analysis through Microsoft Purview and Defender, rather than reviewing Copilot activity separately.

What to do: If you are a GitHub Enterprise Cloud customer with Enterprise Managed Users and use Microsoft Agent 365, review the streaming audit log documentation on GitHub Docs to determine whether to enable this integration for your compliance or monitoring workflows.</description>
    </item>
    <item>
      <title>GitHub Copilot Fusion adds three models across tiers</title>
      <link>https://radar.trulysovereign.com/items/31f42bff-fac7-443c-9078-666d59e0e6aa</link>
      <guid isPermaLink="false">31f42bff-fac7-443c-9078-666d59e0e6aa</guid>
      <pubDate>Tue, 17 Nov 2026 20:57:55 GMT</pubDate>
      <category>verify_only</category>
      <source url="https://github.blog/changelog/2026-11-17-github-copilot-fusion-updates-more-availability-benchmarks-and-models">GitHub Copilot changelog</source>
      <description>GitHub added Claude Sonnet 5.5 to Copilot Fusion Max, GPT-6.1 Terra to Copilot Fusion High, and MAI-Code-2 to Copilot Fusion Standard. Copilot Fusion is now available on github.com, Visual Studio, and GitHub Mobile beta apps for iOS and Android, with production mobile app support coming later. Copilot Fusion Max achieved 71.2% on Terminal-Bench 4.1, 5.4 percentage points ahead of Opus 5.5 and Fable 5.2.

Why it matters: If you use Copilot Fusion, the model routing logic now includes different models at each tier, which may change response characteristics, latency, or cost for existing workflows. The web and Visual Studio availability means Fusion is no longer limited to specific editor integrations.

What to do: Test Copilot Fusion in your current development environment to confirm the new model routing produces acceptable results for your use cases. Check whether the model picker now appears in surfaces where you previously could not select Fusion.</description>
    </item>
    <item>
      <title>GitHub Copilot CLI adds Microsoft Entra authentication in preview</title>
      <link>https://radar.trulysovereign.com/items/a6b67c4f-eb09-4b74-98aa-b94bfd241200</link>
      <guid isPermaLink="false">a6b67c4f-eb09-4b74-98aa-b94bfd241200</guid>
      <pubDate>Tue, 17 Nov 2026 20:57:37 GMT</pubDate>
      <category>verify_only</category>
      <source url="https://github.blog/changelog/2026-11-17-github-copilot-cli-adds-microsoft-entra-sign-in-as-a-preview">GitHub Copilot changelog</source>
      <description>GitHub Copilot CLI now supports Microsoft Entra authentication in public preview on Windows and macOS (Linux support pending). This enables two distinct modes: (1) silent SSO for GitHub Enterprise Managed Users via OIDC, using GitHub inference and existing Copilot Business/Enterprise licenses, and (2) direct access using Microsoft 365 Copilot licenses with usage-based billing, using Microsoft 365 inference instead of GitHub inference. Minimum version 1.0.113 is required.

Why it matters: Organizations using EMU with OIDC will see authentication flow changes—users authenticate via Microsoft Entra instead of GitHub directly. Organizations with Microsoft 365 Copilot licenses and usage-based billing now have an alternative inference path with different billing and model access governed by Microsoft 365 settings rather than GitHub Copilot plans. The inference backend and billing model differ depending on which authentication path is used.

What to do: If your organization uses GitHub EMU with OIDC or has Microsoft 365 Copilot licenses, update to GitHub Copilot CLI version 1.0.113 or later by running `copilot update`. Review the GitHub Copilot CLI documentation to determine which authentication mode applies to your setup and verify that the correct inference path and billing model are in effect.</description>
    </item>
    <item>
      <title>GitHub Copilot app adds Azure DevOps and GHES support, browser use preview</title>
      <link>https://radar.trulysovereign.com/items/451804f4-bf4c-4dab-852a-5063ebec2741</link>
      <guid isPermaLink="false">451804f4-bf4c-4dab-852a-5063ebec2741</guid>
      <pubDate>Tue, 17 Nov 2026 20:57:25 GMT</pubDate>
      <category>verify_only</category>
      <source url="https://github.blog/changelog/2026-11-17-github-copilot-app-microsoft-ignite-releases">GitHub Copilot changelog</source>
      <description>GitHub Copilot app now supports Azure DevOps repositories and GitHub Enterprise Server accounts, both requiring manual account setup in Settings &gt; Accounts. Browser use entered public preview for Chromium-based browsers (Chrome, Edge) via a new extension, off by default. GHES support moved from opt-in preview to generally available in version 1.2.0 or later. Cloud sessions are unavailable for both Azure DevOps and GHES repositories.

Why it matters: Teams using Azure DevOps or self-hosted GitHub Enterprise Server can now use Copilot app features (agent branching, PR creation, CI fix automation) that were previously GitHub.com-only. Browser use enables form filling and web app testing in authenticated browser contexts, but requires explicit opt-in and extension installation. The cloud sessions limitation means these repositories cannot use certain Copilot features that depend on cloud execution.

What to do: If your team uses Azure DevOps: open Settings &gt; Experimental, enable Azure DevOps integration, then add your Microsoft account under Accounts. If using GHES: update to Copilot app 1.2.0+, then add your GHES account under Settings &gt; Accounts. For browser use: install the GitHub Copilot extension for Chrome/Edge, then enable both Computer Use and Browser Use in Settings &gt; Computer Use.</description>
    </item>
    <item>
      <title>GitHub Copilot code review adds adaptive effort selection in public preview</title>
      <link>https://radar.trulysovereign.com/items/83d46dfe-1337-4c0b-8255-ec2f5e3d47a1</link>
      <guid isPermaLink="false">83d46dfe-1337-4c0b-8255-ec2f5e3d47a1</guid>
      <pubDate>Tue, 17 Nov 2026 20:57:13 GMT</pubDate>
      <category>verify_only</category>
      <source url="https://github.blog/changelog/2026-11-17-copilot-code-review-adaptive-effort-secret-detection-and-more">GitHub Copilot changelog</source>
      <description>GitHub Copilot code review now offers Adaptive effort level selection in public preview, which automatically chooses Lite, Balanced, or Max review depth based on each pull request's complexity and risk. Previously, users had to manually select the effort level in settings or when requesting a review. Adaptive can be set as the default in personal, repository, organization, or enterprise settings, and respects configured maximum effort level constraints. Also in public preview: cross-repository context for public repositories, secret detection using both deterministic (500+ known formats) and AI/ML methods, and repository insights tracking. Copilot code review for Azure DevOps moved from public preview to generally available, with usage billed in GitHub AI credits to the linked Azure subscription.

Why it matters: Teams currently setting review effort levels manually for each pull request or using a single default for all changes can now have the system match review depth to actual risk. This affects review coverage: routine changes get faster feedback, and high-risk changes get deeper analysis without manual triage. For Azure DevOps users, general availability means the feature is production-ready and billing now flows through Azure subscriptions rather than GitHub directly.

What to do: If you use Copilot code review, test Adaptive on a sample of pull requests to verify it selects appropriate effort levels for your codebase's risk profile. Check that your configured maximum review effort level allows Adaptive to choose the range you want. For Azure DevOps organizations, confirm your Azure subscription is linked and review GitHub AI credit charges in Azure Cost Management.</description>
    </item>
    <item>
      <title>GitHub Copilot for JetBrains ends support for IDE 2025.2</title>
      <link>https://radar.trulysovereign.com/items/06e88857-96ac-4ed7-bea2-05896fccde08</link>
      <guid isPermaLink="false">06e88857-96ac-4ed7-bea2-05896fccde08</guid>
      <pubDate>Tue, 17 Nov 2026 20:56:59 GMT</pubDate>
      <category>migrate</category>
      <source url="https://github.blog/changelog/2026-11-17-github-copilot-in-jetbrains-ignite-releases">GitHub Copilot changelog</source>
      <description>GitHub Copilot for JetBrains no longer supports JetBrains IDE version 2025.2. Users must upgrade to IDE version 2025.3 or later to continue receiving Copilot updates. GitHub recommends version 2026.2 or later. Additionally, enterprise-managed settings now disable Claude and Codex by default unless an administrator policy allows an exception.

Why it matters: Teams running JetBrains IDE 2025.2 will stop receiving Copilot updates, including security fixes and compatibility patches. Enterprise users who relied on Claude or Codex models will find them disabled unless their administrator explicitly enables them, potentially breaking existing workflows that depend on those specific models.

What to do: Upgrade JetBrains IDE to version 2025.3 or later. If you use Claude or Codex models in an enterprise-managed environment, verify with your administrator that these providers are enabled in the policy settings, or adjust workflows to use other available models.</description>
    </item>
    <item>
      <title>GitHub Copilot adds strictPluginOnlyCustomization setting for five customization types</title>
      <link>https://radar.trulysovereign.com/items/088a3ef0-ffb1-40f0-a05b-a5c9c738104a</link>
      <guid isPermaLink="false">088a3ef0-ffb1-40f0-a05b-a5c9c738104a</guid>
      <pubDate>Tue, 17 Nov 2026 07:55:52 GMT</pubDate>
      <category>verify_only</category>
      <source url="https://github.blog/changelog/2026-11-16-control-where-github-copilot-customizations-come-from">GitHub Copilot changelog</source>
      <description>GitHub Enterprise Cloud administrators can now enable a strictPluginOnlyCustomization managed setting that blocks standalone user and project customizations while allowing plugin-sourced and managed-settings-sourced customizations. The setting applies to five categories: skills, custom agents, hooks, MCP servers, and executable Copilot extensions. It can be applied to all categories or selected individually. Available for Copilot Business and Copilot Enterprise licenses.

Why it matters: Teams using standalone MCP server configurations, custom hooks, or executable extensions in user or project settings will lose access to those customizations when an administrator enables this restriction. Approved customizations must be redistributed through plugins or managed settings to remain available.

What to do: Audit current Copilot customizations in user and project configurations across the five categories. Identify which ones are business-critical and coordinate with enterprise administrators to either distribute them through approved plugins or add them to managed settings before the restriction is enabled.</description>
    </item>
  </channel>
</rss>
