buoy_console

Inspect captured print, debugPrint, and error messages, with filtering and search.

Requirements

Use a Flutter debug build and a Free or Pro Buoy account key. These packages require Dart 3.9 or later, below 4.0, and Flutter 3.27 or later; your Flutter installation must satisfy both constraints. The Buoy widget does not start its tools in profile or release builds, including with Pro.

Install and register

flutter pub add buoy_console

This example registers the standalone package. In an existing app, keep your screens and providers and apply the registration and builder changes to that app. Complete the tool-specific integration below before testing capture.

import 'package:buoy_console/buoy_console.dart';
import 'package:flutter/foundation.dart';
import 'package:flutter/material.dart';

void main() {
  BuoyConsole.runZoned(() {
    if (kDebugMode) registerBuoyConsole();
    runApp(const MyApp());
  });
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      builder: (context, child) => BuoyDevTools(
        licenseKey: const String.fromEnvironment('BUOY_KEY'),
        child: child ?? const SizedBox.shrink(),
      ),
      home: const Scaffold(body: Center(child: Text('Buoy test app'))),
    );
  }
}

Get a key from your Buoy account, then run:

flutter run --dart-define=BUOY_KEY=YOUR_LICENSE_KEY

If you already use the buoy umbrella, it registers the panel; keep its builder and complete the app integration below. For a complete umbrella setup, see the Flutter Quick Start.

Capture scope

print capture requires BuoyConsole.runZoned. Keep binding initialization and runApp inside that zone; the helper initializes the binding. Do not initialize the Flutter binding in an outer zone first.

registerBuoyConsole() installs debugPrint and error hooks. If you install capture separately, BuoyConsole.install() provides those hooks but does not register the menu tool. Only the zone captures print calls within its scope. These hooks do not capture every native crash or another isolate's output.

The log buffer is in memory by default. Enable Preserve log in the Console filters to retain supported log history across restarts, subject to account and history limits.

Check the integration

After account access is ready, trigger a print inside the captured zone and a debugPrint. Find both in Console. Messages emitted before capture or account admission may be absent.

Desktop and MCP

Open Buoy Desktop, sign in, and select the connected device. The default broker port is 42831. The iOS Simulator uses localhost; the Android emulator maps localhost to its host address. For a physical device, set socketUrl: 'http://YOUR_COMPUTER_LAN_IP:42831' on BuoyDevTools and use a network that can reach your computer.

MCP needs separate process account configuration and Pro access. Remote capabilities depend on each tool's adapter. Account validation makes network requests, and device sessions can cross your LAN. See Telemetry for data-flow details.

Full Console guide

License

Proprietary software. © Buoy LLC. See the Terms of Service and pricing.