Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for people whose agent workflows keep losing hard-won context between sessions and need local recall without handing project memory to a hosted service.
Who should use it
Who should skip it
Pass on CodeAbra/iai-personal-memory-engine if its scope or audience does not match what your team is building right now.
About this signal
CodeAbra/iai-personal-memory-engine is tracked by RepoRadar as an AI project in the AI Infrastructure section. It was first seen on 2026-06-18 and last updated on 2026-06-18. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. CodeAbra/iai-personal-memory-engine leads on workflow potential (9.6) and practical usefulness (9.0); its lowest signal is momentum (6.0), so factor that in before investing setup time. This page summarizes the public evidence on the linked source page and states where additional review is still needed. 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 CodeAbra/iai-personal-memory-engine a composite score of 8.5 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 evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
It captures real coding-assistant session history, so first rollout should stay on trusted projects until retention, redaction, and disk layout are fully understood; Install path pulls together Python, Node, and a native Rust build, so Windows and mixed-environment teams should treat the current setup as a hands-on evaluation rather than a zero-friction drop-in.