Nicheloom visits: 58,213 all-time · 7,637 in the last 7 days

The opportunity tracker for new startups.

Today: 1,008 launches · Niche of the day: specialized calculation tools · See what launched today →

Unify memory across agents and improve context rot, written in Rust

Get picks like this daily. Today's launch numbers, the top launches, AI and tech news, and a daily opportunity pick, straight to your inbox.

Want to reach these readers? Sponsor an issue.

I was frustrated that memory is usually tied to a specific tool. They’re useful inside one session but I have to re-explain the same things when I switch tools or sessions. Furthermore, most agents' memory systems just append to a markdown file and dump the whole thing into context. Eventually, it's full of irrelevant information that wastes tokens.So I built this local memory layer that unifies memory across agents. Instead of a flat file, it builds a structured knowledge graph of "memory notes" inspired by the paper "A-MEM: Agentic Memory for LLM Agents" (https://arxiv.org/abs/2502.12110). The graph continuously evolves as more memories are committed, so older context stays organized rather than piling up.It captures conversation turns and exposes an MCP service so any supported agent can query for information relevant to the current context. In practice that means less context rot and better long-term memory recall across all your agents. Right now it supports Claude Code, Codex, Gemini CLI, OpenCode, and OpenClaw.Would love to hear any feedback.

HN · launched Apr 5, 2026 · 5 upvotes (top 89%) · 1 view

Niche: ai agent memory infrastructure · 350 launches, 11 in the last 7 days ▼ -58% · Explore this niche →

Category and tags

  • Horizontal
  • Data infrastructure
  • Developer
  • AI-native
  • Hobby / open-source project

Visit website ↗ Source listing ↗

Could you build this?

Yes A cross-agent memory server in Rust storing facts/summaries in a vector database or SQLite and serving them via MCP or a REST API is well within the scope of modern AI-assisted coding.

Discussion

1 comment analyzed.

Competitors mentioned: screenpipe

Concerns raised: relevance scoring complexity - time decay alone insufficient for mixed critical old and recent noise contexts, imperfect context selection even with Claude reasoning on timestamps

Feature requests: improved relevance scoring beyond time-based decay, better distinction between critical vs. noise contexts in persistent memory

Competitors

Other products that read as similar to this one : 658 launches clear the similarity bar, closest 8 shown.

Attention rank: #594 of 659 (itself plus its competitors, highest first, normalized so YC and Product Hunt are compared fairly).

Launched 151 days after the earliest competitor.

The niche, labels, vibe code rating and competitor comparison on this page are analysis by Nicheloom. If you use them, please credit nicheloom.com. How you may use our data.