Show HN: Go에서 오픈 소스 다중 에이전트 하네스를 구축했습니다.

hackernews | | 📦 오픈소스
#ai agent #ai worker #ai 모델 #claude #go #llama #multi-agent #open source #openai
원문 출처: hackernews · Genesis Park에서 요약 및 분석

요약

Go 언어로 개발된 오픈소스 다중 AI 에이전트 오케스트레이션 도구가 공개되어, 단일 대시보드에서 클로드, 오픈AI 코덱스 등 다양한 AI 모델들을 하나의 팀으로 구성해 병렬 작업을 수행할 수 있습니다. 이 도구는 실시간 웹 대시보드를 통해 에이전트 간 채널 기반 소통, 칸반 보드 형태의 작업 관리, 실시간 터미널 모니터링 등을 지원하며, 세션 중단 후에도 문맥을 잃지 않는 지속성을 갖추고 있습니다. 특히 'CEO' 역할의 리더 에이전트를 설정해 새로운 에이전트를 자율적으로 생성하고 팀을 관리하도록 할 수 있으며, 개발자는 실제로 이 시스템을 활용해 청구 및 팀 관리 기능을 포함한 SaaS 모니터링 서비스를 약 24시간 만에 구축하는 성과를 입증했습니다.

본문

An open source AI agent harness for orchestrating multiple AI workers from a single dashboard. Built in Go. Artificial lets you spawn, manage, and coordinate AI agents (Claude Code, OpenAI Codex, ACP-compatible models, local LLMs) as a team. Agents get personas, skills, communication channels, and a shared task board. You manage them from a real-time web dashboard or the REST API. - Multi-agent orchestration — run multiple AI agents in parallel, each with their own role and persona - Real-time dashboard — chat with agents, manage tasks on a kanban board, monitor activity - Channel-based communication — agents can message each other and receive notifications mid-task - Multiple backends — supports Claude Code, OpenAI Codex, ACP (Agent Communication Protocol), and local models via OpenAI-compatible APIs - MCP integration — each worker exposes tools to its agent via Model Context Protocol - Session persistence — stop and resume agent sessions without losing context ┌───────────────────────────────────────────────────┐ │ svc-artificial │ │ Dashboard · REST API · WebSocket Hub │ │ SQLite DB │ └─────────┬──────────────┬─────────────┬────────────┘ │ WebSocket │ WebSocket │ WebSocket ┌─────┴──────┐ ┌────┴──────┐ ┌───┴────────┐ │ cmd-worker │ │ cmd-worker│ │ cmd-worker │ │ (Codex) │ │ (Claude) │ │ (ACP) │ │ ┌──────┐ │ │ ┌──────┐ │ │ ┌────────┐ │ │ │ GPT │ │ │ │Claude│ │ │ │Cursor/ │ │ │ │ 5.4 │ │ │ │Opus │ │ │ │opencode│ │ │ └──────┘ │ │ └──────┘ │ │ └────────┘ │ └────────────┘ └───────────┘ └────────────┘ # Build both binaries make build # Start the central service (dashboard at http://localhost:4000) make run-artificial # In another terminal, start a worker (or spawn from the Dashboard) make run-worker EMPLOYEE_ID=1 - Go 1.25+ - Claude Code CLI, OpenAI Codex CLI, or an ACP-compatible agent server - Set up company knowledge — create a folder with a README describing your project, conventions, and priorities (see Company knowledge). Set the path in dashboard Settings. - Create a CEO — add an employee with the "CEO" role from the dashboard. This is the lead agent that can hire and fire other workers, and spawn new agents on its own. - Add a project — set up the project you want the team to work on, with its path and description. - Grow the team — either add employees manually from the dashboard, or chat with the CEO and ask it to hire more people to work on the project. The CEO can spawn and manage workers autonomously. src/ ├── svc-artificial/ # Central service (dashboard, API, WebSocket hub, SQLite) ├── cmd-worker/ # Worker binary (agent lifecycle, MCP server, hub client) └── pkg-go-shared/ # Shared protocol types The built-in web dashboard provides: - Chat — direct messages and channel conversations with agents - Board — kanban task management (todo, in progress, review, done) - Team — view and manage active workers, spawn new agents - Live TTY — stream agent terminal output in real-time Create a folder that will serve as your team's shared knowledge base. This is where agents look for context about your project, conventions, and goals. mkdir my-company cat > my-company/README.md << 'EOF' # My Company ## What we're building Describe your product/project here. ## Conventions - Language, framework, and style preferences - How we name things, structure code, etc. ## Tools - List CLI tools, scripts, or services agents can use - e.g. `make test`, `npm run lint`, deployment commands - Any internal APIs or databases they should know about ## Current priorities - What the team is focused on right now EOF Once the service is running, set the knowledge path in the dashboard Settings. Every agent spawned will have access to this context. The REST API exposes endpoints for managing employees, tasks, channels, messages, and worker lifecycle. See src/svc-artificial/internal/server/api.go for the full list. | Backend | Description | Status | |---|---|---| | Claude Code | Spawns Claude Code CLI via PTY with MCP tools | Tested | | Codex | Spawns OpenAI Codex CLI via PTY with MCP tools | Tested | | ACP | Connects to any Agent Communication Protocol server | Tested with Cursor Agent and opencode | | Local models | Via opencode + OpenAI-compatible APIs (LM Studio, ollama, etc.) | Works, but needs a strong local model | I built MyUpMonitor — a complete uptime monitoring SaaS with billing, teams, status pages, CLI, Terraform provider, and more — in about 24 hours of focused work using Artificial to orchestrate my AI development workflow. Built by André Baltazar MIT

Genesis Park 편집팀이 AI를 활용하여 작성한 분석입니다. 원문은 출처 링크를 통해 확인할 수 있습니다.

공유

관련 저널 읽기

전체 보기 →