ACO System: Open-Source Multi-Agent Pipeline from GitHub Issue to Merged PR

ACO System is an open-source multi-agent framework that runs the entire software development pipeline autonomously — from a GitHub Issue to a merged PR — using six specialized AI agents. Built by Aniket Karne, it's designed to eliminate context loss and handoff overhead typical in human-only development workflows.
Unlike LangChain, AutoGen, or CrewAI, ACO's agents do not communicate with each other directly. Instead, each agent reads from and writes to a shared database. Complexity lives in the schema, not in inter-agent logic. The pipeline runs with SQLite in development and Postgres in production, and ships with a live Kanban dashboard and streaming event feed for real-time agent observation.
Pipeline Stages
- PM agent writes the user story from a given idea.
- Planner agent breaks the story into tasks with estimates.
- Architect agent (hard gate) validates feasibility without using an LLM — it scans for hardcoded secrets, missing acceptance criteria, and invalid tech stack configuration. If the story fails, it never reaches a developer.
- Developer agent creates a branch and opens a PR.
- QA agent reviews the code and runs tests.
- Human gives final sign-off before merge.
The Architect gate is deterministic, not probabilistic. It enforces a hard set of rules: no hardcoded secrets, acceptance criteria must be complete, and tech stack must be consistent. This prevents hallucinated or unworkable PRs from ever being generated.
Why It's Different
Agents run independently via a shared database, not through agent-to-agent messages. This design keeps each agent simple and the overall system predictable. The framework is built in Python with a Next.js frontend for the dashboard.
Getting Started
The project is open source on GitHub. Clone the repo, run with SQLite locally, and connect to Postgres for production. The Kanban dashboard and event stream are live by default.
Who It's For
Dev teams building agentic CI/CD pipelines, researchers exploring multi-agent architectures, and anyone tired of context loss between handoffs.
📖 Read the full source: r/openclaw
👀 See Also

Real Cost of AI Coding Tools: 42 Hours of Overhead per 60 Days — A Solo Dev's Detailed Breakdown
A solo dev tracked every dollar and minute spent on AI coding tools for 60 days. Subscriptions ($200/mo) were the smallest cost; 42 hours of overhead from bad output and tool-switching were the real tax. Net productivity gain was 1.7-2x, not 10x. Surprise: CodeRabbit, a $15/mo review tool, had the highest ROI.

Clawdex: A Directory for Tracking OpenClaw Derivatives and Forks
Clawdex is a directory listing 18 OpenClaw-related projects across three tiers, with data on stars, language, and category tags. The project is PR-driven, requiring contributors to fork the repo, add a YAML file to /src/data/projects/, and open a pull request.

First-Tree: Open-Source Daemon That Uses Claude Code to Triage GitHub Notifications While You Sleep
An open-source menu bar daemon that uses Claude Code to autonomously triage GitHub notifications – it handled 98 out of 100 notifications in a recent scan, leaving only 2 for human review.

Recall: A Persistent Memory MCP Server for Claude Code
Recall is an open-source MCP server that gives Claude Code persistent memory across sessions via semantic search with embeddings. It includes four lifecycle hooks: session-start, observe, pre-compact, and session-end.