Understand VS Code Workspaces, Folders, and App Windows

In VS Code, “workspace” describes the project context loaded by the editor; “window” describes the application instance displaying it. They often look like one object because opening a folder typically opens it in one window.

What the workspace contains

For a normal single-folder project, VS Code says the workspace is that root folder. Workspace settings can live in the project’s .vscode folder. A multi-root workspace contains several folders and can be saved as a .code-workspace file with workspace-wide settings and extension recommendations.

The saved workspace can be reopened from the file or Open Recent. An untitled multi-root workspace lasts with the instance and prompts for saving when the instance closes.

What the window controls

A VS Code window is a running editor surface with its own tabs, panels, focus, and screen position. You can open another window or show a file in a new instance without redefining the original workspace. Conversely, opening a different folder in the same window changes the workspace shown by that window.

Use the distinction when organizing

Name and save the workspace when the folder set and settings should be reusable. Use separate windows when contexts must stay visually independent or sit on different displays. Wallo can associate the current VS Code window with a goal, but it neither reads the .code-workspace structure nor guarantees restoration of editor state after that window closes.