Permissions & safety
Syntic Code can read, write and run things on your computer, so it has several layers that keep you in control. You choose how much to hand over; the layers below are always there.
| Layer | What it does | Read more |
|---|---|---|
| Permission modes | Set the overall stance: ask for everything (default), let edits through (auto-edit), plan only, or run routine work on its own (auto). | Permission modes |
| Rules | Allow, ask about or block specific tools and commands, per project or for you. | Permission rules |
| Auto mode checks | In auto mode, risky actions (deleting outside the project, pushing, publishing, touching credentials) still stop for your OK. | Auto mode |
| Folder trust | You are asked once per folder at start. A new folder’s own settings, hooks, MCP servers, agents and skills stay off until you trust it; a trusted folder starts in auto-edit. | Folder trust |
| Outside changes | git push, cluster, cloud, production-deploy and remote-database commands never run unattended in auto mode, and their prompt names the target. | Commands that reach outside |
| File safety | The agent must read a file before changing it, and cannot overwrite changes it has not seen. | Safety nets |
| Shell sandbox | Optionally run every agent command inside the operating system’s sandbox. | Shell sandbox |
| Checkpoints | Every file edit is backed up so you can rewind files, the conversation, or both. | Checkpoints & rewind |
A sensible setup
- Keep the default of auto mode for your own projects, or switch to default mode if you want to approve each change.
- Add allow rules for the safe commands you run all the time (your test and lint commands).
- Add deny rules for things that must never happen (reading
.envfiles, fetching from certain hosts). - Use plan mode before large changes.
- Turn on the sandbox when working on code you do not fully trust.
Where to go next
| Task | Page |
|---|---|
| Pick a mode, or understand what one does | Permission modes |
| Write allow, ask and deny rules | Permission rules |
| Decide which folders to trust | Folder trust |
| See which commands count as reaching outside your machine | Commands that reach outside |
| Fence commands in with the operating system | Shell sandbox |
| Tune auto mode for a team | Configure auto mode |
| Understand the overall safety model | Security |
Organizations can enforce any of this for every user with organization policy.