Microsoft says Copilot agent mode is generally available in the Visual Studio June update. The feature can plan a multi-step task, edit code, run commands, react to build or lint failures, and keep a visible action feed for review.

MCP support is the important interoperability change. Visual Studio can use mcp.json configuration and compatible servers so agents can reach tools such as repositories, CI/CD systems, telemetry, or design context without bespoke integrations for every service.

Field|Current evidence
Primary source|Microsoft: Agent mode is now generally available with MCP support
Source date|2025-06-23
Update scope|Visual Studio agent mode, MCP configuration, tool calling, and editable review controls
Verification note|Official source only; no search-result scraping, no ranking guarantee, no uncited claims

The useful change is that agent mode is tied to the IDE's own tools instead of only a chat transcript. Visual Studio can let Copilot inspect code, apply edits, run commands, and respond to failures while keeping previews, undo, and action feeds visible to the developer.

Teams using Visual Studio should test agent mode against real build errors and repository workflows, then decide which MCP servers are allowed. The biggest risk is over-connecting tools before permission, logging, and data-boundary expectations are clear.

This update matters most for Microsoft-stack teams that want agent workflows inside Visual Studio. Teams already standardized on VS Code or web-based agents should compare the governance model rather than treating GA as an automatic migration trigger.

Limits and open questions: the post is about Visual Studio's June update and does not guarantee identical behavior across every workload, extension, or MCP server. Security and productivity claims need local validation. Source handling note: KyenAI records the publisher, publication date, and source URL on the page, then keeps the update date tied to evidence-backed edits rather than automatic refreshes. When source material is thin, the system keeps interpretation narrow and waits for stronger documentation. Editorial review compares the new claim against the article summary, fact table, internal links, and listed source before allowing another optimization pass. Search outcomes are measured after publication rather than assumed at writing time.

Microsoft's Visual Studio June update makes Copilot agent mode generally available with MCP support for external tools and richer development context.

Agent mode is now generally available with MCP support

Visual Studio Agent Mode Adds General Availability and MCP Support

GitHub Copilot CLI now has a refreshed terminal surface and a rubber duck agent that can critique plans, implementation, or tests before the main agent continues.

Prompt scheduling with /every and /after points toward terminal agents that keep checking builds, usage, or repo state over time. Voice input is local, which matters for teams evaluating privacy and developer ergonomics.

Field|Current evidence
Primary source|GitHub: Copilot CLI: Improved UI, rubber duck, prompt scheduling, and voice input
Source date|2026-06-02
Update scope|terminal agent review, scheduled prompts, local voice input, and CLI ergonomics
Verification note|Official source only; no search-result scraping, no ranking guarantee, no uncited claims

The notable change is the critic agent inside a terminal workflow. Rubber duck review creates a second pass before the main agent continues, which can catch weak plans, missing tests, or risky implementation shortcuts. Scheduled prompts also move CLI agents toward monitoring work, not only answering one command at a time.

For teams, the first evaluation should be operational rather than theatrical: schedule a build check, ask the critic to review a migration plan, and inspect whether the CLI produces auditable output. Voice input is useful only if it fits the team's privacy, accessibility, and workstation norms.

This update is strongest for developers who prefer terminal-first workflows. It is less decisive for organizations that need centralized review logs, because prompt scheduling and critic behavior still need policy and retention boundaries.

Limits and open questions: the source does not prove reliability across shells, operating systems, or private repositories. Claims about productivity gains should wait for measured before-and-after data from real teams. Source handling note: KyenAI records the publisher, publication date, and source URL on the page, then keeps the update date tied to evidence-backed edits rather than automatic refreshes. When source material is thin, the system keeps interpretation narrow and waits for stronger documentation. Editorial review compares the new claim against the article summary, fact table, internal links, and listed source before allowing another optimization pass. Search outcomes are measured after publication rather than assumed at writing time.

GitHub's Copilot CLI refresh adds a redesigned terminal experience, a critic agent, scheduled prompts, and local voice input.

Copilot CLI: Improved UI, rubber duck, prompt scheduling, and voice input

Copilot CLI Adds Rubber Duck Review, Prompt Scheduling, and Voice Input

Google's Antigravity CLI announcement frames the migration as a move from a terminal assistant to a unified agent-first platform. The new CLI keeps critical Gemini CLI features such as Agent Skills, Hooks, Subagents, and Extensions as Antigravity plugins.

The important timeline is operational: individual and free Gemini CLI and Gemini Code Assist users need to transition before June 18, 2026, while enterprise access remains under paid Google Cloud and Gemini Enterprise arrangements.

Field|Current evidence
Primary source|Google: An important update: Transitioning Gemini CLI to Antigravity CLI
Source date|2026-05-19
Update scope|Gemini CLI migration path, Antigravity plugins, and multi-agent execution
Verification note|Official source only; no search-result scraping, no ranking guarantee, no uncited claims

The useful signal is the migration deadline and plugin continuity. Google is positioning Antigravity CLI as the agent-first successor while preserving important Gemini CLI concepts such as Skills, Hooks, Subagents, and Extensions. That gives teams a concrete checklist instead of a vague platform announcement.

Teams using Gemini CLI should audit scripts, extensions, account type, and access path before the transition date. The migration work is not only installing a new CLI; it includes confirming plugin behavior, enterprise eligibility, and how asynchronous agents are monitored.

This update is a planning trigger for teams with Gemini CLI in developer workflows. If the CLI is experimental, the team can wait; if it is part of internal automation, migration testing should happen before deadline pressure appears.

Limits and open questions: the source does not prove parity for every extension, nor does it describe every enterprise billing path. The article should keep those as open items until Google publishes detailed migration notes. Source handling note: KyenAI records the publisher, publication date, and source URL on the page, then keeps the update date tied to evidence-backed edits rather than automatic refreshes. When source material is thin, the system keeps interpretation narrow and waits for stronger documentation. Editorial review compares the new claim against the article summary, fact table, internal links, and listed source before allowing another optimization pass. Search outcomes are measured after publication rather than assumed at writing time.

Google is unifying Gemini CLI and Code Assist workflows into Antigravity CLI, an agent-first platform with asynchronous multi-agent execution.

An important update: Transitioning Gemini CLI to Antigravity CLI

Google Moves Gemini CLI Users toward Antigravity CLI

If you cannot write the desired outcome clearly, stay in chat mode and clarify the task first.

Write the task in one sentence

Tell the agent which files, folders, or modules it may inspect and edit.

Name the allowed area

Add the test, build, or manual check that proves the change worked.

Give the proof command

Agent mode can move faster than your attention, so read the changed files before merging.

Review the final diff

Chat mode and agent mode decision tree

VS Code agent mode

GitHub Copilot coding agent

Compare agent mode vs chat mode by file edits, terminal commands, network risk, token cost, safe use cases, and stop rules.

Agent Mode vs Chat Mode: Risks and Use Cases

Using agent mode for unclear work

Letting the agent decide the scope

Treating a passing command as full review

Use chat mode for questions and small explanations. Use agent mode when the assistant must inspect files, edit code, run commands, react to errors, and bring a task closer to done.

Agent Mode vs Chat Mode: Differences, Risks and When to Use Each

Capture commands, scripts, docs, CI references, auth assumptions, and plugin or extension usage before editing anything.

Freeze current Gemini CLI usage

For every recurring workflow, write the Antigravity CLI equivalent and mark unresolved behavior differences.

Map each workflow

Move one repository or one workflow first, verify auth and hooks, then update docs before expanding to the team.

Run a small migration test

Keep a dated change log on the page so users can see what changed after the migration article was first published.

Monitor official updates

Gemini CLI to Antigravity CLI migration map

Transitioning Gemini CLI to Antigravity CLI

Antigravity CLI migration documentation

Checklist for migrating from Gemini CLI to Antigravity CLI, including commands, auth, hooks, extensions, and team docs.

Antigravity CLI Migration from Gemini CLI

Renaming commands without testing workflow behavior

Ignoring old docs and onboarding paths

Letting a time-sensitive page age silently

A migration checklist for Gemini CLI users moving to Antigravity CLI, with the key dates, retained concepts, and verification steps.

Antigravity CLI migration from Gemini CLI

Describe which action should happen automatically, which action needs a tool, and which action must stay human-approved.

Write the workflow boundary

Add MCP servers and hooks with the smallest useful permission set so failures are observable without being destructive.

Install read-only first

For each hook and MCP tool, write what happens when it times out, fails, returns empty data, or lacks credentials.

Document failure behavior

Only widen permissions after the workflow has completed successfully on a small project and the owner agrees with the logs.

Promote after proof

Record the expected working directory, required binaries, credentials, timeout behavior, and rollback command before teammates copy the setup.

Add a troubleshooting note

Hooks, MCP, and skills control map

Claude Code hooks

Claude Code MCP

Model Context Protocol

Compare Claude Code hooks, skills, and MCP with setup examples, hook-to-MCP boundaries, logs, troubleshooting, and security checks.

Claude Code Hooks vs MCP Setup

Using MCP for deterministic local steps

Adding write access too early

No rollback path

A setup-oriented guide for combining Claude Code hooks, skills, and MCP servers without creating brittle automation.

IDE & CLI

Evidence updates

Visual Studio Agent Mode Adds General Availability and MCP Support

Copilot CLI Adds Rubber Duck Review, Prompt Scheduling, and Voice Input

Google Moves Gemini CLI Users toward Antigravity CLI

IDE & CLI

Core guides

Agent Mode vs Chat Mode: Differences, Risks and When to Use Each

Antigravity CLI migration from Gemini CLI

Claude Code Hooks vs MCP: Setup, Examples and Security

Evidence updates

Visual Studio Agent Mode Adds General Availability and MCP Support

Copilot CLI Adds Rubber Duck Review, Prompt Scheduling, and Voice Input

Google Moves Gemini CLI Users toward Antigravity CLI