One surface for the inner loop.

01 Thesis

Stop acting as a human router between editors, terminals, and device pickers.

This extension wires VS Code to the Gradle + AGP + SDK stack you already use — tasks, targets, and install in one flow. build.gradle stays the source of truth; controls sit next to the code.

With agents in VS Code, fewer forced trips to a full IDE for routine Gradle or device steps — stay in one surface.

02 The hidden tax

Compilers are fast. Friction isn’t. It lives around the compile button.

  • Gradle in the wrong working directory
  • Guessing which device is attached
  • Install steps that don’t live next to your code

That’s fragmentation — not “how Android is.” This tool aims to own the loop from the editor, without replacing your build.

03 The arsenal

A cockpit, not a junk drawer — Gradle, targets, install, detection.

Gradle, navigable

Browse Gradle tasks in the side panel — assemble, install, clean, sync without leaving the editor.

Variants, picked

Discover build variants and modules from Gradle. Pick the active variant or root from a quickpick.

Targets, unambiguous

Live device + emulator picker with auto-selection. Status bar shows the active install target.

Build → install → launch

Tight loop — build, push to device, launch the app. Repeat until it runs.

Logcat, integrated

Live device logs with regex filters, level coloring, package filter, and persistent column settings.

APK cache, browseable

Re-install previous build outputs from a cache. Clean it on demand.

Debug, attached

Attach the JDWP debugger to a running process via local port forwarding. Source-mapped breakpoints out of the box.

Remote ADB, bridged

Connect to a phone over a WebSocket relay — wireless, remote LAN, or paired companion app.

Release signing, scaffolded

Guided setup writes signingConfigs blocks into your build.gradle. Local-override flow keeps secrets out of the repo.

Daemons, contained

Isolated GRADLE_USER_HOME so editor builds don't fight Studio. Auto-stop idle daemons after N minutes.

04 The loop

Linear flow — write → build → target → install → run.

  1. Write
  2. Build
  3. Target
  4. Install
  5. Run

05 Principles

Less theater around the toolchain.

  • Respect Gradle — UI on top, not a replacement.
  • Match CI — local runs should align with what pipelines enforce.
  • Plain SDK/ADB — same binaries, visible flows.

06 Compatibility

Expects a normal Android/Gradle layout, AGP, SDK, and local.properties where applicable.

  • AGP workflows
  • Gradle builds
  • Android SDK + ADB
  • VS Code 1.85+
  • Cursor
  • Java / Kotlin breakpoints

07 Reality check

Independent extension — not from Google or Gradle. Not a replacement for Android Studio when you need the full IDE; it optimizes the daily write → build → target → prove loop in VS Code.

It does not: rewrite your Gradle files, replace Studio for niche tooling, or magic away the SDK.

08 Install

Free on the Visual Studio Marketplace.

Install from Marketplace Inspect the source

09 Open source

Issues and PRs: github.com/AndroidGradleTools

10 License

MIT — see the repository for exact terms.