Skip to content
| Marketplace
Sign in
Visual Studio Code>Debuggers>Flutter Debugger PlusNew to Visual Studio Code? Get it now.
Flutter Debugger Plus

Flutter Debugger Plus

dattd-01

|
169 installs
| (1) | Free
Searchable Flutter/Dart debug console with ANSI colors, file-link navigation and regex search — sits next to Terminal, Debug Console & Output.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Flutter Debugger Plus

A searchable Flutter/Dart debug console with native VSCode colors, ANSI support, clickable file links, and a VSCode-style find bar — docked in the bottom panel alongside Terminal, Output, and Debug Console.

Features

🎨 Native Debug Console Colors

Log categories are styled with the same CSS variables VSCode uses internally, adapting automatically to any theme.

🌈 ANSI Color Support

Parses \x1b[...m escape sequences and renders them using VSCode's terminal color palette. Supports bold, dim, italic, and underline.

🔗 Clickable File Links

Detects file references in log output and makes them clickable.

🔍 Filter Bar (always visible — VS Code Debug Console style)

  • Filter input always at top with Cc · W · .* toggles and match navigation
  • Clear (✕) button inside the filter field — appears when text is present; also clears with ESC
  • ↑ / ↓ in filter for search history · ESC clears filter
  • Cmd+F / Ctrl+F focuses filter with selected text (scoped to the console — does not also open editor Find)
  • Works in Cursor, VS Code, and Antigravity IDE

🧰 Console Toolbar

  • Filter bar with Cc · W · .* toggles, match navigation, and category filter
  • Hover tooltips on toolbar buttons (Android Studio style — auto-hide after a configurable duration)
  • Soft wrap toggle — wrap long lines or scroll horizontally
  • Scroll to the end (auto-follow toggle — releases when you scroll up)
  • Clear logs · right-click log area for Copy / Copy All / Add to Chat / Clear Log
  • Add to Chat — select log text and press Ctrl+L / Cmd+L to paste into the current IDE chat input (no temp file / no new chat tab)

🔤 Configurable Log Typography

Customize how log text looks without changing your editor theme:

Setting Default Behavior
fontSize 0 px; 0 follows editor.fontSize
fontFamily "" empty follows editor.fontFamily
lineHeight 1.8 unitless multiplier of the font size
fontColor "" CSS color for normal lines only; empty follows the theme (stderr / warn / ANSI / links unchanged)

Changes apply live — no reload required.

▶ Quick Debug (Editor Title Bar)

When you have a .dart file open, debug controls appear in the top-right editor toolbar:

Control Action
▼ (triangle) Pick a run mode from .vscode/launch.json — same list as Run and Debug (demo, demo profile, demo release, …). Does not include IDE items below the separator (Node.js…, Add Configuration…).
Debug (▶) Starts the selected launch configuration via vscode.debug.startDebugging
Stop Stops the active session (shown while debugging)

How configs are loaded: reads only the configurations[] array in .vscode/launch.json (each entry's name). Your last choice is remembered per workspace.

If there is no launch.json, Debug falls back to the Dart extension / F5 behavior.

After debug starts, Flutter Console+ opens automatically (if autoRevealOnFlutterDebug is enabled).

🚨 Error & Warning Highlighting — same as VS Code's Debug Console

Colors follow the exact same rule VS Code's native Debug Console uses — no custom text-pattern guessing:

  • Red (stderr): the debug adapter (Dart/Flutter) tagged this output line as stderr.
  • Yellow (warn) / Red / other: ANSI color codes embedded in the line itself (e.g. the Dart compiler's red/yellow output, or the logger package's 256-color codes) are honored, just like a real terminal.
  • Default (info/log): everything else — stdout/console output with no ANSI hint.

Since a debug adapter usually sends a whole multi-line message (e.g. a full Flutter error box) as one output event with one category, every line split from that event keeps the same color — matching what you'd see in the native Debug Console.

File paths in log lines (package:…, lib/…, file:///…) stay clickable regardless of category.

⚡ Performance

  • Batched rendering via requestAnimationFrame
  • Auto scroll-to-bottom, pauses when scrolled up
  • Configurable max log lines in memory

Settings

{
  "flutterDebuggerPlus.autoRevealOnFlutterDebug": true,
  "flutterDebuggerPlus.onlyFlutterDart": true,
  "flutterDebuggerPlus.maxLines": 5000,
  "flutterDebuggerPlus.clearOnRestart": true,
  "flutterDebuggerPlus.tooltipDuration": 3,
  "flutterDebuggerPlus.fontSize": 0,
  "flutterDebuggerPlus.fontFamily": "",
  "flutterDebuggerPlus.lineHeight": 1.8,
  "flutterDebuggerPlus.fontColor": ""
}
Setting Default Description
autoRevealOnFlutterDebug true Auto-open the panel when a Flutter/Dart debug session starts
onlyFlutterDart true Capture only Dart/Flutter sessions; disable to capture all debug adapters
maxLines 5000 Maximum number of log lines kept in memory
clearOnRestart true Clear logs on hot restart / new debug session
tooltipDuration 3 Toolbar tooltip visibility in seconds; 0 = until pointer leaves
fontSize 0 Log font size in px; 0 follows editor.fontSize
fontFamily "" Log font family; empty follows editor.fontFamily
lineHeight 1.8 Log line spacing multiplier
fontColor "" Default color for normal log lines; empty follows the theme

Project Details

  • Repository: arthurtran01/flutter-debugger-plus
  • Issues: Report a bug
  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft