Specialized Agents

nebflow ships with exactly three built-in agents — a deliberately small core. A specialized agent is not a new kind of thing to register: it is the same base agent, shaped for one job by the plugins assigned to it. One kernel, many capability shapes — instead of a growing shelf of preset personalities.

The three built-in agents

Agent	Role
Nebula	Your orchestrator — the single entry you talk to. Understands what you want, turns it into tasks, hands all execution to projects, keeps memory across sessions, and reports back
project-dispatcher	The project planner. Turns a task into a graph of nodes, wires the edges, and lets the graph do the coordinating
general	The base worker. Every task node runs on it with a fixed core toolkit; its assigned plugins add domain knowledge, not tools

All three share the same kernel, the same sandbox guarantees, and the same plugin protocol. They differ in role, not in kind.

Specialization is assignment, not configuration

• A task node runs on the general base. Give the node the right plugins and it becomes a specialist for that job — the plugin is the unit of specialization
• The orchestrator and the dispatcher coordinate rather than specialize — specialization happens where the work happens
• There is no per-domain agent to create and maintain. When your needs change, you change an assignment — not an agent definition

A worked example

explorer-toolkit is a real plugin that ships with nebflow — a capability pack made of two methodology skills:

• exploration-method — how to explore a codebase: enter through the front door, follow the call chains, and back every claim with file paths and line numbers
• solution-planning — how to turn findings into a plan: current state, direction, touched files, expected change, and acceptance criteria

Assign it to a node, and that node becomes an exploration specialist: same general base, but now it works with evidence-first discipline — every conclusion traceable, every plan verifiable. Assign design-spec instead, and the same base turns into a design reviewer. The specialist is the assignment.

Building your own

1. Write a plugin: a folder with a plugin.json manifest and a skills/<name>/SKILL.md that teaches one thing well — the format is on the plugin protocol page
2. Drop it into your plugins directory and install it from the plugin panel
3. Ask for work that needs it — your task dispatcher picks plugins from the catalog, per node

That's the whole loop. A plugin you write today is a specialist tomorrow — with nothing extra to install, register, or maintain.