VS Code windows are not limited to a single top-level folder. Additional root folders can be added to an existing window, which is handy when a codebase is split across repositories. CodePen's setup, for example, consists of a main Ruby on Rails app and a separate microservices repo; opening both together in one window makes cross-project search behave as if everything were a single project.

Multiple folders open at once. This means I don’t need to deal with my symlinks anymore.

When a window with multiple roots is closed, VS Code offers to save it as a workspace. The resulting .code-workspace file can live anywhere; keeping it outside the repository avoids imposing one person's setup on the rest of the team. Collected in a local folder, the files double as launchers — placed in the macOS Dock, one click reopens a workspace in its exact layout.

Different icon per workspace

The icon is a little generic, but I like it. A document with a little tiny VS Code icon below it.

Workspace files carry their own icon, which can be replaced. Placing project logos in the bottom-right corner of the VS Code logo SVG produces an own icon for each workspace, making them easier to distinguish in the Dock. On macOS, the icon is changed via "Get Info" on the file: click the icon in the panel and paste the image in.

Starting the project's processes with the workspace

Tasks can run terminal commands on open. The configuration lives in .vscode/tasks.json alongside the settings file:

{
  "version": "2.0.0",
  "tasks": [
    {
      "label": "Run Gulp",
      "type": "shell",
      "command": "gulp",
      "task": "default",
      "presentation": {
        "focus": false,
        "panel": "shared",
        "showReuseMessage": true,
        "clear": true
      },
      "runOptions": {
        "runOn": "folderOpen"
      }
    }
  ]
}

In this case the command gulp starts whenever the workspace is opened. The task must be run manually once (Terminal → Run Task) so VS Code has the required permissions; afterwards it runs automatically.

Scoping settings to a single project

Beyond workspaces, a .vscode/settings.json file inside a project folder overrides VS Code settings for that project only. In a basic Sass setup where Gulp preprocesses .scss into .css, selectors show up in both file types, but the compiled CSS is never edited directly. Excluding it in this file limits the change to the given project and leaves other projects unaffected:

{
  "search.exclude": {
    "**/*.css": true,
  }
}