Every Android engineer knows the pain: you change a modifier, tweak a layout parameter, or want to test edge-case UI states, and you’re stuck waiting for Gradle builds or flaky preview renders.
Now bring AI coding agents into the loop—they write code, but they can’t *see* or *interact* with the actual runtime state on your physical device.
I wanted to bridge this gap, so I built **ComposeBridge**:
A developer framework and MCP server that connects Android Studio / AI agents directly to running Jetpack Compose apps.
**How it works under the hood:**
- Runs a lightweight MCP server & WebSocket daemon.
- Inspects live Compose node trees and state parameters on-device.
- AI agents (Claude, Cursor, etc.) can inspect runtime UI and apply deterministic AST mutations directly to the source.
- Instant live override—no full rebuilds required.
I open-sourced the project and just published the official JetBrains plugin & Glama MCP integration.
Curious to hear from fellow Android & toolchain devs:
How are you currently integrating AI agents into your native mobile workflows? Would live AST runtime mutation fit into your daily setup?
🔗 GitHub: https://github.com/JALAL591/compose-bridge
submitted by /u/TechsOne[link] [comments]