Dedicated tasks

A powerful VS Code extension that transforms your tasks.json and launch.json into an organized, easy-to-access UI with grouping, icons, and quick-access status bar integration.

Why Dedicated tasks?

If you have many tasks and debug configurations in your workspace, the default VS Code task picker and launch menu can become overwhelming. This extension solves that by:

📁 Organizing tasks and launch configs into hierarchical groups - Create multi-level folder structures
📌 Pinning tasks and debug configs to the status bar - One-click access to your most-used actions
🎨 Supporting icons - Use VS Code's built-in icon library for visual identification
🔍 Providing a dedicated sidebar view - All your tasks and launch configs in one convenient location
⚡ Maintaining your existing config files - Just add metadata, no breaking changes
🔀 Unified organization - Tasks and launch configs can share groups and be sorted together

Features

Configuration Support: Organize tasks into configurations for top-level separation. Tasks can belong to multiple configurations. Switch between configurations via a dropdown in the tree view header.
Multi-folder Workspace Support: Full support for multi-folder workspaces with folder abbreviations and per-folder configuration
Tree View Controls: Filter, expand all, and collapse all buttons for easy navigation
Dedicated Activity Bar View: Access your tasks and launch configs from a dedicated icon in the VS Code activity bar
Status Bar Integration: Pin frequently used tasks and launch configs to the status bar for quick access with hierarchical group selection
Icon Support: Use any VS Code icon (e.g., $(gear), $(rocket), $(debug)) in labels
Hierarchical Groups: Organize tasks and launch configs into multi-level collapsible folder structures
Unified Organization: Tasks and launch configs can share groups and be sorted together by order
Flexible Organization: Items can appear in multiple groups simultaneously
Custom Labels & Details: Override names with friendly labels and add descriptions
Item Ordering: Control the display order of tasks and launch configs within groups
Selective Visibility: Hide items from the UI while keeping them in your config files
Dual File Support: Configure both tasks.json and launch.json with the same metadata structure

Usage

1. Configure Your Tasks and Launch Configurations

Add the dedicatedTasks configuration to your tasks in .vscode/tasks.json:

{
  "version": "2.0.0",
  "tasks": [
    {
      "label": "Build",
      "type": "shell",
      "command": "npm run build",
      "options": {
        "dedicatedTasks": {
          "label": "$(rocket) Build Project",
          "detail": "Compile TypeScript and bundle",
          "groups": [["Build", "Production"]],
          "order": 1
        }
      }
    },
    {
      "label": "Test",
      "type": "shell",
      "command": "npm test",
      "options": {
        "dedicatedTasks": {
          "label": "$(beaker) Run Tests",
          "detail": "Execute all unit tests",
          "groups": ["Test", ["Development", "Test"]],
          "order": 1
        }
      }
    },
    {
      "label": "Dev Server",
      "type": "shell",
      "command": "npm run dev",
      "options": {
        "dedicatedTasks": {
          "label": "$(server) Start Dev Server",
          "detail": "Launch development server with watch mode",
          "groups": [["Development", "Server"]],
          "order": 1
        }
      }
    },
    {
      "label": "Clean",
      "type": "shell",
      "command": "npm run clean",
      "options": {
        "dedicatedTasks": {
          "label": "$(trash) Clean Build",
          "detail": "Remove all build artifacts",
          "groups": ["Build"],
          "order": 0
        }
      }
    }
  ]
}

And/or add it to your launch configurations in .vscode/launch.json:

{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Debug Extension",
      "type": "extensionHost",
      "request": "launch",
      "dedicatedTasks": {
        "label": "$(debug) Debug Extension",
        "detail": "Launch extension in debug mode",
        "groups": [["Debug", "Extension"]],
        "order": 1
      }
    },
    {
      "name": "Run Tests",
      "type": "node",
      "request": "launch",
      "program": "${workspaceFolder}/test/index.js",
      "dedicatedTasks": {
        "label": "$(beaker) Debug Tests",
        "detail": "Run tests with debugger attached",
        "groups": ["Test", ["Debug", "Tests"]],
        "order": 1
      }
    }
  ]
}

2. View Your Tasks and Launch Configurations

Click on the "Dedicated Tasks" icon in the activity bar (left sidebar)
Your tasks and launch configs will be organized into collapsible groups
Click on any task to run it, or click on any launch config to start debugging

3. Use Configurations (Optional)

Organize tasks at the top level using configurations:

Add a configurations array to any task or launch config's dedicatedTasks configuration
Tasks without configurations default to ["default"]
Tasks can belong to multiple configurations simultaneously
When multiple configurations exist, a dropdown button appears in the tree view header
Click the dropdown to switch between configurations
The tree view title updates to show the current configuration (e.g., "DEDICATED TASKS: Development")
Status bar items are also filtered to show only tasks from the selected configuration

Example with configurations:

{
  "label": "Build for Production",
  "type": "shell",
  "command": "npm run build:prod",
  "options": {
    "dedicatedTasks": {
      "label": "$(package) Production Build",
      "groups": ["Build"],
      "configurations": ["Production", "CI/CD"]
    }
  }
}

4. Configure Status Bar (Optional)

Add frequently used tasks and launch configs to the status bar for quick access:

Click the gear icon (⚙️) in the Dedicated Tasks view title bar, or
Run the command "Configure Status Bar Items" from the command palette
Select individual tasks/launch configs or entire groups to display in the status bar
Selected items will appear in the status bar with their icons
Click any status bar item to execute it immediately (run task or start debugging)

Status Bar Tips:

You can select entire groups (e.g., all "Build" items) to show multiple related tasks and configs
Items in the status bar show their configured icons and labels
Hover over a status bar item to see its description
Configuration is saved in .vscode/dedicated-tasks.json and can be version controlled
Tasks and launch configs can be mixed in the same status bar

Configuration Files

This extension uses the following configuration files in your workspace:

`.vscode/tasks.json`

Standard VS Code tasks file with optional dedicatedTasks metadata in options:

{
  "version": "2.0.0",
  "tasks": [
    {
      "label": "Build",
      "type": "shell",
      "command": "npm run build",
      "options": {
        "dedicatedTasks": {
          "label": "$(rocket) Build",
          "groups": ["Build"],
          "order": 1
        }
      }
    }
  ]
}

`.vscode/launch.json`

Standard VS Code launch configurations with optional dedicatedTasks metadata at the root level:

{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Debug",
      "type": "node",
      "request": "launch",
      "program": "${file}",
      "dedicatedTasks": {
        "label": "$(debug) Debug",
        "groups": ["Debug"],
        "order": 1
      }
    }
  ]
}

`.vscode/dedicated-tasks.json`

Extension configuration file (auto-generated when you configure status bar items):

{
  "abbreviation": "API",
  "statusBar": {
    "itemNames": ["Build", "Debug"],
    "groups": [["Development", "Build"]]
  }
}

File structure:

abbreviation: Optional custom folder abbreviation (overrides auto-generated 3-character abbreviation)
statusBar.itemNames: Array of task/launch config names to show in status bar
statusBar.groups: Array of group paths - all items in these groups will be shown

This file can be manually edited or manipulated by scripts/tools. Changes are automatically detected and applied.

Getting Started

Quick Start

Install the extension from the VS Code Marketplace
Open your workspace that contains .vscode/tasks.json and/or .vscode/launch.json
Add dedicatedTasks configuration to your tasks and/or launch configs (see examples above)
Click the checkmark icon in the activity bar to view your organized tasks and launch configs
Optional: Click the gear icon (⚙️) in the view title to configure status bar items

Icons

You can use any icon from the VS Code icon library by prefixing your label with the icon syntax:

"label": "$(icon-name) Task Name"

Popular icons:

$(rocket) - Launch/Build
$(gear) - Configure
$(trash) - Clean
$(beaker) - Test
$(server) - Server
$(cloud-download) - Download
$(cloud-upload) - Upload
$(debug) - Debug
$(tools) - Tools
$(package) - Package

See the complete icon reference for all available icons.

Configuration Options

`dedicatedTasks` Object

Add this object under tasks[].options in your tasks.json, or directly in each configuration object in launch.json:

Property	Type	Required	Description
`label`	string	No	Display label for the task/config (defaults to task's `label` or config's `name`)
`statusbarLabel`	string	No	Shorthand label for status bar display (defaults to `label` if not set)
`detail`	string	No	Additional detail text shown below the item label
`hide`	boolean	No	Set to `true` to hide this item from the UI (default: `false`)
`groups`	array	Yes	Array of group paths. Each item can be a string for single-level groups or an array of strings for multi-level hierarchies
`order`	number	No	Sort order within the group - tasks and launch configs sort together (lower numbers appear first, default: `0`)
`configurations`	string[]	No	Array of configurations for top-level organization. Tasks with no configurations default to `["default"]`. When multiple configurations exist, a dropdown appears in the tree view header. Tasks can belong to multiple configurations.

Group Path Examples

The groups field supports flexible hierarchies:

Single-level group: "groups": ["Build"] - Item appears in "Build" group
Multi-level group: "groups": [["Build", "Frontend"]] - Item appears nested under Build → Frontend
Multiple locations: "groups": ["Quick Tasks", ["Build", "Frontend"]] - Item appears in both "Quick Tasks" and "Build → Frontend"
Mixed levels: "groups": ["Build", ["Development", "Build"]] - Item appears in top-level "Build" and nested "Development → Build"
Shared groups: Tasks and launch configs can use the same group names and will be sorted together by order

Complete Examples

Task Example (in tasks.json):

{
  "label": "Build Production",
  "type": "shell",
  "command": "npm run build:prod",
  "options": {
    "dedicatedTasks": {
      "label": "$(package) Production Build",
      "detail": "Build optimized production bundle",
      "groups": [["Build", "Production"], "Quick Actions"],
      "order": 2,
      "hide": false
    }
  }
}

Launch Config Example (in launch.json):

{
  "name": "Debug Production Build",
  "type": "node",
  "request": "launch",
  "program": "${workspaceFolder}/dist/index.js",
  "dedicatedTasks": {
    "label": "$(debug) Debug Production",
    "detail": "Debug the production build",
    "groups": [["Build", "Production"], "Quick Actions"],
    "order": 3,
    "hide": false
  }
}

Both items will:

Display with their respective icons
Appear in two locations: "Build → Production" and "Quick Actions"
Be sorted together by order (task at 2, launch config at 3)
Be visible in the UI (not hidden)

Requirements

VS Code version 1.85.0 or higher

Extension Settings

This extension contributes the following settings:

Setting	Type	Default	Description
`dedicatedTasks.showDetailsInTreeView`	boolean	`false`	Always show task/launch config details in the tree view. When disabled, details are only visible in tooltips.
`dedicatedTasks.suppressLaunchJsonWarnings`	boolean	`false`	Suppress validation warnings for `dedicatedTasks` property in launch.json.

Tips & Tricks

Organizing Large Lists

For projects with many tasks and launch configs (50+), use a hierarchical structure:

"groups": [["Build Type", "Architecture", "Operation"]]

Example: ["Debug", "x64", "Build"] → Debug → x64 → Build

Status Bar Best Practices

Select parent groups instead of individual items to quickly show all related tasks and launch configs
Use icons to make items visually distinct in the status bar
Keep labels short for status bar items (the detail field provides additional info on hover)
Use order numbers to control the sequence of items in the status bar (lower = left)
Mix tasks and launch configs in the same groups for related workflows (e.g., build task at order 1, debug config at order 2)

Quick Access Pattern

Create a "Quick Actions" or "Favorites" group for your most-used tasks and launch configs:

"groups": ["⭐ Favorites", ["Build", "Debug"]]

This makes the item appear both in its logical location and in a quick-access group. Works for both tasks and launch configurations.

Hiding Implementation Details

Use "hide": true for helper tasks that should run via dependsOn but don't need to be directly accessible:

{
  "label": "clean-temp",
  "command": "rm -rf temp",
  "options": {
    "dedicatedTasks": {
      "groups": ["Build"],
      "hide": true
    }
  }
}

Similarly for launch configs you rarely use directly but want to keep configured.

Known Issues

Launch.json Schema Validation

VS Code's built-in schema for launch.json doesn't recognize the dedicatedTasks property, so it may show as a validation warning/error in the editor (yellow/red squiggly lines). This is cosmetic only - the extension works perfectly fine.

Workarounds:

Ignore the warning - The property is read correctly by the extension

Add a comment to document it for other developers:

{
  "name": "Debug Extension",
  "type": "extensionHost",
  "request": "launch",
  // For Dedicated Tasks extension - organizes launch configs in sidebar
  "dedicatedTasks": {
    "label": "$(debug) Debug Extension",
    "groups": [["Debug"]]
  }
}

Disable schema validation for launch.json (not recommended as it disables all validation)

This limitation exists because VS Code doesn't allow extensions to extend the built-in launch.json schema, only replace it entirely (which would break all standard IntelliSense). The tasks.json schema works fine because VS Code allows custom properties in the options object.

License

MIT

Dedicated Tasks

Jan Jörke