Android Studio BYOA: Codex, Claude Agent, Antigravity & ACP
QUICK ANSWER
Google announced Bring Your Own Agent (BYOA) for Android Studio on September 24, 2026. The feature is rolling out in preview in Android Studio Rabbit 2 Canary and lets developers connect supported coding agents such as OpenAI Codex, Anthropic Claude Agent and Google Antigravity, plus other Agent Client Protocol (ACP)-compatible agents. Android Studio provides IDE-native project context and can inject Android-specific capabilities such as build diagnostics, Jetpack Compose previews, Android SDK tools and emulator control. Google says agents can read and edit files, run shell commands and tests, search the web, delegate to subagents, preserve project context and use granular permission controls. Treat this as preview software rather than a stable production guarantee: pin the Canary build you are testing, restrict permissions, keep credentials out of prompts and repositories, and preserve a reversible source-control/checkpoint path before allowing an agent to mutate important code or run privileged commands.
You want to use Codex, Claude Agent or Antigravity directly inside Android Studio instead of switching between separate tools
An ACP-compatible coding agent is available but the team is unsure whether Android Studio can connect it
A connected agent can edit files or run commands and the team needs a safer permission and rollback model
Android Studio can see the agent but build, emulator, Compose Preview or Android SDK context is missing or incomplete
A team treats the Canary BYOA preview as if it were a stable generally available Android Studio contract
Possible causes
Android Studio Rabbit 2 Canary introduces a new BYOA integration layer rather than relying only on the built-in Gemini experience
Agent Client Protocol standardizes communication between editors and coding agents, reducing one-off editor-agent integrations
Android Studio can enrich a connected agent with project-graph, build, diagnostic, preview, SDK and emulator context that a standalone chat may not have
Different agent providers have different authentication, quota, privacy and billing models even when they connect through the same IDE surface
Canary and preview features can change faster than stable Android Studio workflows, so configuration drift and compatibility issues are expected
HOW TO FIX IT
Work from the safest step to the harder repair.
Step 1. Confirm the channel and build first. Google's announcement says BYOA is rolling out in preview starting with Android Studio Rabbit 2 Canary. Do not troubleshoot a stable-channel installation as though the preview feature must already exist there.
Step 2. Install the latest compatible Canary build alongside stable Android Studio when possible instead of replacing the only known-good IDE. Google's preview documentation supports side-by-side installation, which makes rollback and comparison easier.
Step 3. Open the Android Studio agent window and use the available agent selector or Settings > Tools > AI > Agents to connect a supported agent. Google names Claude Agent, Codex and Antigravity as featured options and says additional ACP-compatible agents can be connected through the registry.
Step 4. Choose authentication deliberately. Use the provider-supported sign-in or API-key flow shown by the agent integration. Do not paste durable API keys, OAuth tokens, session cookies or enterprise credentials into prompts, project files or screenshots.
Step 5. Verify the permission model before enabling broad automation. Google says agents can read, write and edit files, run shell commands, run tests and search the web, while granular permissions can pause for approval on riskier actions. Start with the narrowest permissions that still complete the task.
Step 6. Test IDE-native context with a harmless task. Ask the agent to explain a Gradle/build issue, inspect a Compose Preview problem or run a bounded test so you can confirm Android Studio is actually providing project and diagnostic context instead of assuming the integration is active.
Step 7. Keep destructive actions reversible. Commit or checkpoint working code before allowing wide refactors, dependency upgrades, manifest changes, signing changes, schema migrations or generated-code rewrites. Review diffs before accepting them.
Step 8. Separate coding-agent access from production authorization. An agent being connected to Android Studio does not mean it should have production cloud credentials, release-signing keys, Play Console access, customer data or unrestricted deployment permissions.
Step 9. If one agent reaches quota or produces weak results, switch agents only after preserving the current working state. Google explicitly describes multi-agent flexibility, but context continuity does not make the agents behaviorally identical.
Step 10. For third-party ACP agents, verify the agent's own privacy, retention, billing and enterprise terms. ACP standardizes editor-agent communication; it does not standardize every provider's data handling or commercial policy.
Step 11. Measure the integration on real engineering outcomes: build success, test pass rate, review defects, latency, token or subscription cost, rollback frequency and human review time. Do not treat provider marketing claims as universal productivity guarantees.
Step 12. Recheck the Android Studio preview notes after Canary upgrades. Because BYOA is a preview feature, agent availability, settings paths, permission behavior and supported tools can change before stable release.
Need the actual code? Go to GenesisCodeDoctor.com to search the Code Store or request code for the exact platform, error, and repair you are working on.
1. Are you on Android Studio Rabbit 2 Canary or another build that explicitly documents BYOA? If no, install or test a supported preview build before diagnosing missing agent controls.
2. Is the desired agent listed directly? If yes, use the native connection flow. If no, verify whether the agent is actually ACP-compatible before attempting a custom integration.
3. Does the task require file or shell mutation? If no, keep the agent read-oriented. If yes, create a checkpoint and grant only the permissions needed for the bounded task.
4. Does the agent need production credentials or destructive access? If yes, stop and redesign the workflow around scoped tooling, approval and auditability before proceeding.
5. Did the agent change code? If yes, review the diff, run tests and verify the Android build/emulator behavior before accepting or publishing the change.
6. Did a Canary update change behavior? If yes, recheck current preview notes and agent-provider documentation before assuming the project itself regressed.
REPAIR FLOW
A visual path from symptom to verified production.
Observe→
Protect→
Isolate→
Repair→
Test→
Publish→
Verify live
BEFORE YOU PASTE CODE
Protect the working site first.
Use source control or an equivalent checkpoint before broad agent edits and inspect the diff before merge or publish.
Keep release signing, Play Console, production cloud and customer-data credentials outside the agent unless a narrowly scoped approved workflow genuinely requires them.
Prefer least-privilege command and filesystem permissions; require explicit approval for package installation, shell commands with side effects, network mutation, deployment and credential changes.
Run typecheck, unit/instrumentation tests and a representative emulator/device flow after agent-generated Android changes rather than treating a successful edit as proof of correctness.
STOP AND GET HELP WHEN
Do not turn a repair into a larger outage.
Do not describe Android Studio BYOA as a stable generally available feature while Google labels it a preview in Rabbit 2 Canary.
Do not claim Codex, Claude Agent or Antigravity is universally the best agent; provider capability, quota, privacy, cost and task fit vary.
Do not grant shell, file, deployment, signing or production-data permissions merely because the agent can request them.
Do not paste API keys, OAuth tokens, Play signing material or customer secrets into prompts or source files to work around an authentication problem.
Do not assume ACP makes all agents behaviorally equivalent or gives them identical Android Studio tool support.
Do not allow an unreviewed preview agent to publish a production build, change billing, rotate credentials or perform destructive infrastructure actions.
HOW GENESIS HANDLES IT
Diagnose the exact failure before choosing a repair.
Genesis separates the visible symptom from the underlying technical cause. Run the supported diagnostic first, review the evidence, and then use a matching repair only when the failure is actually verified.
Platform scope
Android Studio Rabbit 2 Canary · OpenAI Codex · Anthropic Claude Agent · Google Antigravity · Agent Client Protocol
Category
AI coding · Android Studio · Agent interoperability
Last updated
2026-09-25
REPAIR PROFILE
Know the complexity before you edit.
Difficulty
Intermediate
Change risk
High
These labels describe implementation complexity and blast radius, not a guaranteed repair time.
AUTHORITATIVE SOURCES
Verify time-sensitive platform details at the source.
Google's September 24, 2026 announcement highlights OpenAI Codex, Anthropic Claude Agent and Google Antigravity and says other ACP-compatible agents can also connect through Android Studio's agent registry.
Is BYOA available in stable Android Studio?
Google describes BYOA as a preview rolling out starting with Android Studio Rabbit 2 Canary. Treat stable-channel availability as unconfirmed unless current Android Studio release notes explicitly say otherwise.
What is ACP?
Agent Client Protocol is an editor-agent interoperability protocol. Its documentation describes ACP as a standardized way for coding agents and editors or IDEs to communicate in local and remote scenarios.
Can a BYOA agent run commands and tests?
Google says connected agents can read and edit files, run shell commands, run tests, search the web and use Android Studio-provided tools, subject to the integration's permission controls.
Does Android Studio keep my agent credentials private?
Authentication and data handling depend on the selected agent provider and integration. Use the provider-supported sign-in or key flow, keep durable secrets out of prompts and repositories, and review the provider's current privacy and enterprise terms.
Can I switch from Codex to Claude Agent or Antigravity?
Google describes BYOA as supporting multiple agents and says developers can switch when quota or performance needs change. Preserve working state and revalidate permissions because the agents are not behaviorally identical.
Start with a free diagnostic. If Genesis verifies a problem and a compatible treatment exists, continue to the matching Code Store product or repair path. If you cannot find the exact code you need, request it at GenesisCodeDoctor.com rather than forcing a generic snippet into the wrong platform.
