Installation
Install @axonpack/expo-devtools and its three peer dependencies.
npx expo install @axonpack/expo-devtools react-native-safe-area-context react-native-webview expo-clipboardreact-native-safe-area-context, react-native-webview and expo-clipboard are peer dependencies.
Your app supplies them, so each resolves to the version your Expo SDK ships rather than one this
package pins.
There is nothing else to install: no config plugin, no app.json changes, and no native code to
write.
Expo Go or a development build
Both work. The package ships exactly one native module, loaded optionally, so an app running in Expo Go still gets the whole panel. A handful of readings go quiet:
- Main-thread frame rate
- App memory and device memory
- CPU usage
- Disk space (Android only in any case)
- The measured startup breakdown
- The Debug tab's main-thread controls
- Native crash capture, and most device details on a crash report
- The measured phases of a request, in the Timing tab
Everything else, including all of Console and Navigation, behaves the same. A development build made
with expo run:ios, expo run:android or EAS lights the rest up. The full list is in
What needs a development build.
A control that needs the native module says so where it sits. Nothing in the panel crashes without it.
Give your AI agent the skill
The package also installs the devtools command, which reads the running app from a terminal so an
AI agent can see what it recorded. It needs Node 22 or newer. After the
quick start, with the app open and expo start running, this
lists it:
npx devtools appsUse with AI agents covers every command. If you work with a coding agent, install the Axonpack skill into the project too. It has the agent learn the tool and the setup from these docs:
npx skills add axonpack/skillsThen you can ask it to "Set up @axonpack/expo-devtools in this app", and it follows this page and the quick start from the live docs. Agent skill has the command for each package manager.