Agent Library Overview

Where agents live: global, team, and flow scopes.

Agent Library

The Agent Library is the collection of agents across all three scopes of the architecture.

Scope by Directory

| Scope | Location | Reachability | |-------|----------|--------------| | Global (standalone) | agents/<name>/ | Directly delegatable | | Team-scoped | teams/<team>/agents/<name>/ | Through the owning team | | Flow-scoped | flows/<flow>/agents/<name>/ | Only as flow nodes |

Global Agents

Standalone agents in agents/ are the most reusable. They carry no state and can be delegated by name:

Mail("Explorer", "Find where restoreTabs is defined")

Give global agents a clear description and useWhen so the orchestrator routes to them accurately.

Team Agents

teams/<team>/agents/ holds agents that only make sense inside one project. They receive the team's rules.md and session context when activated. See Team.

Flow Agents

flows/<flow>/agents/ holds single-purpose workers for one pipeline. They must return structured JSON for node routing. See Flow.

Creating an Agent

  1. Create a directory at the right scope
  2. Add agent.json (name, description, tools, category)
  3. Add system.md with role, rules, and style
  4. Grant the minimum tools and MCP servers it needs

See Agent Config for the full schema.