Terminal permissions and safety
A terminal can modify files and external systems, so its effective authority should match the task’s workspace and risk.
On this page2
Steps
- Confirm the project root, branch, and account or environment before running a command.
- Prefer read-only inspection and narrowly targeted paths before mutation.
- Review commands requested by an approval card, especially pipes, redirects, installers, and remote actions.
- Keep secrets out of transcripts and verify destructive or production changes directly.
Expected result
Commands run with deliberate scope and leave an auditable result that can be checked or recovered.
Note: Full Access can extend agent authority beyond the workspace; it does not make an unsafe command reversible.