All but React Native are in beta.
All but React Native are in beta.

Inspect captured events from registered source tools in one chronological timeline. Debug complex user flows by watching network requests, storage changes, state updates, and navigation happen in real-time.

your app, in order, in 83 secondsThe film and the demo show the React Native tool, and the demo uses mock data. Use the Flutter setup and feature descriptions below for supported behavior; the demo does not establish Flutter feature parity.
This interactive timeline combines generated storage, state, query, network and navigation events. Your app shows captured events from configured sources.
flutter pub add buoy_eventsWith the umbrella, Events and its bundled source tools are registered for you. For a standalone install, register Events as well as the sources you need:
import 'package:buoy_events/buoy_events.dart';
registerBuoyEvents();
import 'package:buoy_events/buoy_events.dart';
registerBuoyEvents();
Call registration before using the tool and keep BuoyDevTools mounted in debug mode. Complete Network, Storage, Routes, or Riverpod integration on the corresponding tool pages. Trigger one event and check its source badge in the timeline.
| Source | Events |
|---|---|
| Network | every HTTP request with status and timing |
| Storage | every persisted write with diffs |
| Routes | every navigation with params |
| Riverpod | every provider state change |
Auto-detection — A source must be registered and capturing events before it appears in the timeline.
Tap the magnifying glass in the header to filter the timeline as you type. Matches an event's title, its subtitle (status, duration, host, key), and the full URL of network events — so you can search a host, an action type, a storage key, or a query string value.
Search stacks with the source badges — filter to Network, then search for the failing endpoint.
Copy your event timeline in formats optimized for AI assistants. Reproduce a bug, export, and paste into Claude or ChatGPT with your question — or skip the copy-paste entirely and let an agent read it live with the MCP server's get_events.
The export follows what's on screen: filter to a source or search the timeline first and you copy that slice, not the whole session.
Related events can share a correlationId (included in JSON / LLM exports) so you can trace a full lifecycle across sources when tools emit one.
Install buoy_events — it aggregates automatically from the Buoy tools you already have: network requests, storage writes, navigation, and Riverpod state changes, newest-first, with per-source filters and live counts. Source tools must be registered and configured.
Yes — pause capture and copy the timeline as markdown, JSON, plaintext, or a mermaid diagram.