NetStacksNetStacks

Modes & Permissions

How the AI panel's Mode (Auto Pilot / Overlord) and Permission (Ask / Auto / Go Nuts) selectors work, which tool calls need approval, and how to enable, disable or rename tools.

Overview

The input bar of the AI panel has two selectors that shape how the assistant behaves:

  • Mode (Auto Pilot / Overlord) — which tool set and default permission the agent starts with.
  • Permission (Ask / Auto / Go Nuts) — which tool calls you approve before they run.

Each mode has its own saved permission. The panel's picker and the Permission mode setting in Settings → AI → AI Tools edit the same value, so a change in either place sticks until you change it again.

AI panel input bar showing Auto Pilot mode, the provider and Auto permission

Both apply in standalone and enterprise mode. In the standalone Terminal neither one lets the assistant push configuration to a device — that requires AI Configuration Mode.

Agent Modes: Auto Pilot and Overlord

Auto PilotOverlord
Tooltip"Full access — all tools + bash, runs autonomously""Full access — all tools, asks before acting"
Default permissionAutoAsk
Local shell (run_bash)Yes (standalone)No
All other toolsSame tool set in both modes (subject to what you disable in Settings)

In practice: use Overlord when you want to review each command, and Auto Pilot when you want the agent to work through a task and also be able to run commands on your own machine (for example dig, curl or a Python script). Switching mode shows that mode's saved permission; the defaults are Auto for Auto Pilot and Ask for Overlord.

Local shell commands
The Bash / Shell tool runs commands on the computer running NetStacks (it needs bash; on Windows install WSL or Git Bash). Up to 10 commands per call, each with a timeout. A built-in deny list blocks destructive commands such as rm, sudo, kill, shutdown and dd, and you can add your own entries.

Permission: Ask, Auto, Go Nuts

PermissionWhat happens
AskEvery tool call needs your approval ("Approve every tool call before execution").
AutoReads run straight away; anything that changes state needs your approval ("Reads auto-execute, anything that changes state needs approval").
Go NutsEverything runs without approval ("Everything auto-executes — no approval needed"). The selector is highlighted as a warning.
Permission selector set to Go Nuts

Calls that need approval stop in an Approval Required card listing each call, its session or tool, and why it needs approval. Nothing from that turn runs until you click Approve (Approve All when there are several). Reject (or Stop) skips the pending calls and tells the agent you rejected them. The AI panel, the floating Ask AI chat and the inline AI popup all show this card.

Whatever the permission, the deny rules below stay in force. See Safety, Approvals & AI Configuration Mode.

Which Tool Calls Ask for Approval

In Ask, every tool call waits for you. In Auto, only calls that change state wait:

  • Device and shell commands that are not read-only (run_command, ai_ssh_execute, run_console_command, run_bash). Read-only commands such as show run straight away.
  • Calls to your API Resources with a method other than GET, HEAD or OPTIONS.
  • Tools that create or change something: saving documents and memories, creating or importing MOPs, writing details onto topology devices, importing topology from NetBox, LibreNMS or NetStacks-Crawler, onboarding devices, opening a console tab, starting background agent tasks, and writing, editing or patching remote files.
  • Every tool from an MCP server.

Reading scrollback, listing sessions, searching documents, lookups and navigation never need approval in Auto. If you don't want the assistant to use a tool at all, switch it off in AI Tools.

Calls That Never Run

Some calls are refused in every permission, including Go Nuts. They are not put to you for approval; the assistant is told why and can try something else:

  • A tool you have switched off for the current mode, or an MCP tool that is not enabled.
  • A device command that is not read-only while AI Configuration Mode is off.
  • A local shell command on the bash deny list.
  • Writing, editing or patching remote files while AI Terminal Mode is off.
  • Adding, removing or moving topology devices and connections while Allow AI to edit topologies is off.

Controller Approvals (Enterprise) Enterprise

When the Terminal is connected to a Controller, background SSH commands and the Controller's own AI tools also go through the Controller's permission check. If the Controller requires approval for a call, the same Approval Required card appears, with a reason that starts with Controller:, even if your own permission would have let the call run. The call runs once you approve it. An approval can be used once and expires after 10 minutes; if it expires, ask the assistant to try again. A call the Controller does not allow at all is reported as "Not permitted by the Controller".

Background Tasks

In the standalone Terminal, background agent tasks follow the same rules, using the Auto Pilot permission mode and the tools enabled for Auto Pilot. See AI Agents.

Choosing a Combination

SituationSuggested setting
Production devices, you want to see every command firstOverlord + Ask
Read-only investigation in the standalone Terminal, relying on the command filterAuto Pilot + Auto
Scripted lab work that also needs local shell commandsAuto Pilot + Auto
A planned change in a maintenance windowOverlord + Ask, plus AI Configuration Mode for 5 minutes

Enabling and Disabling Tools

Open Settings → AI and scroll to AI Tools. The header shows how many tools are enabled.

Settings, AI, AI Tools section with Auto Pilot and Overlord tabs, mode name fields and tool categories
  1. Pick the mode tab (Auto Pilot or Overlord). Each mode has its own settings.
  2. Set Permission mode (Ask, Auto or Go Nuts) for that mode. This is the same setting as the panel's picker.
  3. Use a category switch to turn a whole category on or off, or expand the category and tick individual tools.
  4. Changes apply to the next tool call.

Categories: Core Session Tools, Document Tools, Session Context, Change Control, Network Lookups, Neighbor Discovery, Topology Enrichment, NetBox Integration, LibreNMS Integration, NetStacks-Crawler Integration, MOP Management, AI Memory, Background Agents, Integrations, Remote File Operations, Bash / Shell, OOB Console. The OOB Console tools are off by default.

  • The Bash / Shell tool is only ever offered in Auto Pilot.
  • Remote File Operations are only offered when AI Terminal Mode is enabled (see AI Terminal Mode).
  • Topology editing tools (add, remove, move devices and connections) also require Allow AI to edit topologies in AI Automation.

Renaming the Modes

In AI Tools, the Mode 1 name and Mode 2 name fields rename Auto Pilot and Overlord. The new names appear in the panel's Mode selector, in Settings → Prompts and in the instructions sent to the model.

Bash Command Deny List

Below the tool list, Bash Command Deny List extends the built-in deny list ("rm, sudo, kill, shutdown, chmod, …"). Type a command name (for example wget, nc) and click Add. With no entries the list reads "No custom deny entries — using built-in deny list only".

Bash Command Deny List, AI Overlord provider settings and the start of AI Memory

Mode Prompts

Each mode has its own editable instructions under Settings → Prompts → System Prompts → AI Modes. Editing them changes the tool guidance the agent receives; the built-in safety rules and NetStacks platform knowledge are always added and cannot be edited. See System Prompts.