Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.265 ·

Workspace trust plumbed into init config and SDK session request

Workspace trust status is now passed into session setup and checked against trusted network directories

Under the hood No documentation found Internal Changes
JSON All of v2.1.265
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Workspace TrustArea: what it touches
Internal ChangesKind: in v2.1.265,
Internal ChangesSection of the release

Unclear What happens as a result of this workspace-trust check (e.g. what gets blocked or warned) is not stated.

What

A workspaceTrust setting from init configuration is now passed through to session setup, where it's used to run a new workspace-trust check. That check considers the current working directory, a list of trusted network directories, and storage state, and runs during setup when the host owns the terminal's standard input.

Why

This threads workspace trust information deeper into session initialization, likely as part of deciding what a session is allowed to do in an untrusted workspace, though the finding doesn't specify the effect of the check's result.

Read from
Names in the bundleworkspaceTrust
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat happens as a result of this workspace-trust check (e.g. what gets blocked or warned) is not stated.

See this entry in the whole of v2.1.265 →

Feedback