Departments

Each member of a department is an existing marketplace agent, bound to a role and given an alias that teammates address it by. Because every agent exposes typed, invocable tools, one member can call another as a tool — that typed tool input/output is the message contract between agents.

You wire members together with one of three patterns:

• Pipeline — members run in order, each output feeding the next.
• Hub-orchestrator — a designated hub member delegates to the others and synthesizes their results.
• Peer-to-peer — any member may message any member (full mesh). Each request is handled first by the entry member you choose (the first member by default).

Aliases must be unique within a department, a hub-orchestrator must name a hub member, and any explicit comms edge must connect two declared members.

A department can carry a standing reporting instruction from its owner — tone, format, what to always include or leave out. It is added ahead of every member's own prompt at run time, so the whole team reports the way you want without editing any member agent. It is treated as owner configuration (never as the user's request), and it is scanned for leaked secrets and injection attempts when you save.

If your members recognize named flows — say a request classifier that returns a flow like reproduce-then-fix — a department can declare a flows map naming which members serve each flow. The runtime surfaces those members as a hint in the teammate tool descriptions so the team knows who to involve for a given flow. It is a hint only — it never forces routing, and every member's own guardrails still apply. Author it in the department manifest:

"flows": {
  "reproduce-then-fix": ["quality_engineer", "code_builder", "code_reviewer"]
}

The no-code builder lets you pick members, assign roles and aliases, choose a topology, and save the team:

Download a department by slug, then run it as one MCP server. This is the path available today; running a department on FindAgent's own infrastructure is being tested and is not open yet.

npx @findagent/cli download growth-crew-a1b2c3

That writes the department bundle locally. The @findagent/mcp runtime then exposes the whole team as a single MCP server your client connects to:

npx @findagent/mcp run-department ./growth-crew-a1b2c3

From your client's perspective the department is one server — the runtime handles the agent-to-agent routing internally according to the topology you built.