Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for builders who want a more opinionated agent runtime than a bare chat loop, especially when they care about verification, memory, and reducing repeated mistakes across real repo work.
Who should use it
Who should skip it
Skip ChanningLua/prax-agent if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
ChanningLua/prax-agent is tracked by RepoRadar as a developer tool in the Agent Runtime section. It was first seen on 2026-07-01 and last updated on 2026-07-01. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. The standout signals for ChanningLua/prax-agent are workflow potential (9.4) and open-source/build quality (8.4), while maturity (5.8) 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 ChanningLua/prax-agent a composite score of 7.9 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
It stores learned corrections and experience across sessions and projects under the user's home directory, so first evaluation should happen on a disposable repo before feeding it sensitive code or notes; You supply the model endpoint and API key yourself, including optional third-party proxy routes, so review provider trust and data-handling before routing proprietary repository context through it.