agent-react-devtools

React component tree inspection retrieves the rendered hierarchy, subtrees, and details including props, state, and hooks. Start the daemon, connect your app, and run a tree query command like `get tree --depth 3` to observe the live component structure.

Yes, you can profile rendering performance for slow or frequently updating React components by recording profiling sessions. This identifies slow components, frequent re-renders, and commit timelines to pinpoint bottlenecks, with profiling commands supporting export and diff capabilities.

This React debugging approach works with Vite, Next.js, Create React App, and React Native applications. It supports app connection via an init/connect import or Vite plugin, and requires a started daemon to diagnose UI behavior across these platforms.

The best way to trace re-render causes in a running React app is to inspect component-level props, state, and hooks while profiling rendering performance. Recording sessions and analyzing commit timelines pinpoint what triggers frequent re-renders.

Yes, you need a started daemon to inspect React component state and hooks. The daemon enables live component tree inspection, targeted debugging by component name, error checks, and performance profiling commands with export and diff capabilities.

To find specific components by name and check for errors in your React UI, use targeted debugging commands to search components, count them, and inspect error-prone or warning-prone parts of the UI. This requires a connected app and started daemon.