Editor
Workspaces
From a single folder to a monorepo spanning multiple repositories, Gunamaya's workspace model scales with your project.
Folders vs. workspaces
Opening a single folder (File → Open Folder…) is the default and covers most projects — Gunamaya remembers your layout, open editors, and per-folder settings automatically, without you needing to save anything explicitly.
A multi-root workspace groups multiple folders — which don't need to be nested inside one another, or even on the same drive — into a single window with one Explorer tree, one Search scope, and one Source Control view that tracks each folder's own Git repository independently.
Add a folder to the current window
Use File → Add Folder to Workspace… to bring in a second root alongside whatever's already open.
Save the workspace
File → Save Workspace As… writes a .code-workspace file capturing
every root folder plus any workspace-level settings — open that file
later to restore the exact same multi-root layout.
Scope search and tasks per folder
Right-click any root in the Explorer for folder-scoped actions — searching, running a task, or opening a terminal rooted at just that folder rather than the whole workspace.
Workspace settings
Settings can be scoped at three levels, each overriding the one before it:
User (applies everywhere), Workspace (applies to everyone who opens
this .code-workspace or folder), and Folder (applies only within one
root of a multi-root workspace). This is how a monorepo can enforce, say, a
consistent formatter for the whole team while still letting an individual
package override the default line length if it genuinely needs to.
Workspace settings are stored in your project
A single-folder workspace's settings live in .vscode/settings.json inside
that folder; a saved multi-root workspace stores them directly inside the
.code-workspace file. Both are safe to commit to version control so your
whole team shares the same defaults.
Workspace Trust
The first time you open a folder you haven't opened before, Gunamaya asks whether you trust its authors before running any of its tasks, debug configurations, or workspace-defined extensions — a safeguard against opening a malicious repository and having it execute code without your consent. You can trust a folder permanently, trust it just for the current session, or restrict Gunamaya to a read-only mode for folders you don't trust at all. Manage previously-granted trust decisions from Manage Workspace Trust in the Command Palette.