freeze

To restrict file edits to a specific directory during debugging, you can apply a session-scoped freeze boundary that blocks any modifications outside the allowed path. This prevents accidental scope bleed while you work.

Yes, you can lock edits to a single folder to prevent accidental changes elsewhere by setting a directory boundary. The restriction persists for the entire session and can be changed or cleared as needed.

A directory boundary blocks scope bleed by using a pre-tool hook to intercept and prevent edit operations outside the specified path. The boundary is stored in a state file to persist the restriction throughout the session.

Yes, you can still run other tools while edits are frozen to a specific module. The restriction specifically blocks edit operations outside the boundary while allowing other debugging and analysis tools to operate normally.

The best way to scope code fixes to a single module without affecting other files is by applying a session-scoped freeze boundary. This enforces boundary-controlled editing by blocking any modifications outside your designated directory.

You should not use a directory freeze boundary when your task requires modifying files across multiple modules simultaneously. The boundary blocks all edits outside the specified directory, which will prevent cross-directory refactoring or updates during that session.