Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for advanced Claude Code users who want repeatable multi-agent coordination and a local brain without moving the whole workflow into a hosted platform.
Who should use it
Who should skip it
Move on from mercurialsolo/claudectl if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
mercurialsolo/claudectl is tracked by RepoRadar as a developer tool in the Agent Orchestration section. It was first seen on 2026-07-01 and last updated on 2026-07-01. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. mercurialsolo/claudectl leads on workflow potential (9.5) and open-source/build quality (8.4); its lowest signal is momentum (6.0), so factor that in before investing setup time. 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 mercurialsolo/claudectl a composite score of 8.0 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
It coordinates multiple coding agents and stores local decision history, so first runs belong on a disposable repo with limited permissions rather than a sensitive client codebase; The local brain can retain operational context from past runs, so review what gets stored before using it on proprietary repositories.