Run tasks from tasks.json and package.json directly in the Explorer view without waking up every task-provider extension in VS Code.
Highlights
Executes cached vscode.Task objects directly instead of routing through workbench.action.tasks.runTask.
Shows both vscode tasks and npm scripts, including multi-root workspaces and first-level physical subfolders under the primary workspace.
Always keeps vscode and npm source groups for both the main workspace and nested folders, even when only one source exists.
Adds a Running group at the top whenever any task is active.
Clicking an idle task previews the matching definition line in tasks.json or package.json.
Clicking a running task reveals its terminal and also previews the corresponding configuration line.
Running tasks keep the default spinning indicator, while the Running group uses the extension logo.
Hide, favorite, pin, shortcut, reveal-terminal, auto-run, and display-name rename preferences are stored in .vscode/settings.json instead of rewriting task definitions, and same-name tasks are separated by an internal task identity key.
Checked menu states are shown with text markers such as ✓ Favorite and ✓ Show Terminal on Run.
runTasks.revealTerminalTasks is opt-in and empty by default, so terminals stay hidden unless enabled per task.
runTasks.autoRunTasks starts selected tasks after VS Code launches; once a task stays up, unexpected exits trigger an immediate restart until the user stops it manually.
runTasks.renamedTaskLabels only affects the name shown by RunTasks; the original task label still drives execution and matching.
Icon heuristics cover npm, Python, TypeScript, Shell, PowerShell, Docker, and C/C++ build commands such as cmake, cl.exe, make, ninja, gcc, g++, and clang.
