← Reddit

built chat app which cites what memories it used

Reddit · MontyOW · July 10, 2026
A chat application was built featuring citations that identify which memories were used in responses and allow users to view, edit, or delete them through a side panel. The system addresses problems with existing memory systems through scoped memory management, preventing cross-chat content bleed, and achieved top scores on LongMemEval-S benchmarks after a ten-month development cycle.

Detailed Analysis

A developer has released c137.ai, a chat application built around a memory system designed to address a persistent frustration with Claude's native memory feature: stale or irrelevant recollections bleeding across unrelated conversations. Rather than treating memory as an opaque black box that silently injects context, the tool cites the specific memories it draws on for any given response, letting users click through to see the exact source turn in the conversation that generated each memory. This creates an auditable trail from raw conversation to stored memory to eventual reuse, addressing a core usability gap in how AI memory systems currently operate—users are typically forced to guess why a model said something or re-explain context because there's no way to inspect or correct the underlying memory store.

The architecture also introduces explicit scoping rules that mirror how people actually compartmentalize their work: individual chats are isolated from each other by default, preventing unwanted cross-contamination, but memories can be deliberately pulled in via @ mentions when relevant. Inside a "project" container, however, every chat, document, and image shares visibility with every other chat in that project, letting related work build on itself while still respecting boundaries between unrelated tasks. This is a notable departure from the more monolithic memory approaches seen in mainstream assistants, where all context tends to live in a single undifferentiated pool that expands and contracts with limited user control.

The developer backs the project with a benchmark claim rather than just anecdotal design rationale, reporting a score of 470/500 on LongMemEval-S, a benchmark specifically built to evaluate long-term conversational memory in LLM-based assistants by testing recall accuracy, temporal reasoning, and knowledge updates across extended interaction histories. Framing the release as the product of roughly ten months of development, and explicitly distancing it from "vibecoded memory snake oil," the developer also open-sourced an evaluation runner so the claimed top score can be independently reproduced and checked for prompt manipulation or other benchmark-gaming tactics—an important credibility signal given how easy it is to inflate self-reported LLM benchmark numbers.

This release fits into a broader industry-wide push to solve the "memory problem" in conversational AI, an area where Anthropic, OpenAI, and Google have all shipped features over the past year but have generally prioritized convenience and automatic recall over transparency and user control. As models are increasingly used for long-running, multi-session work—coding projects, research, personal assistants—the ability to see, audit, and edit what a model "remembers" becomes as important as the memory itself, since incorrect or outdated context can silently corrupt outputs in ways that are hard to detect. Independent projects like c137.ai, which layer citation, provenance, and reproducible benchmarking on top of a memory system, reflect a growing appetite in the developer community for more inspectable, user-governed alternatives to the increasingly capable but often opaque memory features being built directly into major frontier chat products.

Read original article →