Claude Code for VS Code Now Asks You to Trust a Folder Before the First Session

Claude CodeView original changelog

The Claude Code VS Code extension in 2.1.323 adds a trust prompt before the first session in a folder the user has not trusted. Declining leaves the folder's settings and MCP servers unused.

Key Takeaways

  • A trust prompt now appears before the first session in an untrusted folder in VS Code.
  • Declining leaves the folder's settings and MCP servers unused.
  • Repository settings can no longer disable user hooks in untrusted folders.
  • The same limit applies to self-hosted runners under --trust-workspace false.
  • An untrusted checkout can neither add MCP servers nor switch off protections.
  • It shipped in Claude Code 2.1.323.

Trust prompt

Before the first session in an untrusted folder, the VS Code extension now shows a Claude Code trust prompt. If the user declines, the folder's settings and MCP servers are not used, so opening an unfamiliar repository no longer silently adopts whatever it configures.

Repository settings lose their reach

A related change makes VS Code sessions in an untrusted folder, and self-hosted runners under --trust-workspace false, stop letting the repository's settings disable the user's hooks or turn plugins on or off. Together the two changes mean an untrusted checkout can neither supply its own MCP servers nor switch off protections the user put in place.