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

OpenClaw Outlook Add-in Connects Local Agent to Email Sidebar
A developer built an Outlook add-in that connects to a local OpenClaw Gateway via WebSocket, providing full agent access with tools and automations directly in the email sidebar. The tool reads selected emails as context, maintains per-email chat sessions, and works with Outlook Desktop and Web.

Claude File History: VS Code Extension for Tracking Claude Code Sessions
A VS Code extension called Claude File History tracks every Claude Code session that touched your files, allowing you to find past conversations, preview what was discussed, and resume conversations with a double-click.

Comparison of 14 Claw AI Agent Variants Across 10 Categories
A detailed comparison of 14 popular Claw AI agent variants including OpenClaw, NanoClaw, NemoClaw, ZeroClaw, PicoClaw, Moltis, IronClaw, and NullClaw, scored across 53 sub-parameters with composite rankings and ideal use cases for each.

LM Studio plugins add web image analysis for vision-capable LLMs
A developer created plugins for LM Studio that enable vision-capable LLMs to fetch and analyze images from the web, with automatic image processing and tool chaining. The plugins work with models like Qwen 3.5 9b/27b and include updated Duck-Duck-Go and Visit Website functionality.