JetBrains IDEs get Claude agent preview and enhanced GitHub Copilot features

Every quarter, an IDE upgrade claims to change your workflow. Most don't. The June 2026 Copilot release for JetBrains IDEs is the exception: organization agents, Claude as an agent provider, per-turn credits, queuable CLI input, and a more capable model picker — shipped together, according to the official GitHub changelog. For teams scaling AI-assisted development, this is the release where sandboxed assistants start becoming governed workflow.

Here is what each announced feature does, how to use it, and where the real value lands — all grounded in the changelog itself.

What shipped in the June 2026 Copilot release for JetBrains

The changelog describes a dense slate: support for organization- and enterprise-level agents, the ability to queue and steer messages in Copilot CLI sessions, a new agent debug logs summary view, Claude as an agent provider in public preview, model picker enhancements, a per-turn AI credits indicator, and Cloud agent reaching general availability — plus the usual round of user experience and reliability improvements.

Each item answers a specific, known pain: CLI sessions that blocked on input, agent debugging scattered across raw logs, team standardization done by copy-pasted YAML, and model choice locked behind defaults. For once, the changelog maps cleanly onto real breakdowns.

How organization and enterprise agents work in JetBrains IDEs

Admins can now publish custom agents at the GitHub organization or enterprise level, and those agents are automatically distributed to every eligible developer using Copilot in a JetBrains IDE. Per the changelog, the flow is: an admin creates and publishes custom agents in GitHub, developers open the agent picker in the Copilot Chat panel, and the org or enterprise agents appear grouped and ready to select — running with the admin-defined configuration.

The payoff is team-wide consistency without per-user setup drift:

• Standardized workflows: every developer works with the same curated agents, tuned for the team's repos and conventions.
• Centralized governance: capabilities, access scopes, and guardrails are monitored and updated in one place.
• Instant distribution: publishing or upgrading an agent reaches every IDE with no manual configuration.

For onboarding, this is the headline feature. New hires and contractors land in team conventions by default instead of an open playground. If your shop runs on shared standards, define your agents once at the org level — the agent-readable repository structure pattern pairs well here, since curated agents perform best against repos that are already machine-legible.

How to queue and steer messages during Copilot CLI sessions

Long CLI runs used to present a binary choice: wait passively or cancel the agent's work to give new input. The changelog confirms that is over. While a request is in progress, the Send button becomes a dropdown with three options, quoted here from the release notes:

• Add to Queue: queue a message to be processed after the current response completes.
• Steer with Message: tell the current request to yield once the active tool execution finishes, then process your message immediately — redirect the agent without killing its progress.
• Stop and Send: stop the current turn and send the new message at once, for cases where the agent has veered off course.

Where this earns its keep: multistep CLI tasks you can queue without babysitting, mid-run redirection when the agent drifts, and clean interrupts for runaway work instead of hammering cancel and losing history. The operational shift is simple — the CLI is now responsive to you, not the other way around.

Claude as an agent provider: what the public preview means

Anthropic's Claude is available in public preview as an agent provider inside Copilot for JetBrains, selectable from the agent model picker. The Claude Code documentation is the authoritative reference for Claude's coding-agent capabilities.

Why it matters: different models genuinely excel at different work, and Claude's reasoning and summarization strengths make it a meaningfully different engine for agent turns rather than a cosmetic alternative. Public preview means any Copilot JetBrains user can opt in for selected sessions — no private beta process. Practical advice: assign models per task rather than per habit. Run batch and boilerplate work on the default, and reach for Claude on complex migrations, gnarly debugging, and anything where answer quality compounds. If you standardize prompts across the team, keep them as prompts-as-deliverable artifacts so model swaps don't silently change behavior.

Per-turn credits and the model picker: cost transparency arrives

The model picker now gives session-by-session control over which model powers an agent run, and the per-turn AI credits indicator shows resource consumption at the granularity of each interaction. Three consequences follow:

• Informed choice: pick a cheaper model for batch scripts and a stronger one for the migration that matters.
• Cost clarity: credits per turn make budgeting possible across hundreds of developers instead of guessing what long sessions burn.
• Debuggability: when a session suddenly costs more, the indicator shows which model and turn were responsible.

Transparent costs plus real-time control are prerequisites for serious org-wide adoption. For teams tracking AI spend, this is the release that makes chargebacks and budgets feasible — worth pairing with explicit rules your agents actually follow so cheap models stay on rails.

Reliability and usability: debug summaries and Cloud agent GA

The Agent Debug panel gains a summary view aggregating session activity instead of forcing developers to trawl raw logs — faster troubleshooting and easier cross-session comparison. GitHub's Cloud agent exits beta into general availability, which the changelog frames as the durable backend for agent-centric workflows at org scale. The remainder is the standard reliability pass: UX fixes and defect repair driven by live feedback. None of these headline alone; together they are what trust is made of.

What to adopt this week

• Publish one org-level agent with admin privileges covering your most repeated workflow.
• During your next long CLI run, use the Send dropdown instead of waiting or cancelling.
• Opt into Claude in the model picker for one complex task and compare answer quality directly.
• Watch the per-turn credits indicator for a day, then set a team budget baseline.
• After your next tangled session, open the Agent Debug summary before touching raw logs.

The boundaries beneath this release — org-driven governance, explicit per-turn costs, interruptible multitasking — are the new table stakes for AI-integrated development. If your codebase is already agent-legible and your path to production is short, each Copilot upgrade compounds. OTF kits keep that path short: full-stack templates your agent can ship without a rewrite step. Start from a kit that ships.

Sources

• New features and Claude as agent provider preview in JetBrains IDEs — GitHub changelog, June 22, 2026: org/enterprise agents, CLI queue and steer, debug logs summary, Claude public preview, model picker, per-turn credits, Cloud agent GA.
• Claude Code documentation overview — Anthropic's reference for Claude's coding-agent capabilities.
• Agent-readable repository structure — repos that curated agents perform best against.
• Cursor rules that actually work — keeping models on rails across swaps.
• Ship your AI MVP to production checklist — the short path from agent output to prod.