Every agent in Agent Studio belongs to one of a defined set of categories, fixed the moment it’s created. The category decides how much you can customize it, which guardrails apply, and who’s allowed to touch its behavior.
Skills authoring lives here too: teach NetBrain’s agents your network’s own language, no model retraining needed. Automation Tools covers the authoring workflow and Skills Assistant in full.
Administrators hold one guardrail that no agent configuration can override. Put a device in Excluded devices, and its sensitive data, Config, CLI, and NCT, never reaches the LLM. This is enforced at the tool level, not through agent-specific settings.
Your team defines agent behavior, authors runbooks and network goals, configures skills, and sets the access guardrails every agent operates within.
A System Agent is one of the core agents NetBrain ships, with a locked description and system prompt. A Custom Agent is one your team builds from a baseline, fully editable.
An administrator-controlled boundary. Once a device is placed in Excluded devices, its sensitive data, Config, CLI, and NCT, never reaches the LLM, enforced at the tool level rather than through any per-agent setting.
Yes, as Custom Agents or Function Agents, starting from a baseline you fully control.