Permissions

Docs › Core Features › Permissions

Permissions

Permission modes decide what NOVA may do without asking you first. Pick the level that fits the job, and change it any time.

The five modes

ModeEdits filesRuns commands
planNever. It only proposes a plan.Never
ask (default)Asks firstAsks first
editsYesAsks first
overdriveYesYes. Still asks before writing outside the project.
autoYesYes, including outside the project

Change the mode

Inside NOVA:

nova
\mode edits

Type \mode on its own to see the current mode. Or press Shift+Tab to cycle through ask → edits → auto.

For a one-off run from a script:

bash
nova -p "Fix the lint errors" --permission-mode acceptEdits

In settings and with nova -p, the edits mode is written acceptEdits.

To set a default for a project, see Settings.

What always asks

In every mode, NOVA stops and asks before it:

  • deletes files
  • installs software onto your computer
  • commits or pushes with Git, or rewrites history
  • deploys
  • opens files that hold secrets, such as .env

In plan mode, these are refused.

Note: auto mode needs NOVA to save undo checkpoints in your project. If it can't, NOVA tells you and suggests edits instead.

Answering a request

When NOVA asks, it shows exactly what it wants to do. Before you say yes:

  1. Read the command or file paths.
  2. Check nothing unrelated is included.
  3. Approve only what you intended. If in doubt, say no and narrow the task.

If you choose "allow always", NOVA remembers it for this project on this computer only.

Allow and deny lists

You can pre-approve or always block specific commands in Settings:

.nova/settings.json
{
  "permission": {
    "allow": ["git status", "pytest*"],
    "deny": ["rm*"]
  }
}

A deny always wins over an allow.

Join our Discord

Chat with our engineers and become part of the active NOVA developer community.

Join Discord

Need help?

Open an issue on GitHub or email support@bridgeye.com.

Get help
Bridgeye • Autonomous Software Engineering.