Claude Code can block writes outside working directories. What still needs checking?
The collected summary describes a new write restriction in Claude Code v2.1.314. Establish which working directories may be changed and check that the setting applies; this restriction alone says little about other operations.
What to consider
Define the directories that may be changed, then use disposable samples to check writes inside and outside them. The collected summary says Claude Code v2.1.314 adds permissions.blockWritesOutsideWorkingDirectories to reject out-of-directory writes in every permission mode. That is a useful control to examine, but the summary does not establish its default state, full setup steps or restrictions on other actions. It does not establish isolation of the whole computer.
Match the permitted directories to the actual project
Establish where the agent runs and which project copy it should change. Record the working directory, commit and existing changes, then define the files in scope. Matching folder names do not establish that local, remote and backup copies contain the same code.
A write-path restriction does not define project scope for you. If the permitted directory is broader than the task needs, specify which contents may change and which existing edits must remain. Keep that scope statement with the configuration so the control has an understandable boundary.
Check the saved setting and the enforced restriction separately
In an isolated sample, prepare one file within scope and another outside it, then compare action responses with the actual files. Keep the sample separate from everyday material so an unexpected write is disposable. These are proposed checks; this article did not run the release or verify enforcement.
The setting’s name in a file does not establish that the active process has loaded it. Record the version, entry point, directories and results, marking unfinished checks clearly. The summary supplies no full setup guide, so this article does not guess configuration paths or installation commands.
Review changes within the allowed directory against the task
Even with out-of-directory writes blocked, changes inside the directory still need review. After a small task, inspect the diff, relevant tests and deliverables for unrelated work or overwritten edits. Explain any need to change something outside scope before broadening the working area.
Include the setting in write-control checks for coding tasks without inferring permissions for reading, networking or sending messages. The factual basis is the collected release summary only. No bypass testing was performed, and the setting is not presented as a verified security guarantee.
Source links
The links below were supplied with the collected records. This article offers independent analysis of their summaries; we have not individually checked the original sources or tested the products.