guard

Destructive command warnings are always on to prevent risky commands like rm -rf or DROP TABLE from executing. The guard mode intercepts these dangerous actions during live debugging and local sessions, enforcing safety checks before any damage occurs.

Edit boundary enforcement restricts file edits to a user-specified directory boundary during production debugging. This prevents unauthorized edits and risky modifications from affecting critical systems outside the designated safe zone.

To activate guard mode for combined safety protections, set a freeze boundary for edits, then type /guard. This works in tandem with /careful and /freeze integrations to provide end-to-end safety across your local sessions and live debugging scenarios.

Guard mode operates without additional dependencies or components, relying solely on its internal safety check logic. It enforces guard rules through the /careful and /freeze integrations and stores the freeze state in a deterministic location.

Force-push triggers a warning during a local session because destructive command warnings are always on. The system intercepts force-push and similar risky operations to enforce safety checks before they can impact your repository.

Edit boundary enforcement should not be used when you need to make edits across multiple directories outside the user-specified boundary. The restriction prevents any modifications outside the defined safe zone, which limits cross-directory workflows.