freeze

You can restrict file edits to a specific directory by setting a session-scoped boundary that blocks write operations outside the allowed path. This prevents accidental changes to unrelated code while leaving reads unaffected.

An edit boundary is a persisted restriction that confines write operations to one allowed folder. It prevents code drift by warning and blocking any Edit or Write attempts that target files outside the specified directory.

Yes, you can still read files outside the freeze boundary. The restriction only applies to Edit and Write operations, leaving reads and other operations unaffected while you work within the allowed directory.

Yes, the directory edit block persists across the session. The boundary state is saved so that your configured restrictions remain active and continue to guard critical areas until you change or remove them.

The best way to prevent accidental writes to unrelated modules is to enforce a session-scoped edit boundary. This approach blocks out-of-scope changes at the tooling level, which is safer than relying on manual checks during module-specific work.

Your edits are being blocked because an active edit boundary is restricting writes to a specific directory. You must either move your work into the allowed folder or update the boundary path to include the target directory.