freeze

To restrict file edits to a specific directory, you establish a per-session edit boundary using a PreToolUse hook. This automatically blocks Edit and Write operations outside your chosen path, preventing accidental cross-project changes while debugging.

Per-session edit boundaries limit file modifications to a single user-chosen directory for the duration of an interactive session. You need them when focusing on a single module or debugging to prevent accidental writes to other project paths.

You set up an edit boundary by specifying your target directory through a guided prompt. Once designated, a shell script runs to establish the boundary, automatically enforcing write restrictions before any edit or write action occurs.

Yes, the edit boundary blocks both Edit and Write operations outside the saved path. The PreToolUse hook intercepts these actions automatically and returns a clear denial message if the target file is outside the boundary.

Yes, you can isolate changes by locking edits to a session directory. This restricts writes to your specified folder without altering your underlying project structure, ensuring modifications remain contained during interactive development.