Opening Your Own IDE's Door to a Rival's Agent — Android Studio Welcomes Claude and Codex via the Shared ACP Standard, "On Your Own Subscription"

Google has added a mechanism to its own integrated development environment, Android Studio, that lets you plug in third-party coding agents as-is. Named "Bring Your Own Agent" (BYOA), the feature was released as a preview on September 24, 2026, in the canary (early-access) channel of the upcoming "Rabbit 2" release. Users can pick their favorite from options such as Anthropic's Claude Agent, OpenAI's Codex, and Google's own Antigravity, and run it inside Android Studio on the subscription they already use.

The key is "a shared socket that fits any editor"

What underpins BYOA is an agreement called the Agent Client Protocol (ACP). This is an open standard that unifies the conventions for how the editor side and the agent side communicate. Zed, the editor's developer, released it under the Apache license in August 2025 and has been developing it jointly with JetBrains and others. Built on the same idea by which the Language Server Protocol (LSP) once bundled code completion and go-to-definition across languages into a single convention, ACP aims for a state where "any agent can be called from any IDE." More than 25 agents, led by JetBrains, Google, and GitHub, have already announced support, and Android Studio's adoption means Google itself has joined that trend.

For developers, the change is that choosing a tool is no longer a matter of "switching your entire IDE." Until now there were situations where you had to move to a dedicated editor just to use a particular agent, but as long as things follow ACP, you can swap out only the agent inside while staying in the Android Studio you're used to. Just as MCP (the shared standard for connecting external tools) that Anthropic popularized spread across companies, the center of gravity around agents is shifting from "lock-in" toward "shared standards."

The "local knowledge" the IDE hands to the agent

This is not merely placing a chat window. Android Studio hands the external agent the clues and operational authority it needs for development. According to the published information, the main things shared are as follows.

• The big picture of the project: the project graph including dependencies, build configuration, and information about target platforms
• Build and verification: build diagnostics, running tests, and passing along error details
• Android-specific tooling: Jetpack Compose previews, Android SDK tools, and emulator control
• A foundation of conventions: a collection of Android-oriented skills and a knowledge base summarizing the latest recommended practices
• Execution permissions: reading, writing, and editing files; running shell commands; web search; and delegation to sub-agents

Google describes this as "combining your favorite agent with the IDE's unique local knowledge." The claim is that, because the agent can work while taking into account build settings and screen previews that are hard to pick up on its own, the work becomes faster, more accurate, and easier on costs. Fine-grained permission settings are also provided, such as requesting approval for high-risk operations while leaving routine work to the agent.

A billing model of "borrow the brains, but keep the contract your own"

Another thing to grasp is payment. Rather than Google covering the model-usage fees in bulk, BYOA takes the form of each person signing in and using their own contract. Pricing is decided by each agent's provider, and both corporate and individual plans are supported. The main combinations are as follows.

Because you can use your existing subscription as-is, you can bring the agent you already have into your main development environment without piling on a separate charge. On the other hand, Google is being generous with usage allowances for its own Antigravity, so the dynamic of welcoming rival agents while pushing its in-house product remains.

What it means from the field and from management

There are two implications for companies. One is freedom of choice. The relative merits of models and agents shuffle on a timescale of months, but if you can swap only the agent while keeping the IDE fixed, you can keep using "the best thing right now" while holding down switching costs and learning costs. It points in the direction of loosening lock-in to a specific vendor.

The other is ease of procurement. You can apply the AI plan your whole company already has under contract to Android development as-is, without having to raise a new approval request for each tool. By widening the door to Android's enormous developer base with a "use whichever agent you like," Google has created a distribution channel that each agent provider cannot ignore either.

Points that aren't all welcome

Behind the convenience, there are also issues worth pausing to check.

• Not yet a stable release: it is offered only as a preview on the canary (early-access) channel, so it is premature to put it into production.
• Context that goes outside: the project graph, source code, and build information flow to the infrastructure of the chosen third-party agent. The question of which providers to trust and what may be handed over is risky to leave to individual developers; information governance boundaries need to be decided at the organizational level.
• The center of gravity of a socket that looks neutral: even though ACP itself is an open standard, Google favors its own Antigravity with usage allowances. It pays to keep in mind that the default center of gravity of an entryway that "takes anything" tends to tilt toward the provider.

That said, the move to consolidate the connection between agents and editors onto a single open standard works in the direction of widening users' choices. By the time Android Studio makes this standard in a stable release, an era in which each company freely rearranges "which IDE, which agent, and on whose contract" should have come one step closer.

References: Android Developers Blog, "Build your way: Use any AI agent of your choice in Android Studio" / Mixed News, "Android Studio now runs Anthropic's Claude Agent and OpenAI's Codex, in canary" / Zed, "Agent Client Protocol" / JetBrains, "Agent Client Protocol (ACP)"