Editor Console Toolkit

English · 简体中文

Log any expression in one keystroke, then switch every generated log off with one command before you commit. Stop the process holding your dev port, silence the editor's "installation appears to be corrupt" warning, and clear the editor's history and caches in one go.

This VS Code extension is for developers who debug with print statements, run several local servers at once, or patch and tidy up the editor itself. Unlike a snippet, a generated log knows its language and where it belongs, and carries a marker so removing or toggling logs never touches one you wrote by hand. Unlike lsof and kill in a terminal, the port view shows each process's working directory, so you do not have to guess which PID is yours. The extension has no runtime dependencies and makes no network requests of its own.

Get started

1. Install from the VS Code Marketplace. For other compatible editors, see Install and update.
2. Put the cursor on a variable and press Alt+L (Option+L on macOS). The log appears on the next line, ready to run:

const user = getUser();
console.log("🎯🎯🎯 [DEBUG] user:", user); // ect:v1

Log the expression under your cursor

The log lands where the value is already defined: inside the block when the cursor is on a function signature or an if condition line, before the statement when the block cannot hold statements (such as switch), and after the statement otherwise. It supports 15 language IDs, from JavaScript and Python to Rust and Elixir, and with multiple cursors. Each run is one undo step, and the file is never saved or reformatted. See Insert and clean up debug logs.

Switch every generated log off before you commit

Run Console Toolkit: Toggle All Console Logs and every log the extension wrote in the file is commented out; run it again to bring them back. Only lines ending in the ect:v1 marker are touched, so your own console.log calls stay as they are.

Stop the process that holds your port

Find the process holding your port in the Port Toolkit view in the Activity Bar, tick the ones you want to stop, and terminate them in one go. The view lists one row per listening process, with its working directory and full command line; a this workspace marker tells you which of several node processes is yours. The editor's own processes cannot be ticked. See Find and stop processes on your ports.

Silence "installation appears to be corrupt"

After you patch the editor's own files, run Checksum Toolkit: Fix Checksums and fully restart the editor, and the warning is gone. It rewrites only the checksums in product.json, keeps a backup for Checksum Toolkit: Restore Checksums, and never asks for your password. See Fix the corrupt-installation warning.

Clear editor history and caches in one go

Run Cleanup Toolkit: Clear History and Caches and confirm the list: it calls the clear commands that the editor and your installed extensions already provide to clear Command Palette history, recent files, search and terminal history, built-in browser storage and more. Clearing Command Palette history, recent files and voice transcripts asks for one more confirmation, and clearing the built-in browser's storage signs you out of sites.

To delete work data instead, run Cleanup Toolkit: Delete Work Data...: uncheck what to keep, and it deletes the checked chat sessions, Local History, cloud Edit Sessions or Copilot memories for good. See Clear editor history and caches.

When not to use it

Inserting and toggling logs does not work in Go, C, C++, shell or the <script> blocks of Vue and Svelte files yet; the port, checksum and cleanup features do not depend on the language you write in. For breakpoints and watch expressions, the built-in debugger is the better tool. The port view and the checksum commands have been verified on real hardware only on macOS so far, and the checksum commands refuse to run in Remote windows (SSH, WSL, containers) and on the web.

Learn more

• Documentation: full usage, settings, troubleshooting and privacy.
• Commands and settings are listed on the marketplace page's Feature Contributions tab.
• Changelog: what changed in each release.

License

MIT. The checksum commands' behaviour is derived from vscode-fix-checksums (MIT © Jürg Lehni 2018, MIT © RimuruChan 2024); none of its code is bundled.