Task CardsTask Cards turns tasks declared in each workspace folder's
Get started · Contribute · Support · Security Features
InstallationAfter Marketplace publication, search for Task Cards in the VS Code Extensions view or run:
For local testing, open the Extensions view, select Views and More Actions… → Install from VSIX…, and choose the packaged Getting startedAdd a
Open Task Cards from the Activity Bar. Click a card to run it, or right-click it to open the corresponding JSON definition.
|
| Property | Required | Description |
|---|---|---|
label |
Yes | Display name and stable identity within the workspace folder. |
command |
Yes | Command to execute. |
args |
No | Array of command arguments. |
execution |
No | shell (default) or process. |
folder |
No | Slash-separated nested folder path. |
icon |
No | Emoji or short text displayed on the card. |
confirm |
No | true for the standard prompt, or a string for a custom prompt. |
Standard VS Code fields such as options, presentation, problemMatcher, dependsOn, runOptions, and detail remain supported.
For shell execution, a command without args is treated as a complete shell command line, so operators such as pipes and && work normally. When args is supplied, VS Code safely constructs the command line from the executable and its arguments.
Ordinary configured task types are also displayed under Ungrouped. Custom folder, icon, and confirm properties are available only on task-card tasks so that tasks.json remains schema-valid.
Scope and confirmation boundary
Only tasks explicitly declared in a workspace folder's .vscode/tasks.json are shown. Auto-detected package scripts, user tasks, and tasks defined only in a .code-workspace file are intentionally excluded.
Confirmation is enforced only when a task is launched from Task Cards. VS Code does not let this extension intercept every native execution path, so launches from Tasks: Run Task, keybindings, dependencies, or other extensions bypass Task Cards confirmation.
Task Cards targets official desktop VS Code, including remote workspaces. It has no browser extension entry, telemetry, or external network requests.
Contributing
Contributions are welcome. Start with the contributing guide, which documents the project philosophy, architecture, development setup, test expectations, and the changes that should be discussed before implementation.
For help, see Support. Report vulnerabilities through the private process in the Security policy. Maintainers can use the release and Marketplace checklist.
