Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers who want a more opinionated local coding agent with deterministic checks and broader built-in tooling than a minimal terminal wrapper, while keeping cloud providers as optional fallbacks.
Who should use it
Who should skip it
Skip QodeXcli/QodeX if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
QodeXcli/QodeX is tracked by RepoRadar as a coding agent in the Local AI section. It was first seen on 2026-06-28 and last updated on 2026-06-28. The current verdict is 'worth watch' with a Silver tier and moderate setup difficulty. The standout signals for QodeXcli/QodeX are open-source/build quality (8.4) and workflow potential (8.1), while momentum (5.0) 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 QodeXcli/QodeX a composite score of 7.7 out of 10, placing it in the Silver 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
QodeX can read and edit code, run shell commands, drive a browser, and open shareable artifacts, so first use should stay in a sandboxed repo with auto-approval off; The project makes very broad capability claims relative to its current footprint, so teams should validate the exact toolchains they need before replacing an established coding agent.