Editor
Workspaces
Open one folder, or several roots in one window, when a project spans more than one repository.
Folders vs. workspaces
Opening a single folder (File → Open Folder…) covers most projects. Gyaanmitra remembers your layout, open editors, and per-folder settings. You do not have to save that yourself.
A multi-root workspace groups several folders into one window. They do not have to be nested, and they do not have to be on the same drive. You get one Explorer tree, one Search scope, and one Source Control view that tracks each folder's own Git repository.
Add a folder to the current window
Use File → Add Folder to Workspace… to bring in a second root next to whatever is already open.
Save the workspace
File → Save Workspace As… writes a .code-workspace file with every
root folder and any workspace-level settings. Open that file later to
get the same multi-root layout back.
Scope search and tasks per folder
Right-click a root in the Explorer for actions that stay in that folder: search, run a task, or open a terminal that starts there.
Workspace settings
Settings can sit at three levels. Each one overrides the level before it:
User (everywhere), Workspace (anyone who opens this
.code-workspace or folder), and Folder (only one root of a multi-root
workspace). A monorepo can share one formatter for the team, and a single
package can still set its own line length when it needs to.
Workspace settings are stored in your project
A single-folder workspace keeps settings in .vscode/settings.json inside
that folder. A saved multi-root workspace keeps them inside the
.code-workspace file. Both are safe to commit, so the team shares the
same defaults.
Workspace Trust
The first time you open a folder you have not opened before, Gyaanmitra asks whether you trust its authors before it runs tasks, debug configurations, or workspace extensions. That is a guard against opening a repository that would run code without you agreeing. You can trust a folder for good, trust it only for this session, or keep a folder in a read-only mode if you do not trust it. Review earlier decisions from Manage Workspace Trust in the Command Palette.