Cline Auto-Approve and Checkpoints Policy

Look forRead project files on, and edits, commands, browser, and MCP off until there is a reason, as Cline's documentation recommends. One engineer who still approves each step after two years of daily use reports better results and lower token spend.

Look forExecute safe commands only. The model tags each command as safe or not, and the CLI has no allow or deny list for shell commands. One user found git commit --amend ran as a safe command, and a team found Cline ran an eval of a base64 payload hidden in fetched content with only safe commands approved. Keep Execute all commands off on shared machines. To block specific commands in the CLI, add a PreToolUse hook that cancels them, as Cline's CLI reference describes.

Look forEdit project files without Edit all files, so edits stay in the workspace. Keep configuration, CI, and dependency changes on manual approval, as one architect's policy does.

Look forCheckpoints on, their default. After each tool use, Cline commits the project files to a shadow Git repository kept apart from your own history, and offers Restore Files, Restore Task Only, or both. Cline notes they can slow very large repositories, so measure before you turn them off.

Look forThe CLI's global auto-approve defaults to on, except in ACP mode, where it defaults to off. Pass --auto-approve false for interactive use, and run unattended jobs only on a clean branch in an isolated environment.

Look forYOLO mode only in throwaway or sandboxed environments, as Cline's own guidance says. YOLO approves every action, including the switch from Plan to Act. No product enforces the organization setting yet, so name an owner for the rule.