Skip to main content
What it contains
Public-beta autonomous engineering-team runtime coordinating planning, coding, review, QA, merge, verification, and replanning agents.
Typical uses
Run high-autonomy single/multi-repository engineering programs with parallel worktrees, checkpoints, retries, and model-per-role selection.
Why people choose it
Inference: useful when a single coding-agent loop is insufficient and public-beta operational complexity is acceptable.
LicenseApache License 2.0
Last meaningful updateUnknown
Production readinessdevelopment
Classification
Subject domains
autonomous software engineeringmulti-agent orchestration
Task categories
autonomous software engineeringmulti-agent orchestration
Project phases
planningimplementationtestingreview
Secondary types
serviceagent collectionAPI
Select when
- Need an autonomous engineering factory
Do not select when
- Small task
- Production policy disallows public-beta autonomy
Implementation complexityhigh
Routing heuristic 74.0%
Security boundary clarity
5/5 First-party routing documentation
5/5 Strengths
None documented.
Poor-fit scenarios
- Small task
- Production policy disallows public-beta autonomy
Limitations
None documented.
README.md
Top-level autonomous build entry.
planexecuteverify
README.md
PM/architecture/lead planning.
decompositionDAG
README.md
Implement and validate.
codingreviewQA
README.md
Integrate and verify acceptance.
mergeverification
README.md
Adapt after failures.
replanning
FrameworksNone documented
RuntimesPython >=3.12, AgentField, Claude Code/OpenCode/Codex
Operating systemsNone documented
Installation methodsNone documented
Required credentialsNone documented
External servicesmodel providers
Major dependenciesAgentField
Compatibility notes
None documented.
One-sentence semantic summary
Public-beta autonomous engineering-team runtime coordinating planning, coding, review, QA, merge, verification, and replanning agents.
Capability keywords
planningparallel codingreviewQAmergeverificationmulti-reporeplanning
User intent phrases
- Need an autonomous engineering factory
Negative match phrases
- Small task
- Production policy disallows public-beta autonomy
Differentiators
None documented.
Security considerations
- Use least-privilege repo credentials/protected branches and human review.
Privacy considerations
None documented.
Uncertainty
Unresolved items
None documented.
Inference notes
None documented.
Repository usage guidance
installation summaryUnknown
basic usage summaryRun high-autonomy single/multi-repository engineering programs with parallel worktrees, checkpoints, retries, and model-per-role selection.
documented entry pointsNone documented
key configuration filesNone documented
important directoriesNone documented
documentation pathsREADME.md
example pathsNone documented
Relationships
alternative
high
SWE-AF is autonomous engineering factory; Multica is human+agent workboard/orchestration.
Recommended combinations
Not part of a curated combination.
Routing rules
rule_022: Need an autonomous engineering factory P978
Rationale
Public-beta autonomous engineering-team runtime coordinating planning, coding, review, QA, merge, verification, and replanning agents.
Required conditions
None documented.
Preferred
Agent-Field/SWE-AF
Fallback
None