Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers who want to keep using Claude Code's native workflow while separating accounts, providers, and model costs across different profiles.
Where this stands now
sasdsamatt123/claudex ranks #25 of 33 tracked Coding Agents items by composite score (7.8 against a section median of 8.0). The section currently carries 20 Gold, 10 Silver, 3 Bronze. RepoRadar has retained observations for this record since 2026-07-01 (74 days in the current window). Signal extremes versus the section: novelty at the 21th percentile.
Who should use it
Who should skip it
Skip sasdsamatt123/claudex unless the captured evidence suggests it solves a problem you are actively working on.
About this signal
sasdsamatt123/claudex is tracked by RepoRadar as a developer tool in the Coding Agents section. First seen 2026-07-01; the source record was last checked on 2026-07-01. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. Across RepoRadar's eight signals, sasdsamatt123/claudex is strongest on workflow potential (9.3) and open-source/build quality (8.4) and weakest on maturity (5.7) — 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 sasdsamatt123/claudex record combines a 7.8/10 composite score with separate popularity (1.0), risk (conditional), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.
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 stores multiple API keys and profile configs locally, so the first setup should use dedicated low-spend test credentials and confirm where secrets land on disk; Anthropic-compatible providers can differ on tool support, context handling, and model behavior, so workflows should be tested per provider instead of assuming full Claude Code parity.