Node Types¶
Nodes are the core building blocks of AgentPool. This section covers the different types of nodes you can configure: agents (individual AI workers) and teams (coordinated groups).
Agents¶
Native Agents¶
Native agents are the using regular client APIs of AI model providers and are backed by Pydantic-AI.
ACP Agents¶
ACP (Agent Communication Protocol) agents integrate external coding agents like Claude Code, Gemini CLI, Codex, and many others. These run as separate processes and communicate via the ACP protocol. This means that AgentHub can act as a ACP bridge: ACP-Agents are connected to the AgentPool via ACP, can use some of its extended featureset and then also be controlled by the User via a UI ACP client such as Zed or Toad.
AG-UI Agents¶
AG-UI agents connect to remote HTTP endpoints implementing the AG-UI protocol, enabling integration with any AG-UI compatible server.
Claude Code Agents¶
Claude Code agents provide native integration with the Claude Agent SDK. While Claude Code can also be used via the ACP bridge, this direct integration offers lower latency, tighter integration, and the ability to expose AgentPool's internal toolsets to Claude Code via MCP.
Teams¶
Teams coordinate multiple agents to work together on complex tasks:
- Parallel teams: Members execute simultaneously
- Sequential teams: Members execute in sequence, passing results along
- Nested teams: Teams can contain other teams for complex workflows
Quick Comparison¶
| Feature | Standard Agent | Claude Code Agent | ACP Agent | AG-UI Agent | Team |
|---|---|---|---|---|---|
| Runs in-process | Yes | Yes (SDK) | No | No | Yes |
| Full configuration | Yes | Yes | Limited | Limited | Yes |
| External tools | Via toolsets | Built-in + MCP bridge | Built-in | Via server | Via members |
| Streaming | Yes | Yes | Yes | Yes | Yes |
| Use case | Primary agents | Coding tasks | External agents | Remote services | Coordination |