Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams running multi-stage autonomous coding work who need deterministic guardrails (shell-enforced commit/staging/worktree rules) outside the model's control, for engineering leads who want completion criteria enforced by loom itself rather than self-reports, and for codebases that benefit from per-stage memory journals feeding a curated knowledge base.
Where this stands now
cosmix/loom ranks #5 of 12 tracked Agent Frameworks & Orchestration items by composite score (7.6 against a section median of 7.6). The section currently carries 7 Silver, 5 Gold. RepoRadar has retained observations for this record since 2026-08-10 (46 days in the current window). Signal extremes versus the section: momentum at the 8th percentile; novelty at the 83th percentile.
Who should use it
Who should skip it
Hold off on cosmix/loom if the setup requirements exceed what your current workflow or team can support without dedicated engineering time.
About this signal
cosmix/loom is tracked by RepoRadar as a framework in the Agent Frameworks & Orchestration section. First seen 2026-08-10; the source record was last checked on 2026-08-10. The current verdict is 'try now' with a Gold tier and hard setup difficulty. Across RepoRadar's eight signals, cosmix/loom is strongest on workflow potential (9.1) and novelty (9.0) and weakest on setup ease (4.2) — a profile worth weighing against your own priorities. This page summarizes the public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The cosmix/loom record combines a 7.6/10 composite score with separate popularity (0.1), risk (conditional), and setup (hard) signals. See the scoring methodology for the current weights and evidence definitions.
Questions worth asking before you adopt this
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
Loom installs 16 Claude Code shell hooks plus a git pre-commit hook on the host repo; inspect commit-guard.sh, git-add-guard.sh, worktree-isolation.sh, and subagent-verify-guard.sh before installing, and confirm the bypass-flag token mechanism is acceptable for your team's threat model.