Artifact database reads and writes now honor the setting that confines file access to your working directories.
The artifact database tool's file-backed reads and writes (db_op paths, file_path resolution) now route through the same working-directory checks as other file access, so blockReadsOutsideWorkingDirectories also constrains which local files can be used as data sources or destinations for artifact database operations. The read/write sub-tool is only enabled when its gating check returns true.
tengu_umber_lattice Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.257: off
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.257. It isn't a statement about your account. What a flag value here can and cannot tell you
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
When you set it in a project's `.claude/settings.json` or `.claude/settings.local.json`, Claude Code honors it under the same [workspace trust rule as hooks in settings files](/docs/en/permissions#what-runs-before-you-trust-a-folder). Whil…memory see the edit
* Fixed Bash commands with two directory changes, a subshell, or a `cd`+`git` chain skipping the prompt under `permissions.blockReadsOutsideWorkingDirectories` in bypass and auto modechangelog see the edit
Anthropic's documentation has since written up blockReadsOutsideWorkingDirectories, on Claude Code changelog.