Field noteNov 14, 20265 min read1 source

GitHub Copilot weekly notes add JetBrains Air, Xcode preview, and app merge tools

In one minute

GitHub’s November 6 Copilot changelog bundles updates across its app, CLI, JetBrains, Xcode and VS Code. The additions extend agent work across IDEs and sessions, add pull-request merge handling, and make local automations more configurable—practical changes for teams already building around Copilot.

What changed: GitHub’s November 2 weekly update adds Copilot in JetBrains Air and Xcode, alongside new app and CLI tools for managing agent sessions, pull-request merges, and settings.

What happened

GitHub’s announcement, dated November 6, 2026, covers weekly releases beginning November 2. In JetBrains, Copilot is now available in JetBrains Air. Users can track multiple agent sessions and run tasks locally in a JetBrains IDE or in the cloud through Air Teams, using an existing Copilot subscription. GitHub also says Copilot can now be used directly in Xcode’s built-in coding assistant. That integration is a public preview starting with Xcode 27.3 beta.

The Copilot app update adds controls around pull requests and sessions. Users can set up Agent Merge directly from a pull request; it remains enabled while required checks or rules are pending. The app can show reviewer status, request additional reviews and let users quote selected review comments to discuss them with Copilot. This makes the pull request a place to configure a pending merge operation rather than only a record of review activity.

When a conversation reaches its context limit, users can compact it or inspect what is using the available space. GitHub also adds a way to begin a session by dropping files on “New” in the sidebar. CSV and TSV files open as tables with sticky headers and an option to view their source. Session-management changes include archiving pinned sessions whose pull requests have merged or closed, pinning or unpinning multiple sessions, and separating nested chats without losing the conversation. My Work now supports more than ten saved custom views.

Personal instructions for assisted approval can guide which tool requests Copilot approves without asking. GitHub says the feature is opt-in and applies to local sessions. The changelog does not characterize it as a cloud-session capability. That scope matters because it places the approval setting alongside a developer’s local work rather than presenting it as a general unattended-execution policy.

For Copilot CLI, /settings opens a unified dashboard for plugins, MCP servers and other settings, with search across settings. In VS Code release 1.145, experimental chat modes allow users to collapse or expand reasoning and tool calls without starting a new conversation. Remote apps and interactive canvases in the Agents window are in preview; remote browser support and canvases must be enabled in settings. Local automations now support cron expressions and custom agents from the workspace. Users can add files as context without moving them into the workspace, although cloud sessions support images only. GitHub’s changelog does not state a new price for these updates.

What the archive adds

New Runtime’s earlier coverage described Copilot Automations as persistent, team-shared workflows with repository visibility and owner-billed AI credits (GitHub launches shared Copilot Automations, November 12, 2026). This weekly release is a new event, not a restatement: its emphasis is IDE access, session management and local automation controls.

Trend signal

This update supports the shift toward a more durable harness around model choice: Copilot’s operational surface spans IDEs, local and cloud sessions, CLI settings, pull requests and scheduled automation. The announcement does not establish how widely teams use these features or whether they improve delivery outcomes. It is a modest example of the broader pattern, not proof of its economic impact (Harness architecture outlives model choice).

Why now

The release is a weekly bundle dated November 6, rather than a change tied to a stated deadline or a new pricing or access policy. The changelog explains where the features are rolling out, but does not give a broader reason for their timing.

Why it matters

For teams using Copilot across different developer environments, these changes reduce some friction in moving between agent sessions and managing their outputs. JetBrains Air extends the workflow to local and cloud task execution; the Xcode preview puts Copilot into Apple’s native coding assistant. Pull-request-based Agent Merge can keep a merge operation in place while checks or rules are still pending, while the CLI dashboard brings plugin and MCP configuration together.

The local-automation update is especially operational: cron expressions can make recurring work explicit, while workspace custom agents allow that work to use agents defined with the project. The ability to inspect reasoning and tool calls in VS Code also gives developers a choice between a condensed conversation view and a fuller execution trace.

The practical boundary is important: these are product-specific features, not a single uniform capability. Xcode remains a preview, remote apps and canvases in VS Code are also previews, and assisted approval applies to local sessions. Teams should verify which controls are enabled in their environment before relying on them for unattended work.

Limits and uncertainty

GitHub’s announcement describes feature behavior but provides no adoption figures, productivity measurements or evidence that these changes reduce review time or defects. It does not specify rollout timing beyond the stated preview status and version references, nor does it disclose whether every feature is enabled for all Copilot plans. The Xcode integration is a public preview for Xcode 27.3 beta, and VS Code’s remote apps and canvases are previews. GitHub also does not explain the security model for assisted tool approval or remote app access in this changelog.

Reader takeaway

Copilot’s updates make agent sessions more manageable across several development environments, but the capabilities and maturity differ by product. Check the specific IDE or client release you use, and treat preview features and local-only approval behavior as distinct from generally available, cross-environment controls.

Evidence / sources

  1. 1github.blog/changelog/2026-11-06-github-copilot-weekly-releases-november-2
All Field Notes

Next reads

Read next

Open the graph
  1. 01topicGithubExplore the github topic hub.
  2. 02archiveField NotesOpen the latest editorial analysis.
  3. 03sourcesSourcesSee the original sources this archive cites.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract