freeze

You can lock edits to a specific directory by providing the folder path when prompted. This sets a persistent boundary that blocks file modifications outside that directory for the current session.

Yes, you can restrict code changes to one folder while debugging by applying a directory boundary. This ensures subsequent edits remain scoped to that specific module until the boundary is explicitly cleared.

The directory boundary mechanism works by using a PreToolUse hook and a Bash helper. It reads a persistent state file to check the specified directory and denies any operations attempted outside that boundary.

Yes, the folder lock persists across multiple edits within the same project session. The boundary remains active for all subsequent edits until you explicitly clear it, ensuring continuous scope isolation.

You should restrict file modifications to a specific directory scope when debugging or making scope edits to a single module. This prevents accidental changes from spreading across the broader project files.

The folder boundary limitation is that it only applies within Claude Code sessions for the current project. It blocks edits outside the specified directory but requires explicit clearing to remove the restriction.