Claude Code sandbox and permission safety guide

Permissions should match consequence

A read-only repository review and a production migration should not share the same authority. Start with the narrowest access that can complete the task. Expand only when a concrete blocked action is understood and the scope remains acceptable.

Protect the irreversible seams

Credentials, production databases, package publication, git history rewrites, and broad deletion need explicit review. Never paste secrets into prompts or logs. Prefer dry runs, previews, backups, and commands limited to the named resource.

• Inspect proposed commands.
• Keep unrelated dirty files intact.
• Use environment-native secret loading.
• Verify external state after authorized writes.

Review generated code as untrusted input

Passing tests reduce risk but do not prove security or product correctness. Read authentication, billing, data migration, and shell-script changes closely. The owner remains responsible for the shipped result.

Primary sources

Provider terms and product behavior can change. Confirm plan, pricing, model, and permission details in the current official documentation.

• Claude Code security

Questions