Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams formalizing multi-agent software delivery, especially when one agent writes plans and context while another agent executes inside isolated worktrees with a repeatable operating model.
Who should use it
Who should skip it
Hold off on cluesmith/codev if the setup requirements exceed what your current workflow or team can support without dedicated engineering time.
About this signal
cluesmith/codev is tracked by RepoRadar as a workflow os in the Developer Workflow section. It was first seen on 2026-06-30 and last updated on 2026-06-30. The current verdict is 'try now' with a Gold tier and hard setup difficulty. cluesmith/codev leads on workflow potential (9.8) and novelty (9.0); its lowest signal is setup ease (4.2), 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 cluesmith/codev a composite score of 8.3 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 evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
README examples use unattended permission-skipping agent runs, so first rollout should stay on throwaway repos or tightly sandboxed branches; Optional browser-based remote access means shared sessions should stay off sensitive repos until access controls and audit visibility are reviewed.