Console Prism

Multiple live filtered views for the VS Code Debug Console.

Console Prism watches the output events produced by your existing debugger and shows matching lines in separate filter tabs. It does not require changes to your application, logging calls, or debug configuration, and the normal Debug Console continues to work as usual.

Features

• Create multiple live filters for the same debug output.
• Use ordinary text or JavaScript regular expressions.
• Toggle case-sensitive matching independently for each filter.
• Clear one filter or all filters without removing their definitions.
• Copy all output from the selected filter.
• Remove filters you no longer need.
• Keep filter definitions per workspace between VS Code sessions.
• Retain the most recent 5,000 lines per filter.
• Batch high-volume output updates to keep the view responsive.

Captured output stays in memory and is not restored after a new debug session or VS Code restart.

Getting started

1. Start your project's normal debug session.
2. Open the bottom panel and select Console Prism.
3. Select Add Filter (+) and enter text to match.
4. Produce output normally. Matching complete lines appear live in that filter's tab.

New filters receive output produced after they are created.

Actions

The same actions are available from the Command Palette under Console Prism.

How it observes output

Console Prism passively observes Debug Adapter Protocol (DAP) output events from the active debug sessions. This commonly includes application stdout, stderr, and messages displayed in the Debug Console.

Output that a debug configuration sends directly to an integrated or external terminal may not be emitted as a DAP output event and therefore cannot be observed by Console Prism. The extension never replaces the debugger or redirects output.

Output from concurrently active debug sessions is currently combined in the same filters.

Privacy

Console Prism does not collect telemetry. Captured console output is kept only in memory. Filter definitions and their matching options are stored in VS Code workspace state so they can be restored for that workspace.

Development

npm install
npm test
npm run package:vsix

Launch the extension in an Extension Development Host with Ctrl+F5. Then open a project in that window and start its normal debugger with F5.

License

MIT. See the included LICENSE file.