freeze

To restrict file edits to a specific directory, you can use a pre-tool hook to lock edits within a user-defined boundary, preventing unintended changes to files outside that scope during your session.

Using an edit boundary when debugging code in a shared workspace prevents accidental modifications to unrelated files, ensuring that changes remain safely contained within your intended directory scope.

Yes, you can use a shell-script pre-tool hook to enforce workflow safety by storing a stateful boundary in your environment that blocks any edits attempted outside the specified directory.

Yes, you need git and python3 installed in your environment to run the shell-script hooks that manage the stateful boundary and enforce scoped edits during your interactive session.

The best way to lock edits to a single folder while prototyping is to define a stateful boundary and apply a pre-tool hook that actively blocks any modifications attempted outside that chosen directory.

Directory-scoped edit restrictions apply only to the current session and rely on a stateful environment boundary, meaning the lock is not persistent across new sessions and requires reconfiguration.