Item detail
github.com

rohitg00/agentmemory

rohitg00/agentmemory is a developer tool that RepoRadar is tracking in its Agent Memory section, currently rated Gold tier with a 'try now' verdict. Its strongest signal is workflow potential, scored 9.8 out of 10.

Score8.3
Popularity1.0
Riskconditional
TierGold
Score breakdown
Usefulness8.0
Novelty8.0
Momentum8.0
Maturity6.5
Open-source/build8.4
Evidence7.2
Workflow potential9.8
Setup ease6.4

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for heavy coding-agent users who want memory that survives across sessions and tools, especially when context budgets and repeated re-explanation are becoming the bottleneck.

Who should use it

Power users who rotate between multiple coding agents and want one persistent memory substrate Teams trying to reduce repeated context loading and prompt restatement costs Developers who want an MCP-addressable memory server instead of per-tool ad hoc notes Builders evaluating long-horizon coding-agent workflows with shared memory

Who should skip it

Skip rohitg00/agentmemory if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.

About this signal

rohitg00/agentmemory is tracked by RepoRadar as a developer tool in the Agent Memory section. First seen 2026-07-01; the source record was last checked on 2026-07-01. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. rohitg00/agentmemory leads on workflow potential (9.8) and open-source/build quality (8.4); its lowest signal is setup ease (6.4), 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.

How this item is evaluated

The rohitg00/agentmemory record combines a 8.3/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 installs hooks, skills, and an MCP service into coding-agent environments, so first evaluation should happen on a disposable repo and agent profile rather than a production workspace; The recall, token-savings, and benchmark numbers are maintainer claims, so compare retrieval quality and context cost on your own codebase before standardizing on it.

Evidence links
Closest alternatives / related signals
agent-memory mcp coding-agent hooks claude-code codex-cli apache-2.0
Verification record

What RepoRadar actually verified

Discovered

Automated discovery and source capture. Last checked 2026-08-13T20:20:15Z.

No editorial or hands-on review is claimed. This record remains at Discovered.

Verification sources

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

34 dated snapshots retained from 2026-07-01 through 2026-08-13; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.

RepoRadar score8.3 current · +0.0 net
Repository momentum9.6 current · +1.6 net
GitHub stars (observed)26,963 current · +1,892 net
GitHub stars26,963 exact observation
Versionv0.9.28
Last release2026-07-19T10:46:30Z
Maintenanceactive
Current riskconditional
Current verdicttry now
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineClaude, OpenAI Codex

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-08-138.39.626,963conditionaltry nowactive
2026-08-128.39.626,916conditionaltry nowactive
2026-08-118.39.626,862conditionaltry nowactive
2026-08-108.39.626,821conditionaltry nowactive
2026-08-098.39.626,768conditionaltry nowactive
2026-08-088.39.626,734conditionaltry nowactive
2026-08-078.39.626,420conditionaltry nowactive
2026-08-068.38.0Not recordedconditionaltry nownot recorded
2026-08-058.38.0Not recordedconditionaltry nownot recorded
2026-08-048.39.626,420conditionaltry nowactive
2026-08-038.39.626,420conditionaltry nowactive
2026-08-028.39.626,345conditionaltry nowactive

Why the record changed

stars changed

Stars changed: 26916 → 26963.

stars changed

Stars changed: 26862 → 26916.

stars changed

Stars changed: 26821 → 26862.

stars changed

Stars changed: 26768 → 26821.

stars changed

Stars changed: 26734 → 26768.

stars changed

Stars changed: 26420 → 26734.

stars changed

Stars changed: 26345 → 26420.

stars changed

Stars changed: 26307 → 26345.

stars changed

Source-observed stars changed: 26285 → 26307. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Source-observed stars changed: 26283 → 26285. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Source-observed stars changed: 26281 → 26283. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Stars changed: 25908 → 25952.