Console

A Chrome-DevTools-style console for your React Native app. Buoy Console captures every console.log, console.warn, console.error, and console.info on the device and shows them in a familiar, filterable panel — on your phone, on the desktop dashboard, or through your AI agent.

Don't take our word for it — this is the real tool, running right here on a mock app session. The guided tour below walks one debugging story: logs stream in, a promo warning and a 500 land, you read the error as structured data instead of one flat line, the gutter names the function behind each run, and the buffer rides out a relaunch. Or skip the tour and just start tapping:

Installation

That's it. The Console tool auto-appears in your FloatingDevTools menu, and capture starts automatically at app launch — logs emitted before you open the tool are retained:

import { FloatingDevTools } from "@buoy-gg/core";

export default function App() {
  return (
    <>
      {/* your app */}
      <FloatingDevTools />  {/* Console tool auto-detected, capture auto-starts */}
    </>
  );
}

import { FloatingDevTools } from "@buoy-gg/core";

export default function App() {
  return (
    <>
      {/* your app */}
      <FloatingDevTools />  {/* Console tool auto-detected, capture auto-starts */}
    </>
  );
}

It patches console.* directly, so logs from your own code and your dependencies are captured — no logger integration or Babel plugin required. Fatal/uncaught JS errors are captured too: the tool hooks React Native's global error handler (chaining any existing one), so a crash — even one during the app's very first render — lands in the log as a [FATAL]-tagged error entry instead of disappearing.

Upgrading? Older versions required mounting <ConsoleRoot /> manually and passing consoleToolPreset via apps. Both are automatic now; existing manual wiring is harmless and can be deleted.

What You Can Do

• See every log, live — log, info, warn, and error stream in as they happen, color-coded by level.
• Filter by level — Focus on just errors and warnings when you're chasing a bug.
• Search — Filter messages by substring to find the exact log you care about.
• Read production logs — Because Buoy runs on-device in any build, you can read console output from a release build with no cable and no Metro connection.
• Expand structured data — Objects and arrays are formatted and expandable, just like the browser console.

Read the console from your AI

With the MCP server, an AI agent can read the console tail directly with get_console — filtering by minimum level or message substring to pull just the errors it needs while debugging.

What's Next

• Events Timeline — Console logs alongside network, state, and route events
• Network Monitor — Inspect the requests behind an error
• AI / MCP Server — Let an agent read the console for you

FAQ

How do I see console logs in a React Native production build?

Install @buoy-gg/console — logs are captured in the app itself and viewable from the floating menu in any build, with access under your control.

Do I still need the Metro terminal or React Native DevTools?

For breakpoints, yes — keep React Native DevTools. For reading logs anywhere (including devices not attached to your machine), the in-app console replaces terminal-watching.