AI, in your work.

GitHub's November 2 weekly roundup, published on November 6, covers access to Copilot across more environments and pull request (PR) tracking. Requirements and capabilities differ between integrations.

Xcode: public preview

According to the November 4 announcement, Copilot integrates with Xcode's built-in coding assistant in public preview starting with Xcode 27.3 beta. It requires a Mac running macOS Tahoe 26.6 or later and is configured under Xcode > Settings > Intelligence. GitHub states that all Copilot plans are supported. The Copilot for Xcode extension remains a separate option.

Air: local and cloud requirements

GitHub's announcement allows an existing Copilot subscription to be used in Air. Local work requires installing Air in a JetBrains IDE and connecting the account. Cloud work requires a JetBrains account in a business organization with Air Teams and Copilot enabled by its administrator. The announcement does not list eligible plans.

Usage is charged to Copilot rather than JetBrains AI credits. Air's analytics do not include that usage; users also cannot choose a personal or organizational plan per task or set Copilot spending limits within Air.

Microsoft's comparison distinguishes Air from the Copilot plugin: Air does not include some plugin features, such as Copilot Code Review and Enterprise Managed Settings. Next Edit Suggestions with Copilot in Air require a JetBrains IDE version 2026.2.4 or later.

Agent Merge: keeping track of a PR

The weekly roundup adds the ability to configure Agent Merge from a PR in the Copilot app and keep it enabled while required checks or rules are pending. The app documentation explains that it can resolve blockers and merge when GitHub allows; it can also address review comments.

The app is available for all Copilot plans, but Business and Enterprise users need the GitHub Copilot app policy to remain enabled. That policy is independent of the Copilot CLI policy.

Agent Merge on GitHub requires a paid plan, permitted access to Copilot in the cloud, and the repository's automations policy enabled. It does not support PRs from forks or stacked PRs. It fixes failed Actions workflows or conflicts; auto-merge is enabled separately. Credits are charged to the person who enables it. Required reviews and checks remain mandatory.

Nexo's interpretation: choosing an environment and retaining control

These updates expand the options for fitting an agent into a team's work. Our interpretation is that each workflow should be evaluated separately: what context it receives, who follows the session, and what review the repository requires. The announcements do not demonstrate identical continuity across applications or improved productivity.

Hypothetical example: a small change from start to finish

In a test repository, a team could ask for a search filter to ignore letter case. This scenario provides a structure for an evaluation without attributing results to any tool:

• Choose Xcode or Air according to the project and check access requirements before starting the task.
• Describe the expected behavior and prepare test cases: “Madrid” and “madrid” should return the same results.
• Review the PR's changes and tests. If Agent Merge is enabled, define its permitted actions and retain the required reviews.

Nexo has not run this exercise. Comparing environments would require recording errors, review time, and usage under equivalent conditions.