guard

Prevent accidental destructive commands during production debugging by activating a safety layer that warns before risky operations like rm -rf or DROP TABLE and restricts edits to a user-specified directory.

Yes, you can restrict file edits to a specific directory boundary during maintenance by specifying your target path, which blocks any unintended changes to critical assets outside that chosen directory.

An edit boundary protects production systems by enforcing a safe operating perimeter around a chosen directory, validating tool use through pre-tool hooks to block modifications outside that path.

Yes, this safety layer warns before force-push attempts and database drops by intercepting destructive commands during active work on production systems to reduce the risk of accidental damage.

Start using guard mode for maximum production safety by specifying which directory to restrict edits to, which activates the warnings and edit boundary enforcement for your maintenance session.

You should not rely solely on an automated edit boundary when performing broad system migrations outside the chosen path, as the safety layer specifically restricts edits to a single user-specified directory.