Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for engineering teams that want to coordinate multiple AI coding agents with clearer branch isolation, review loops, and recovery from CI or merge-conflict churn.
Who should use it
Who should skip it
Move on from AgentWrapper/agent-orchestrator if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
AgentWrapper/agent-orchestrator is tracked by RepoRadar as a developer tool in the Coding Workflows section. It was first seen on 2026-06-28 and last updated on 2026-06-28. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, AgentWrapper/agent-orchestrator is strongest on workflow potential (10.0) and practical usefulness (9.0) and weakest on setup ease (6.4) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned AgentWrapper/agent-orchestrator a composite score of 8.7 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
The orchestrator can spawn multiple coding agents, run commands, and apply CI or review feedback across isolated worktrees, so first use should stay on disposable branches with repository protections enabled; Automatic feedback loops can accelerate changes faster than a solo review habit, so merge and deploy rights should remain behind human approval gates.