An AI-powered organizational model with autonomous role-based agents communicating via MCP protocol
ECHO enables future tech companies to operate with AI workers that:
- Make autonomous decisions within their authority
- Collaborate through consensus when needed
- Escalate to appropriate authority levels
- Require human approval for critical decisions
- Communicate naturally across organizational hierarchies
Each organizational role runs as an independent MCP server that Claude Desktop (or any MCP client) can connect to:
Claude Desktop / MCP Client
βββ> mcp-server-ceo
βββ> mcp-server-cto
βββ> mcp-server-chro
βββ> mcp-server-operations
βββ> mcp-server-product-manager
βββ> mcp-server-architect
βββ> mcp-server-uiux
βββ> mcp-server-developer
βββ> mcp-server-test-lead
All agents share:
βββ PostgreSQL (organizational memory)
βββ Redis (message bus)
NEW: Real-time Phoenix LiveView dashboard for monitoring agent activities!
cd monitor
./start.sh
# Open http://localhost:4000Features:
- π Overview: Daily agent activity summary
- π Power Delegation: Decision flow tracking
- π Performance: Agent metrics and efficiency
- β±οΈ Timeline: Real-time activity feed
See MONITORING_DASHBOARD_GUIDE.md for details.
- Elixir 1.18+ with Erlang/OTP 27
- PostgreSQL 16+
- Redis 7+
- Ollama (for local AI models)
- Claude Desktop (for MCP client)
1. Start infrastructure:
# macOS with Homebrew
brew services start postgresql
brew services start redis
# Or use Nix shell (includes all dependencies)
nix-shell2. Setup database, LLMs, and agents:
# Create database and run migrations
cd shared
mix ecto.create
mix ecto.migrate
cd ..
# Install Ollama and download AI models (~48GB)
./setup_llms.sh
# Build all agents
./setup.sh3. Configure Claude Desktop:
The setup script automatically creates the configuration. Just restart Claude Desktop!
Manual configuration: See CLAUDE_DESKTOP_SETUP.md
# Check system health
./echo.sh summary
# Expected output:
# β System Status: OPERATIONAL
# Infrastructure: β PostgreSQL, β Redis
# Agents: β 3 / 9 agents healthy
# Test LLM integration for specific agent
./scripts/agents/test_agent_llm.sh ceo
# Test all agents' LLM integration
./scripts/agents/test_all_agents_llm.shOpen Claude Desktop and try:
Use the CEO agent to approve a strategic initiative:
- Name: "AI Research Lab"
- Budget: $750,000
- Expected outcome: "Advanced AI capabilities"
See DEMO_GUIDE.md for 10 comprehensive demo scenarios.
| Document | Description |
|---|---|
| CLAUDE_DESKTOP_SETUP.md | Connect agents to Claude Desktop |
| DEMO_GUIDE.md | 10 demo scenarios with examples |
| ECHO_ARCHITECTURE.md | Complete system architecture |
| AGENT_INTEGRATION_GUIDE.md | Agent implementation details |
| LLM_TESTING_SUCCESS.md | LLM integration testing guide |
| OLLAMA_SETUP_COMPLETE.md | Ollama and model setup |
| DISTRIBUTED_SYSTEMS_IMPROVEMENTS.md | Reliability & observability |
| ECHO_SH_README.md | Monitoring script documentation |
Each agent has AI assistance via specialized local LLM models:
| Agent | Role | AI Model | Status |
|---|---|---|---|
| CEO | Strategic leadership, budget allocation | qwen2.5:14b | β Built + AI |
| CTO | Technology strategy, architecture | deepseek-coder:33b | β Built + AI |
| CHRO | Human resources, talent management | llama3.1:8b | β Built + AI |
| Operations Head | Infrastructure and operations | mistral:7b | β Built + AI |
| Product Manager | Product strategy, prioritization | llama3.1:8b | β Built + AI |
| Senior Architect | System design, technical specs | deepseek-coder:33b | β Built + AI |
| UI/UX Engineer | Interface design, user experience | llama3.2-vision:11b | β Built + AI |
| Senior Developer | Feature implementation, coding | deepseek-coder:6.7b | β Built + AI |
| Test Lead | Quality assurance, testing | codellama:13b | β Built + AI |
All agents use local AI models via Ollama - zero API costs, complete privacy, works offline.
Every agent has an ai_consult tool for AI-assisted analysis:
# CEO consulting AI for strategic decision
ai_consult(
query_type: "decision_analysis",
question: "Should we expand to European market?",
context: %{
options: ["Immediate expansion", "Pilot program", "Defer"],
budget: "$5M",
timeline: "12 months"
}
)Benefits:
- π Private - All AI runs locally, no cloud APIs
- π° Free - Zero API costs after setup
- π― Specialized - Each role has domain-specific model
- β‘ Fast - Low latency for real-time decisions
- π Offline - Works without internet
Autonomous - Agent makes decision within authority:
# CEO can approve budgets under $1M autonomously
approve_budget(amount: 750_000) # β
Autonomous
approve_budget(amount: 5_000_000) # β¬οΈ Escalates to humanCollaborative - Multiple agents vote/consensus:
# CTO proposes architecture, team votes
propose_architecture(design: "Microservices")
# β Senior Architect, Operations, Product Manager voteHierarchical - Escalates up reporting chain:
# Developer uncertain β Architect β CTO β CEO
escalate_technical_decision(issue: "Database choice")Human-in-the-Loop - Critical decisions require human:
# Legal, financial, or strategic risks
escalate_to_human(reason: "Regulatory compliance")Agents communicate via Redis pub/sub + PostgreSQL persistence:
# Product Manager β CTO
publish_message(
from: :product_manager,
to: :cto,
type: :request,
subject: "Technical feasibility review"
)Define multi-agent workflows:
workflow "Feature Development" do
step :product_manager, "define_requirements"
step :senior_architect, "design_system"
step :cto, "approve_architecture"
parallel do
step :senior_developer, "implement_backend"
step :ui_ux_engineer, "design_ui"
end
step :test_lead, "create_test_plan"
step :ceo, "approve_budget"
endReal-time system observability:
./echo.sh # Full system status
./echo.sh agents # Agent health with heartbeats
./echo.sh workflows # Running workflows
./echo.sh messages # Message queue status
./echo.sh decisions # Pending decisionsCurrent Phase: Phase 4 - Workflows & Integration
Completed:
- β Phase 1: Foundation (shared library, MCP protocol, database schemas)
- β Phase 2: CEO agent (reference implementation)
- β Phase 3: All 9 agents implemented
- β Phase 4.1: Distributed systems improvements (reliability, observability)
In Progress:
- π Workflow engine testing
- π Integration with external systems
- π Production deployment guides
See ECHO_ARCHITECTURE.md for complete architecture design.
MIT License
ECHO - Building the future of AI-powered organizations, one agent at a time. π