You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Workspace TrustArea: what it touches
ImprovementsKind: in v2.1.281,
ImprovementsSection of the release
What
Claude Code asks you to trust a folder before working in it, and it remembers when you accepted (hasTrustDialogAccepted). The check that looks this up changed:
The walk up through parent folders now returns the path of the trusted folder, or nothing, instead of just yes or no. A new helper tells callers which project path is trusted.
An early step that trusted the workspace unconditionally in some cases has been removed.
The workspace-trust check CI now uses this helper and turns its answer into a true or false result. In the advisory branch that does not touch the file system, it now returns a proper true or false where it may have returned another value before.
Why
Most of this is internal. Because the unconditional bypass is gone, some kinds of session that were trusted automatically may now need real folder trust. Claude Code can also now say which parent folder's trust is being applied.
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 doubtThe finding does not say under what condition the removed shortcut applied.
