Repository navigation
docs: document parallel agents (--concurrency) and fix stale CLI flags - #291
zwanski-start wants to merge 1 commit into
Conversation
The orchestrator already runs up to 5 concurrent coding agents, but the README never mentioned it and CLAUDE.md referenced flags that do not exist on autonomous_agent_demo.py (--max-concurrency, --batch-features, --testing-batch-features). - README: add a Parallel Agents section (UI slider, CLI flags, caveats) - CLAUDE.md: use --concurrency / --feature-ids / --testing-feature-ids - parallel_orchestrator.py: fix stress-test comment and batch-size help text (code clamps to 1-15, help said 1-5) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
🔍 QA report: ✅ PassedTester: Barbara (cubefarm agent, in a fresh session) · Round: 1 · Author: Ada This docs-only PR adds an accurate README section on parallel agents (--concurrency, the UI slider, batching, caveats). It replaces the stale CLI flags in CLAUDE.md and the orchestrator comment and help text with ones the parser accepts, which resolves the question in issue #5. I parsed every documented command with the real argparse (all accepted) and confirmed the old flags are rejected. I checked each claim against the code and saw the slider in the running UI. ruff, the security tests and the UI build pass, and pytest and mypy match master apart from local-environment noise. Non-blocking: the README calls --testing-ratio 'per coding agent', but the code runs a fixed number of testing agents (0-3) regardless of concurrency, and '5 coding + 5 testing' overstates testing agents, which top out at 3. This wording is inherited from the existing --help text and CLAUDE.md and worth correcting in a follow-up.
🧪 Commands run
No browser screenshots were taken in this round. Posted by cubefarm · merges automatically once GitHub's checks pass |
Adaptation: also corrected the run_parallel_orchestrator docstring (testing batch size is clamped to 1-15, not 1-5). Integrates AutoForgeAI#291 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AeH26pcsqoxPb3CDs8g1VN
Closes #5
Summary
Issue #5 asks whether multiple Claude agents can work on a project at the same time to finish it faster. They already can. The unified orchestrator (
parallel_orchestrator.py) runs up to 5 concurrent coding agents. It hands features out atomically and schedules by dependency. You can turn it on with--concurrency Nor the concurrency slider in the UI. The problem is that it was barely documented, and what docs existed pointed at the wrong flags.Changes
--concurrency,--batch-size,--testing-ratio,--testing-batch-size)autonomous_agent_demo.pydoes not accept:--parallel --max-concurrency 3→--concurrency 3--batch-features→--feature-ids--testing-batch-features→--testing-feature-ids--batch-size/--testing-batch-sizehelp said1-5, but the code clamps to1-15. The help now says1-15.Verification
parse_args()was run with the documented flag combination. They all parse.max_concurrency1-5, ratio 0-3, batches 1-15), YOLO skipping testing agents, per-agentPLAYWRIGHT_CLI_SESSION, and the slider range inAgentControl.tsx.ruff check .passes andpython test_security.pypasses.Assumptions
🤖 Generated with Claude Code