Per-Command and Per-Project Permissions

Per-command permissions:

Every command can be enabled or disabled according to your needs. Want the AI to create objects but not delete them? Done. Want to allow scene queries but block file writes? Done. You decide. The Tool Permissions panel in the Dashboard gives you a clear view of every available command and its current state.

Per-project permissions:

One project can allow broad experimentation while another stays far more restricted. That is especially important for studios, prototypes, and works in progress that carry different risk levels. A throwaway prototype might have everything enabled. Your main production project might restrict delete and file operations.

File system safety:

Dry-run defaults, protected paths, containment rules, and explicit execution boundaries keep file operations safer and more intentional. Protected paths like .git, Library, Temp, and Logs are permanently shielded. The AI cannot access them regardless of any other setting.