guard

To restrict file edits to a specific directory, you can define an edit boundary that limits modifications to a single user-specified path. This prevents accidental changes to critical files outside the designated boundary during maintenance.

The best way to add safety guardrails for debugging production systems is to enforce simultaneous destructive-command warnings and per-directory edit restrictions. This approach ensures dangerous commands are intercepted and file modifications stay within safe limits.

You can configure edit boundaries through a guided setup prompt that asks for your target directory. The specified boundary is then stored in a local state file for persistence, eliminating the need for manual configuration file management.

You should enable per-directory edit restrictions during any operation requiring guardrails to prevent accidental changes, such as production maintenance or debugging prod systems. This ensures modifications remain confined to your designated safe zone.

Destructive command warnings and edit boundaries work simultaneously by intercepting dangerous commands like force-push while restricting file modifications to a predefined directory. This dual approach provides comprehensive protection against accidental or dangerous changes.