AI Modes & Prompt Overrides
NetStacks AI runs in four modes — Chat, Operator, Troubleshoot, and Copilot — each tuned for a different task, with editable system prompts so you can adapt them to your environment.
Overview
The assistant is not a single chatbot — it runs in distinct modes. Each mode carries its own system prompt and tool posture so the model behaves appropriately for what you are doing, from asking a question to letting it drive a change.
The Four Modes
- Chat — ask networking questions and get explanations. No actions are taken on devices.
- Operator — the assistant proposes and, with your approval, executes commands to accomplish a goal.
- Troubleshoot — focused on diagnosing a problem: gather state, correlate symptoms, suggest fixes.
- Copilot — an in-session assistant that follows along and offers the next step or command as you work.
Modes that can act on devices route tool use through the same approval path as the rest of NetStacks — you stay in control of what runs.
Prompt Overrides
Each mode's system prompt is editable. From the prompt settings you can override the Chat, Operator, Troubleshoot, and Copilot prompts — and the context prompts used for topology and script generation — to encode your conventions, vendor mix, or guardrails. Overrides persist and apply on every request in that mode; clearing an override restores the built-in default.
Q&A
- Q: Which mode should I start in?
- A: Chat for questions, Troubleshoot when something is broken, Operator when you want the assistant to make a change with your approval, Copilot for hands-on work where you want suggestions inline.
- Q: Do prompt overrides change which provider is used?
- A: No. Overrides only change the instructions; provider and model are configured in LLM Configuration.
- Q: Can the AI run commands without me?
- A: Tool use that affects devices goes through approval. Review before you approve.