freeze

To restrict edits to a specific directory, you set a runtime boundary that blocks Edit and Write operations targeting paths outside that directory, preventing accidental changes during development workflows.

Directory restriction creates an edit boundary that blocks write operations outside a specified path. You should use it during debugging and development workflows when changes need to be confined to a single module to prevent unintended modifications elsewhere.

Yes, you can block write operations outside a specific directory by storing a runtime boundary. This boundary intercepts Edit and Write operations, preventing any file modifications from occurring outside the allowed directory path.

You set up an edit boundary by specifying a target directory to freeze, which stores a runtime boundary for the session. This restricts edits to that specific directory, confining all changes to the single module you are debugging.

Restricting edits to a directory requires no additional dependencies, as it operates by storing a runtime boundary that blocks Edit and Write operations outside the allowed path. It functions independently without needing external shell hooks or components.

The limitation of confining edits to a directory is that the boundary only applies for the duration of the session and exclusively blocks Edit and Write operations. It does not prevent read access or modifications made through external tools outside the established runtime boundary.