Managing VS Code Workspace Trust for Secure Development

Preventing Arbitrary Code Execution in Untrusted Folders

Opening a repository from an external source can inadvertently trigger malicious code via .vscode/settings.json, tasks.json, or extension-driven automation. VS Code Workspace Trust solves this by disabling high-risk features—such as task execution, debugger launch configurations, and certain extension activations—until you explicitly verify that the folder's authors are trusted.

How Workspace Trust Operates

When you open a folder, VS Code checks a local database of trusted paths. If the folder is not recognized, it enters Restricted Mode. In this mode, you can still read and edit files, but the editor blocks any action that could execute code on your machine without your knowledge.

Configuring Trust Behavior

While Workspace Trust is enabled by default, you can customize how the editor prompts you when opening new projects. These settings are applied at the user level and affect all workspaces.

To modify these behaviors, open the Command Palette (Ctrl+Shift+P or Cmd+Shift+P) and select Preferences: Open User Settings (JSON). Add or modify the following configurations:

{
  "security.workspace.trust.startupPrompt": true,
  "security.workspace.trust.banner": "warning"
}

• security.workspace.trust.startupPrompt: When true, VS Code asks if you trust the authors immediately upon opening an untrusted folder.
• security.workspace.trust.banner: Controls the visibility of the trust status banner at the top of the editor window.

Practical Example: Granting and Managing Trust

Consider a scenario where you clone a public utility library to inspect its source code. Upon opening the folder, VS Code displays a banner stating the folder is untrusted.

1. Initial State: You notice that the Run button in the debugger is disabled and tasks.json entries do not appear in the Task runner.
2. Granting Trust: Click the Trust button in the banner or run Workspaces: Manage Workspace Trust from the Command Palette. Select "Yes, I trust the authors".
3. Result: VS Code updates its local database. The debugger is now active, and custom tasks can be executed.
4. Revoking Trust: If you later determine the repository is unsafe, return to Manage Workspace Trust and remove the folder from the Trusted Folders & Workspaces list.

Limitations and Common Engineering Pitfalls

Workspace Trust is a client-side security boundary, not a project-level configuration. This leads to several common misunderstandings:

Misconception	Technical Reality
Trust settings can be committed to Git.	Trust decisions are stored in a local machine database. They do not travel with the code and cannot be shared via .vscode/settings.json.
Restricted Mode blocks all extensions.	Only extensions that require trust to execute code are disabled. Basic syntax highlighting and linting usually remain active.
CI/CD pipelines are affected.	Headless environments (like GitHub Actions) do not use the GUI trust prompt, but automation should not rely on workspace-specific tasks for security reasons.

Verification and Diagnostics

To verify the current trust state of your active window without using the GUI banner:

• Check Status: Look for the Restricted Mode indicator in the bottom-right status bar.
• Command Check: Run Developer: Toggle Workspace Trust from the Command Palette to see the current state and quickly switch modes.
• Audit Trusted Paths: Navigate to Manage Workspace Trust to see a comprehensive list of all directories currently marked as trusted on your system.