What happened
An open-source project called SwarmForge has been released on GitHub (at github.com/unclebob/swarm-forge) as a tmux-based orchestration platform for coordinating multiple AI agents working together on software engineering tasks. It offers three pre-built workflows (two-pack, four-pack, and six-pack) with 2, 4, and 6 agent roles respectively, each optimized for different project sizes and complexity levels.
Why it matters
Teams using AI agents for development can now coordinate multiple specialized agents (coder, architect, QA, etc.) working in parallel on the same project without stepping on each other's work. SwarmForge handles role assignment, git worktree management, message passing, and backend selection (Claude, Copilot, Codex, or Grok), turning what would be manual coordination into a structured, repeatable workflow.
What to watch
SwarmForge runs entirely locally using tmux and git, requiring only zsh, git, tmux, Babashka, and at least one configured agent backend. Users can start with the quick two-agent workflow, move to the moderate four-agent specification workflow, or use the full six-agent workflow for major projects. The system includes a layered constitution structure that allows project-specific customization while maintaining shared operational scripts.
Summaries like this, in your inbox every morning.
SwarmForge addresses a practical gap in AI agent coordination: while individual agents can write or review code, orchestrating multiple specialized agents without manual handoff work has been cumbersome. The project's three templated workflows (two-pack, four-pack, six-pack) reflect a deliberate design choice to match scope to complexity—small tasks can use a lean two-agent setup, while major projects benefit from full separation of concerns across six roles (specifier, coder, cleaner, architect, hardener, QA). By running entirely in tmux and git on a local machine, SwarmForge avoids external dependencies and keeps all swarm state contained in the project directory (.swarmforge/), making it portable and self-contained. The layered constitution system—where shared default articles live on main and runnable branches can add or override them—allows teams to maintain consistent engineering standards while customizing workflows per project. The validated handoff protocol (enforcing exactly 10-character commit abbreviations and single-line message limits) is designed to prevent silent failures and keep agent communication reliable and auditable.
Pick your industry and the AI tools you use, and get news related to your work every day.
Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.
Chunghwa Telecom president Rong-shy Lin said the shift from conversational AI to autonomous AI agents is resha…
Apple and Meta said they would jointly release a new open-weight AI model designed to run on high-end Macs, ai…
A writer and entrepreneur opened his daily to-do list and found 156 items, and concluded that an AI assistant…
A Zenn contributor sorted AI use into three modes — AI as an assistant, AI running alongside people, and AI th…
A non-engineer operator says one person ships four smartphone apps on Google Play, three on the App Store, wit…
The walkthrough points the CLI at a local mock via the ANTHROPIC_BASE_URL environment variable
