Permissions
Granular permission controls protect sensitive credentials, production secrets, and core system files from accidental modification.
Permission security model
By default, Plannix prompts for interactive user approval before running any shell command or modifying existing files outside your project root.
Policy enforcement levels
| Level | Behavior | Best For |
|---|---|---|
| Strict | Confirm every file write & bash command | Production repositories |
| On-Approval | Read tools automatic, write tools confirmed | Active local development |
| Autonomous | Full execution within isolated Docker sandbox | CI/CD pipelines |
Command & path allowlists
{
"allow": {
"commands": ["npm test", "npm run lint"],
"paths": ["src/**", "tests/**"]
},
"deny": {
"paths": [".env", ".env.*"]
}
}