Junie Brave Mode and Action Allowlist: Auto-Approve Commands in Junie CLI

• Off: Junie asks before every sensitive action that is not on the allowlist.
• Auto: a safety check approves terminal commands it thinks are safe and still asks about risky or unknown ones.
• On: Junie runs all sensitive actions without asking.

Cycle levels with the /brave slash command or Ctrl+B. Brave preferences are stored separately for sandboxed and non sandboxed sessions.

{
  "brave": true
}

junie --brave
junie --sandbox

--sandbox starts Junie in sandbox mode, which lets you use brave mode with less risk. Sandbox mode is only in development, nightly and experimental builds and is not supported on Windows.

Junie CLI reads allow rules from ~/.junie/allowlist.json. You can edit it by hand.

{
  "defaultBehavior": "ask",
  "allowReadonlyCommands": true,
  "rules": {
    "executables": {
      "rules": [
        { "prefix": "git", "action": "allow" },
        { "pattern": "grep **", "action": "allow" },
        { "pattern": "npm [iur]*", "action": "ask" }
      ]
    }
  }
}

• Action types: fileEditing, executables, mcpTools, readOutsideProject, readSecretFile.
• Each rule has a prefix or a pattern, plus action set to allow or ask.
• prefix matches commands that start with that text.
• pattern uses glob syntax: * (no /), ** (any characters including /), ? (one character), [abc] and [!abc].

• Rules run top to bottom and the first match wins. Put an npm install * ask rule above an npm allow rule to keep installs gated.
• Each part of a && chain is checked and all must be allowed.
• Substitutions like $(...) and backticks are checked at any depth.
• Multi line commands always ask.

The plugin settings have an Action Allowlist page with Terminal rules, MCP rules and other rule types, an Add button, and a Check Command button to test a command against your rules.