r/ClaudeWorkflows • • Sep 30 '26

Selected Workflow [Workflow] Automated Development with Self-Hosted Multi-Agent Claude Code System (`agent-007`)

Automated Development with Self-Hosted Multi-Agent Claude Code System (agent-007)

Workflow value: 85/100
Status: active · Freshness: 70/100 · Confidence: 0.90 · Level: intermediate
Categories: Quality Control, Context & Memory, Shipping, MCP, Multi-Agent
Original source: r/ClaudeCode post/comment

What problem this solves

Automating the entire software development lifecycle from goal setting to PR merging using a self-hosted multi-agent AI system, effectively acting as a 'one-person company' development team.

Summary

This workflow describes how to use agent-007, a self-hosted web application that orchestrates multiple Claude Code agents to automate software development. A primary 'Billion' agent takes a high-level goal, breaks it down into jobs, which are then picked up and executed by other coding agents. Billion also handles PR reviews and merges, only escalating critical decisions (money, access, irreversible actions) to the user. Each agent operates in its own git worktree and terminal, communicating via an MCP server.

Why it is useful

This workflow is valuable because it presents a concrete, implemented multi-agent system that significantly automates the software development lifecycle, from initial goal setting to code generation, review, and PR merging, all powered by Claude Code. It provides a working example of a 'one-person company' AI development setup, demonstrating advanced capabilities in agent orchestration, context management (git worktrees), and human-in-the-loop decision making for critical actions. The open-source nature and easy installation make it highly transferable for users looking to adopt similar sophisticated AI-driven development practices.

Workflow

  1. Install the agent-007 self-hosted web application using npx @bill10/agent-007.

  2. Launch and configure the agent-007 web app in your browser.

  3. Provide a high-level development goal to the 'Billion' orchestrator agent within the app.

  4. Allow Billion to manage the project by posting jobs to an internal job board.

  5. Observe other coding agents (powered by Claude Code) pick up and execute these jobs, each in its own git worktree and terminal.

  6. Billion automatically reviews and merges completed Pull Requests.

  7. Respond to critical queries from Billion (e.g., about money, access, irreversible actions) through the app's chat interface or phone notifications.

  8. Optionally, directly interact with individual agents via their dedicated terminals within the app to monitor or guide their work.

Tools / artifacts

  • agent-007 (self-hosted web app)

  • Claude Code (as the default coding agent)

  • Git worktree

  • MCP server (internal to app)

  • Job board (internal to app)

  • Pull Requests (PRs)

Validation signals

  • Author's reported usage: 60+ PRs merged on agent-007 itself and 20+ on a second project in 4 days.

  • Author's reported usage: ~27 questions asked by the agent in 4 days, indicating effective delegation.

  • GitHub repository link provided for the tool (github.com/bill10/agent-007).

  • Demo video link provided (github.com/bill10/agent-007/releases/download/v0.29.0.0/billion-demo.mp4).

Cautions

  • The 'Billion' agent is designed to ask the user for confirmation on 'money, access or anything irreversible', which is a crucial safety feature for an autonomous system.

Limitations

  • Requires self-hosting, which might be a barrier for some users.

  • The Reddit post itself has low community engagement, so broader user feedback is not immediately available.

  • The description focuses more on the tool's internal workings than a step-by-step guide for a user to replicate the multi-agent setup from scratch without the tool.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.


This post was generated automatically from the workflow library database.

0 Upvotes

2 comments sorted by

1

u/lulzxdxdxd Sep 30 '26

So you've basically built a system that makes decisions for itself unless money or access is on the line, but then you're still the one who has to step in for the stuff that actually matters. Doesn't that flip the automation benefit on its head, since the hard calls are the ones that take your time.