folddevtools-android-webview-debugger

Debug Android WebView, browser, and Node.js targets via Chrome DevTools.

4|Updated May 16, 2026
One-click install
npx skills add https://github.com/Aradotso/devtools-skills --skill folddevtools-android-webview-debugger
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: folddevtools-android-webview-debugger
Source: https://github.com/Aradotso/devtools-skills/tree/main/skills/folddevtools-android-webview-debugger
Command: npx skills add https://github.com/Aradotso/devtools-skills --skill folddevtools-android-webview-debugger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the hard problem of inspecting and debugging Android WebView (and related) issues when you need Chrome DevTools functionality but the target is running on-device.

Core Features & Use Cases

  • Rooted WebView debugging: Automatically discovers and connects to WebView devtools sockets (e.g., webview_devtools_remote_<pid>) to inspect multiple running WebView instances.
  • Remote debugging without root: Uses ADB localabstract forwarding to expose the device’s devtools socket over TCP so FoldDevtools can connect.
  • Stetho/StethoX support: For apps instrumented with Stetho, forwards the Stetho devtools socket and debugs via the same workflow.
  • XPosed module (force-enable WebView debugging): Enables WebView debugging for other apps without changing their code when the module is installed and configured.

Quick Start

Use FoldDevtools and connect in remote mode to your forwarded debug endpoint (127.0.0.1:9222) to inspect the target WebView in Chrome DevTools.

Frequently Asked Questions about folddevtools-android-webview-debugger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug an Android WebView with Chrome DevTools?▼

Debug Android WebView by discovering the devtools socket and connecting via FoldDevtools in remote mode to a forwarded TCP endpoint like 127.0.0.1:9222. This exposes on-device WebView instances for Chrome DevTools inspection.

How does ADB port forwarding enable remote debugging for WebView without root?▼

ADB localabstract forwarding exposes the device's localabstract devtools socket over TCP, enabling remote debugging without root. FoldDevtools connects to this forwarded port to inspect the target WebView session.

Can I use Stetho to inspect an Android app's WebView without modifying its code?▼

Yes, for apps instrumented with Stetho, the workflow forwards the Stetho devtools socket. An XPosed module can also force-enable WebView debugging for other apps without changing their code.

What's the best way to inspect multiple running WebView instances on a rooted device?▼

On rooted devices, automatically discover and connect to WebView devtools sockets using identifiers like webview_devtools_remote_<pid> to inspect multiple running WebView instances simultaneously.

Does this WebView debugging workflow support Node.js targets?▼

Yes, FoldDevtools enables Chrome DevTools debugging of Android WebView, browsers, and Node.js targets by attaching the devtools client to the target session via local or forwarded remote devtools sockets.

What do I need to connect FoldDevtools to a remote debug endpoint?▼

You need a valid FoldDevtools connection workflow and access to the appropriate debug socket identifiers. Connect in remote mode to your forwarded debug endpoint at 127.0.0.1:9222 to inspect the target.