---
title: "Aperant Runs 12 Claude Agents in Parallel to Build Software Autonomously"
subtitle: "Aperant (formerly Auto Claude) brings a Kanban-driven multi-agent pipeline to your local desktop, running up to 12 parallel Claude agents in isolated git worktrees to plan, build, test, and ship software autonomously."
url: "https://alphasignal.ai/news/aperant-runs-12-claude-agents-in-parallel-to-build-software-autonomously"
author: "AlphaSignal Newsroom"
author_url: "https://alphasignal.ai/editorial-team"
company: "AlphaSignal"
company_url: "https://alphasignal.ai/company/alphasignal"
published: "2026-06-14T08:27:00.000Z"
updated: "2026-07-02T13:13:47.731Z"
type: "Repo"
topics:
  - "Development"
  - "Open Source"
subtopics:
  - "Code Agents"
upvotes: 12
source_url: "https://github.com/AndyMik90/Aperant"
comments: 0
truncated: true
---

# Aperant Runs 12 Claude Agents in Parallel to Build Software Autonomously

> Aperant (formerly Auto Claude) brings a Kanban-driven multi-agent pipeline to your local desktop, running up to 12 parallel Claude agents in isolated git worktrees to plan, build, test, and ship software autonomously.

[Aperant](https://github.com/AndyMik90/Aperant) is an open-source, autonomous multi-agent coding framework that orchestrates Claude agents to handle the full software lifecycle: architecture planning, parallel implementation, self-validating QA, and AI-assisted merging. It started life as "Auto Claude" and quietly accumulated over 14,000 GitHub stars before rebranding in March 2026\. The project is now actively rebuilding toward version 3.0, which will add cloud features on top of the existing local desktop experience.

## The problem it actually solves

Single-agent AI coding tools are fast but sequential. You wait for one task to finish before the next begins, and you're still the one doing the architecture, writing the tests, and managing the merge. If you've used Claude Code for serious development work, you've probably hit the same wall: one agent, one terminal, one branch, one task at a time. You wait for the agent to finish the auth system before it can start on the API layer. You sit idle while it works through a refactor. The model is fast, but the workflow is sequential. 

Aperant's answer is to turn that single-agent loop into a managed pipeline. You describe what you want to build, and a team of agents handles the breakdown, implementation, and validation in parallel, while a Kanban board gives you a live view of what each agent is doing.

## How the parallel execution actually works

The core technical trick is git worktrees. Git worktrees give each AI coding agent its own isolated codebase so parallel sessions never overwrite each other's changes. Instead of cloning the repo multiple times, git worktrees enable parallel AI agent execution by giving each agent its own isolated working directory and git index while sharing a single object store, preventing file-level conflicts, context contamination, and lock contention when multiple agents operate on the same repository.

_Preview only. Full text requires an AlphaSignal Pro account._

## Sources

- [GitHub - AndyMik90/Aperant: Autonomous multi-session AI coding](https://github.com/AndyMik90/Aperant)
- [Aperant — Software that builds itself](https://aperant.com)
- [From Auto Claude to Aperant: Project Evolution](https://zread.ai/AndyMik90/Aperant/7-from-auto-claude-to-aperant-project-evolution)
- [AI Agent Frameworks (2026 Update): 8 SDKs Compared](https://www.morphllm.com/ai-agent-framework)
- [Awesome Agent Orchestrators](https://github.com/andyrewlee/awesome-agent-orchestrators)
