The Console receives every console.log, warn and error from the app with a link to its source line, and its prompt evaluates JavaScript inside Hermes 11,328 on the phone, not in the browser. The same evaluation through scripts/cdp.mjs shows what the runtime is:
node scripts/cdp.mjs eval "[typeof HermesInternal,
HermesInternal.getRuntimeProperties()['OSS Release Version'], typeof nativeFabricUIManager]"["object","250829098.0.17","object"]
HermesInternal exists only in Hermes, and nativeFabricUIManager is the Fabric renderer's native binding. Type such expressions at the Console's prompt, or call app code there (a store's getState(), say) to inspect state without adding logs. With DevTools open, LogBox hides everything but fatal errors in the app, and the messages appear here instead.
React Native 0.83 36,878 added a Network panel for fetch(), XMLHttpRequest and <Image> requests, with headers, timings and response previews. In this Expo 6,418 app the tab is called Expo Network: SDK 57's global fetch is Expo's own (Uploading Media to a Server), and Expo feeds its requests to its panel through a separate /inspector/network socket. When scripts/cdp.mjs enabled the standard CDP Network domain and the app fetched /books/3 (the console logged status 200), no Network.* events arrived at all, so inspect Expo apps in the Expo Network tab, and fall back to logging for WebSockets, which neither panel records.