Skip to content
Commandr

Project commands

Commandr won’t run anything in your project until you say so.

Off until you allow it

Package scripts, installing dependencies and app previews are blocked until you turn on Allow project commands in Project settings → Folder and confirm.

The permission belongs to that folder. It resets when you choose a different folder, and doesn’t carry over to copied projects. Turning it off stops the preview and blocks new commands; scripts already running finish.

What needs it

How commands run

Commands run in a macOS sandbox. They can change the project and their own temporary folders, but not the rest of your files or Commandr’s own data. Check, Test, Debug and Sync run scripts with read-only access to the project.

Build and test scripts can’t reach the internet. Previews only accept connections from your Mac and can’t make outside requests, so an app that needs an outside API or a local database won’t work in the preview yet.

Installing packages can reach the internet and read your project’s files, including any secrets stored in it. The sandbox lowers the risk but can’t make untrusted code safe in every case, so only allow commands for projects you trust.