[ V5 - Multi-Agent Coding Workflow ] Specialized agents for different parts of the agent creation process
🔄 IMPORTANT UPDATE (March 20th): Archon now uses a multi-agent workflow with specialized refiner agents for autonomous prompt, tools, and agent definition improvements. The primary coding agent still creates the initial agent by itself, but then you can say 'refine' or something along those lines as a follow up prompt to kick off the specialized agents in parallel.
Archon is the world's first "Agenteer", an AI agent designed to autonomously build, refine, and optimize other AI agents.
It serves both as a practical tool for developers and as an educational framework demonstrating the evolution of agentic systems. Archon will be developed in iterations, starting with just a simple Pydantic AI agent that can build other Pydantic AI agents, all the way to a full agentic workflow using LangGraph that can build other AI agents with any framework. Through its iterative development, Archon showcases the power of planning, feedback loops, and domain-specific knowledge in creating robust AI agents.
-
The current version of Archon is V5 as mentioned above - see V5 Documentation for details.
-
I just created the Archon community forum over in the oTTomator Think Tank! Please post any questions you have there!
-
GitHub Kanban board for feature implementation and bug squashing.
Archon demonstrates three key principles in modern AI development:
- Agentic Reasoning: Planning, iterative feedback, and self-evaluation overcome the limitations of purely reactive systems
- Domain Knowledge Integration: Seamless embedding of frameworks like Pydantic AI and LangGraph within autonomous workflows
- Scalable Architecture: Modular design supporting maintainability, cost optimization, and ethical AI practices
Since V5 is the current version of Archon, all the code for V5 is in both the main directory and archon/iterations/v5-parallel-specialized-agents
directory.
- Docker (optional but preferred)
- Python 3.11+
- Supabase account (for vector database)
- OpenAI/Anthropic/OpenRouter API key or Ollama for local LLMs (note that only OpenAI supports streaming in the Streamlit UI currently)
- Clone the repository:
git clone https://github.com/coleam00/archon.git
cd archon
- Run the Docker setup script:
# This will build both containers and start Archon
python run_docker.py
- Access the Streamlit UI at http://localhost:8501.
Note:
run_docker.py
will automatically:
- Build the MCP server container
- Build the main Archon container
- Run Archon with the appropriate port mappings
- Use environment variables from
.env
file if it exists
- Clone the repository:
git clone https://github.com/coleam00/archon.git
cd archon
- Install dependencies:
python -m venv venv
source venv/bin/activate # On Windows: venv\Scripts\activate
pip install -r requirements.txt
- Start the Streamlit UI:
streamlit run streamlit_ui.py
- Access the Streamlit UI at http://localhost:8501.
After installation, follow the guided setup process in the Intro section of the Streamlit UI:
- Environment: Configure your API keys and model settings - all stored in
workbench/env_vars.json
- Database: Set up your Supabase vector database
- Documentation: Crawl and index the Pydantic AI documentation
- Agent Service: Start the agent service for generating agents
- Chat: Interact with Archon to create AI agents
- MCP (optional): Configure integration with AI IDEs
The Streamlit interface will guide you through each step with clear instructions and interactive elements. There are a good amount of steps for the setup but it goes quick!
If you encounter any errors when using Archon, please first check the logs in the "Agent Service" tab.
Logs specifically for MCP are also logged to workbench/logs.txt
(file is automatically created) so please
check there. The goal is for you to have a clear error message before creating a bug here in the GitHub repo
To get the latest updates for Archon when using Docker:
# Pull the latest changes from the repository (from within the archon directory)
git pull
# Rebuild and restart the containers with the latest changes
python run_docker.py
The run_docker.py
script will automatically:
- Detect and remove any existing Archon containers (whether running or stopped)
- Rebuild the containers with the latest code
- Start fresh containers with the updated version
To get the latest updates for Archon when using local Python installation:
# Pull the latest changes from the repository (from within the archon directory)
git pull
# Install any new dependencies
source venv/bin/activate # On Windows: venv\Scripts\activate
pip install -r requirements.txt
# Restart the Streamlit UI
# (If you're already running it, stop with Ctrl+C first)
streamlit run streamlit_ui.py
This ensures you're always running the most recent version of Archon with all the latest features and bug fixes.
- Basic RAG-powered agent using Pydantic AI
- Supabase vector database for documentation storage
- Simple code generation without validation
- Learn more about V1
- Multi-agent system with planning and execution separation
- Reasoning LLM (O3-mini/R1) for architecture planning
- LangGraph for workflow orchestration
- Support for local LLMs via Ollama
- Learn more about V2
- Integration with AI IDEs like Windsurf and Cursor
- Automated file creation and dependency management
- FastAPI service for agent generation
- Improved project structure and organization
- Learn more about V3
- Docker support
- Comprehensive Streamlit interface for managing all aspects of Archon
- Guided setup process with interactive tabs
- Environment variable management through the UI
- Database setup and documentation crawling simplified
- Agent service control and monitoring
- MCP configuration through the UI
- Learn more about V4
- Specialized refiner agents for different autonomously improving the initially generated agent
- Prompt refiner agent for optimizing system prompts
- Tools refiner agent for specialized tool implementation
- Agent refiner for optimizing agent configuration and dependencies
- Cohesive initial agent structure before specialized refinement
- Improved workflow orchestration with LangGraph
- Learn more about V5
- V6: Tool Library and Example Integration - Pre-built external tool and agent examples incorporation
- V7: LangGraph Documentation - Allow Archon to build Pydantic AI AND LangGraph agents
- V8: Self-Feedback Loop - Automated validation and error correction
- V9: Self Agent Execution - Testing and iterating on agents in an isolated environment
- V10: Multi-Framework Support - Framework-agnostic agent generation
- V11: Autonomous Framework Learning - Self-updating framework adapters
- V12: Advanced RAG Techniques - Enhanced retrieval and incorporation of framework documentation
- V13: MCP Agent Marketplace - Integrating Archon agents as MCP servers and publishing to marketplaces
- LangSmith
- MCP marketplace
- Other frameworks besides Pydantic AI
- Other vector databases besides Supabase
- Local AI package for the agent environment
The below diagram from the LangGraph studio is a visual representation of the Archon agent graph.
The flow works like this:
- You describe the initial AI agent you want to create
- The reasoner LLM creates the high level scope for the agent
- The primary coding agent uses the scope and documentation to create the initial agent
- Control is passed back to you to either give feedback or ask Archon to 'refine' the agent autonomously
- If refining autonomously, the specialized agents are invoked to improve the prompt, tools, and agent configuration
- The primary coding agent is invoked again with either user or specialized agent feedback
- The process goes back to step 4 until you say the agent is complete
- Once the agent is complete, Archon spits out the full code again with instructions for running it
streamlit_ui.py
: Comprehensive web interface for managing all aspects of Archongraph_service.py
: FastAPI service that handles the agentic workflowrun_docker.py
: Script to build and run Archon Docker containersDockerfile
: Container definition for the main Archon application
mcp/
: Model Context Protocol server implementationmcp_server.py
: MCP server script for AI IDE integrationDockerfile
: Container definition for the MCP server
archon/
: Core agent and workflow implementationarchon_graph.py
: LangGraph workflow definition and agent coordinationpydantic_ai_coder.py
: Main coding agent with RAG capabilitiesrefiner_agents/
: Specialized agents for refining different aspects of the created agentprompt_refiner_agent.py
: Optimizes system promptstools_refiner_agent.py
: Specializes in tool implementationagent_refiner_agent.py
: Refines agent configuration and dependencies
crawl_pydantic_ai_docs.py
: Documentation crawler and processor
utils/
: Utility functions and database setuputils.py
: Shared utility functionssite_pages.sql
: Database setup commands
workbench/
: Created at runtime, files specific to your environmentenv_vars.json
: Environment variables defined in the UI are stored here (included in .gitignore, file is created automatically)logs.txt
: Low level logs for all Archon processes go herescope.md
: The detailed scope document created by the reasoner model at the start of each Archon execution
- Docker Containers: Run Archon in isolated containers with all dependencies included
- Main container: Runs the Streamlit UI and graph service
- MCP container: Provides MCP server functionality for AI IDEs
- Local Python: Run directly on your system with a Python virtual environment
The Docker implementation consists of two containers:
-
Main Archon Container:
- Runs the Streamlit UI on port 8501
- Hosts the Graph Service on port 8100
- Built from the root Dockerfile
- Handles all agent functionality and user interactions
-
MCP Container:
- Implements the Model Context Protocol for AI IDE integration
- Built from the mcp/Dockerfile
- Communicates with the main container's Graph Service
- Provides a standardized interface for AI IDEs like Windsurf, Cursor, Cline, and Roo Code
When running with Docker, the run_docker.py
script automates building and starting both containers with the proper configuration.
The Supabase database uses the following schema:
CREATE TABLE site_pages (
id UUID PRIMARY KEY DEFAULT uuid_generate_v4(),
url TEXT,
chunk_number INTEGER,
title TEXT,
summary TEXT,
content TEXT,
metadata JSONB,
embedding VECTOR(1536) -- Adjust dimensions as necessary (i.e. 768 for nomic-embed-text)
);
The Streamlit UI provides an interface to set up this database structure automatically.
We welcome contributions! Whether you're fixing bugs, adding features, or improving documentation, please feel free to submit a Pull Request.
For version-specific details: