Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for Claude Code users who want the deeper workflow harness, but want to compare cheaper worker models, local backends, or non-Anthropic APIs inside the same coding-agent loop.
Who should use it
Who should skip it
Pass on OnlyTerp/UltraCode-Shim if its scope or audience does not match what your team is building right now.
About this signal
OnlyTerp/UltraCode-Shim is tracked by RepoRadar as a agent harness in the Developer Tools 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. The standout signals for OnlyTerp/UltraCode-Shim are workflow potential (9.6) and open-source/build quality (8.4), while setup ease (6.4) trails — that balance shapes where it fits best. 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 OnlyTerp/UltraCode-Shim a composite score of 8.1 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 proxy sits between Claude Code and your configured model backends, so review how it stores keys and routes request traffic before using it on a shared machine; The README's example configs mention forward-looking model names, so verify actual provider availability and capability before copying benchmark or routing assumptions into production.