Browser-based ADB tool via WebUSB. No SDK, no drivers, no install – just plug in and debug. Includes an AI assistant that runs ADB commands from plain English. BYOK (bring your own API key), zero tracking. Features: shell, logcat, file browser, app manager, screenshots, performance monitoring, and more. Everything runs client-side.
Hey Product Hunt! 👋
Built this because I got tired of two things:
The Android debugging setup dance
Googling ADB commands every single time
So ADBWrench runs entirely in your browser (WebUSB) and has an AI assistant that knows ADB better than I do.
Privacy-first: Bring your own API key, we don't store or track anything. Your device data stays local.
Some things it won't replace:
scrcpy for screen mirroring
Full Android Studio for deep profiling
Wireless ADB (WebUSB needs USB)
But for quick debugging with natural language? This removes a ton of friction.
Open source and free. Would love your feedback!
Report
This is brilliant! ADB in browser with AI assistance is super clever. As a dev tools builder, I'm curious - how do you handle the AI assistant integration? Are you using a specific LLM provider?
Thanks @omuili ! We have kept it open so that you can bring in your onw API keys. It supports OpenAI style API endpoints, so you can use any model via OpenRouter in theory.
Report
@mukulhjoshi Love the model-agnostic approach. OpenAI-style endpoints and OpenRouter is a solid abstraction layer. Are you doing anything special around prompt/context management for ADB commands, or leaving that fully up to the user?
ADB Wrench
This is brilliant! ADB in browser with AI assistance is super clever. As a dev tools builder, I'm curious - how do you handle the AI assistant integration? Are you using a specific LLM provider?
ADB Wrench
Thanks @omuili ! We have kept it open so that you can bring in your onw API keys. It supports OpenAI style API endpoints, so you can use any model via OpenRouter in theory.
@mukulhjoshi Love the model-agnostic approach. OpenAI-style endpoints and OpenRouter is a solid abstraction layer. Are you doing anything special around prompt/context management for ADB commands, or leaving that fully up to the user?