Attach the Android debugger to a running process by pid or package.
npx skills add https://github.com/Acendas/android-debugger --skill ad-attach
Please help me install this Agent Skill. Skill: ad-attach Source: https://github.com/Acendas/android-debugger/tree/main/skills/ad-attach Command: npx skills add https://github.com/Acendas/android-debugger --skill ad-attach
Attaching to a running Android process to inspect live state, set breakpoints, and patch code without rebuilding.
Attach Claude to a running Android process by selecting a target device and process, then attach with the debugger.
High-intent search queries and answers about installing and using this skill.
You can attach an Android debugger to a running process by resolving the target device and debuggable process, then connecting via JDWP. This enables live state inspection and code patching without rebuilding the application.
Yes, Android process debugging supports target resolution by pid, exact package name, or partial package matches. It automatically resolves unambiguous targets and prompts for clarification when multiple debuggable processes match.
For multi-device scenarios, the Android debugger lists all connected devices and their debuggable processes. It handles target resolution across devices to ensure you attach to the correct process on the right hardware.
After attaching to an Android process, the debugger reports VM version, VM name, and capabilities. It also performs a smoke probe of events to inform tool limitations and guide further investigation.
Live Android process debugging requires the target process to be running in a debuggable state. VM capabilities are reported upon attachment to indicate supported actions and any tool limitations you may encounter.
trohitg...
mub7865Centralize Better Auth and JWT authentication for Next.js 16 App Router projects.
philo-grovesCapture Android runtime evidence via ADB, logcat, JDWP, and Frida.
markwang2658Debug Node.js processes via the Chrome DevTools Protocol.
