What problem does it solve? It removes the guesswork from debugging a running JavaScript runtime by giving you a structured way to connect to Metro's CDP endpoint, diagnose connection failures, inspect React component trees, read console logs, and evaluate JavaScript inside the live app. ## Core Features & Use Cases - Connection & Diagnostics: Connect to the JS runtime via debugger-connect and diagnose failures with debugger-status, which returns coded reasons (metro_not_running, no_app_connected, device_mismatch, stale_connection) plus actionable guidance instead of raw errors. - Component Inspection: Dump the full React fiber tree with debugger-component-tree or trace a tapped element to its source file and line with debugger-inspect-element, including source-map symbolication. - Console Log Analysis: Use debugger-log-registry to get log summaries and clusters, then grep the flat log file with anchored entry IDs instead of reading logs inline. - Multi-Platform Support: Works with React Native on iOS, Android (via adb reverse), and Vega, plus a subset of tools for Chromium/CDP apps such as Electron. - Use Case: Your Android emulator app shows a blank screen. Run debugger-status to find no_app_connected, relaunch with restart-app, reconnect, then grep the log registry for the red-screen error and inspect the offending component's source location. ## Quick Start Connect to the running React Native app through Metro and show me the current console error logs and component tree.
