Products & Toolsai developer toolscopilotgithub copilotjetbrains

JetBrains Makes GitHub Copilot a Native IDE Agent

||By LDS Team
6.0
Relevance Score
JetBrains Makes GitHub Copilot a Native IDE Agent

The AI coding tool stack keeps consolidating: JetBrains and GitHub announced on June 30, 2026, that GitHub Copilot is now a first-class, native agent inside JetBrains AI Assistant, not just a separate plugin or an ACP-registry add-on. For practitioners juggling Copilot, Cursor, Claude Code, and Codex across different editors, this matters because it removes setup friction and signals that IDE vendors are racing to become neutral hosts for multiple competing coding agents rather than picking one horse. Developers can now open the agent picker in JetBrains AI chat, select Copilot as the active agent, choose among supported Copilot models, and tune reasoning depth without configuring anything via the Agent Client Protocol. A separate GitHub Copilot subscription is still required. JetBrains and GitHub say Next Edit Suggestions, reusable Skills, and deeper cross-tool orchestration are coming in future releases, building on commitments made at Microsoft Build.

What happened

JetBrains and GitHub announced a deeper integration on June 30, 2026, that makes GitHub Copilot a first-class, native agent inside JetBrains AI Assistant's agent picker, rather than something developers had to wire up separately through the Agent Client Protocol (ACP) registry or install as a standalone plugin (blog.jetbrains.com, github.blog). Developers open the AI chat, select GitHub Copilot from the agent picker, authenticate via OAuth with their GitHub account, and choose which Copilot model and reasoning depth to use for a given task. Copilot CLI slash commands such as /remote and /chronicle are also now available directly inside JetBrains AI chat.

For practitioners

This is another data point in the rapid consolidation of the AI coding tool stack. Over the past year, Cursor, Claude Code, Codex, and Copilot have gone from walled-off products to interoperable agents that plug into shared protocols like MCP and ACP, and JetBrains has onboarded Cursor, Codex, and now Copilot as native or near-native agent options inside its own IDEs within a matter of months. For engineering teams, that reduces lock-in: the editor becomes a neutral surface for whichever coding agent a developer or team standardizes on, and switching costs between agents drop toward zero. It also pressures IDE-native assistants, including JetBrains' own AI Assistant models, to compete on merit rather than distribution, since Copilot, Cursor, and others are now one click away inside the same editor. One caveat: JetBrains is explicit that this integration does not bundle Copilot access, users need an active, separately-billed GitHub Copilot subscription, so the move expands Copilot's reach without changing Microsoft's monetization of it. It also deepens JetBrains' dependency on third-party agent vendors for its core AI experience, a trade worth watching as GitHub, OpenAI, and Anthropic compete for default-agent status inside IDEs.

What to watch

  • Next Edit Suggestions (NES), which will guide developers through multistep code changes by surfacing the likely next edit.
  • Reusable Skills for common workflows, and deeper orchestration across tools for how Copilot plans and executes complex development tasks.
  • Continued build-out of JetBrains' multi-agent strategy, following Cursor's ACP integration in March 2026 and a Claude agent-provider preview added in June 2026.

Key Points

  • 1JetBrains made GitHub Copilot a native, first-class agent inside JetBrains AI Assistant on June 30, 2026, replacing manual ACP setup.
  • 2The move reflects rapid consolidation of the AI coding stack, as Cursor, Codex, and Copilot all become interoperable IDE agents.
  • 3A separate paid Copilot subscription is still required, and JetBrains plans deeper orchestration, Skills, and Next Edit Suggestions next.

Scoring Rationale

A native Copilot integration inside a major IDE vendor's AI assistant is a meaningful signal of how fast the coding-agent market is standardizing around shared protocols, directly affecting millions of JetBrains developers' daily tool choices. Sourced entirely from official JetBrains/GitHub/Microsoft announcements (no independent press coverage found); scored as a solid incremental product integration rather than a new model or research result.

Sources

Public references used for this report.

3 sources

Practice interview problems based on real data

1,625 SQL & Python problems across 15 industry datasets — the exact type of data you work with.

Try 250 free problems