Security & Isolation
Learn how December protects your code, files, and API keys.
This page tells you how December protects your code, your files, and your API keys.
Security & Privacy Model
1. Safety in the CLI
- Trust prompt: The first time you run
decemberin a folder, December asks if you trust it. If you say no, December stops. - Project folder only: File tools work only inside your project folder. To let December open files outside it, turn on Non-Workspace Access in
/settings. - PathGuard: December blocks system folders such as
/etcand/usr, and private key files such as~/.sshand.pemfiles. December asks you before it reads a secrets file such as.env. - Approval for destructive commands: December asks you before it runs a command such as
rm -rf,git reset --hard, orgit push --force. - Stop and undo: Press
Ctrl + Cto stop December. Type/undoto revert the last turn.
If you run December with -y or --print, December approves tool calls without asking. Use these flags only in folders you trust.
2. Sandboxes in December Cloud
- One sandbox per session: Each December Cloud session runs in its own sandbox, not on your computer.
- Active limit: You can have 3 active sandboxes. If you start a fourth, December pauses the one you used least recently.
3. API keys
- Direct requests: If you use your own keys, the CLI sends requests straight to the model provider.
- Local storage: The CLI saves your keys in
~/.december/config.json. Only your user account can read this file (file mode600).