phil65 / agentpool
A unified agent orchestration hub that lets you configure and manage multiple AI agents (native, ACP, AGUI, Claude Code) via YAML, and exposes them through standardized protocols (ACP/OpenCode Server).
View on GitHubAI Architecture Analysis
This repository is indexed by RepoMind. By analyzing phil65/agentpool in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.
Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.
Embed this Badge
Showcase RepoMind's analysis directly in your repository's README.
Repository Overview (README excerpt)
Crawler viewAgentPool **A unified agent orchestration hub that lets you configure and manage heterogeneous AI agents via YAML and expose them through standardized protocols.** Documentation The Problem You want to use multiple AI agents together - Claude Code for refactoring, Codex for code editing with advanced reasoning, a custom analysis agent, maybe Goose for specific tasks. But each has different APIs, protocols, and integration patterns. Coordinating them means writing glue code for each combination. The Solution AgentPool acts as a protocol bridge. Define all your agents in one YAML file - whether they're native (PydanticAI-based), direct integrations (Claude Code, Codex), external ACP agents (Goose), or AG-UI agents. Then expose them all through ACP or AG-UI protocols, letting them cooperate, delegate, and communicate through a unified interface. Quick Start Minimal Configuration Integrating External Agents The real power comes from mixing agent types: Now can delegate work to any of these agents, and all are accessible through the same interface. Key Features Multi-Agent Coordination Agents can form teams (parallel) or chains (sequential): Rich YAML Configuration Everything is configurable - models, tools, connections, triggers, storage: Server Protocols AgentPool can expose your agents through multiple server protocols: | Server | Command | Use Case | |--------|---------|----------| | **ACP** | | IDE integration (Zed, Toad) - bidirectional communication with tool confirmations | | **OpenCode** | | OpenCode TUI/Desktop - supports remote filesystems via fsspec | | **MCP** | | Expose tools to other agents | | AG-UI | | AG-UI compatible frontends | | OpenAI API | | Drop-in OpenAI API replacement | The **ACP server** is ideal for IDE integration - it provides real-time tool confirmations and session management. The **OpenCode server** enables the OpenCode TUI to control AgentPool agents, including agents operating on remote environments (Docker, SSH, cloud sandboxes). Additional Capabilities • **Structured Output**: Define response schemas inline or import Python types • **Storage & Analytics**: Track all interactions with configurable providers • **File Abstraction**: UPath-backed operations work on local and remote sources • **Triggers**: React to file changes, webhooks, or custom events • **Streaming TTS**: Voice output support for all agents Usage Patterns CLI Programmatic Documentation For complete documentation including advanced configuration, connection patterns, and API reference, visit phil65.github.io/agentpool.