cobalt_talker_flutter #

Talker's log screen, in the same palette as the Cobalt inspector.

cobalt_talker is pure Dart on purpose: it adapts Cobalt's events to talker, and pulling talker_flutter in would push a UI dependency onto every consumer, including tests that never draw. This package is where the Flutter half lives, so only an app that wants the screen pays for it.

Navigator.of(context).push(
  MaterialPageRoute<void>(builder: (_) => CobaltTalkerScreen(talker: talker)),
);

The palette is inherited from CobaltInspectorTheme where one is in force, and derived from the host's own Theme where none is — so the log screen and the inspector match without configuration, and both follow the app when it is configured.

Why the bridge is four lines #

TalkerScreenTheme colours entries by their title, and CobaltTalkerObserver writes exactly four: cobalt-scope, cobalt-startup, cobalt-instance, cobalt-failure. Those are the same four families the inspector colours by, which is what makes one palette dress both screens.

final theme = talkerScreenThemeOf(CobaltInspectorTheme.of(context));

Only Cobalt's own entries are recoloured. Your logs, and talker's built-in kinds, keep talker's colours.