Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams studying how mobile agents should compress history and UI state without losing the thread on longer tasks.
Who should use it
Who should skip it
Pass on kwai/MemGUI-Agent if its scope or audience does not match what your team is building right now.
About this signal
kwai/MemGUI-Agent is tracked by RepoRadar as a mobile gui agent in the Agents and Automation section. It was first seen on 2026-06-30 and last updated on 2026-06-30. The current verdict is 'track' with a Silver tier and advanced setup difficulty. kwai/MemGUI-Agent leads on workflow potential (8.6) and open-source/build quality (8.4); its lowest signal is setup ease (4.2), so factor that in before investing setup time. 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 kwai/MemGUI-Agent a composite score of 7.8 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 'none' 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 public repo centers on training and offline evaluation utilities, so reproducing the strongest results still depends on external datasets, checkpoints, and heavier mobile-agent infrastructure than the quick start alone suggests; Benchmark wins do not by themselves make it a safe production phone-automation stack, so treat this as a research signal first and a deployable product second.