Alternatives
Products that do what Clio does
Memory that knows why things connect.
- 1
- 2
- 3YA
Built this for my LLM workflows - needed searchable, persistent memory that wouldn't blow up storage costs. I also wanted to use it locally for my research. It's a content-addressed storage system with block-level deduplication (saves 30-40% on typical codebases). I have integrated the CLI tool into most of my workflows in Zed, Claude Code, and Cursor, and I provide the prompt I'm currently using in the repo. The project is in C++ and the build system is rough around the edges but is tested on macOS and Ubuntu 24.04.
2025 · github.com
- 4
- 5
- 6RG
Hey HN! I'm José, and I built Recall to solve a problem that was driving me crazy. The Problem: I use Claude for coding daily, but every conversation starts from scratch. I'd explain my architecture, coding standards, past decisions... then hit the context limit and lose everything. Next session? Start over. The Solution: Recall is an MCP (Model Context Protocol) server that gives Claude persistent memory using Redis + semantic search. Think of it as long-term memory that survives context limits and session restarts. How it works: - Claude stores important context as "memories" during…
Oct 2025 · npmjs.com
- 7GL
Hey HN! We're Paul, Preston, and Daniel from Zep. We've just open-sourced Graphiti, a Python library for building temporal Knowledge Graphs using LLMs. Graphiti helps you create and query graphs that evolve over time. Knowledge Graphs have been explored extensively for information retrieval. What makes Graphiti unique is its ability to build a knowledge graph while handling changing relationships and maintaining historical context. At Zep, we build a memory layer for LLM applications. Developers use Zep to recall relevant user information from past conversations without including the entire…
2024 · github.com
- 8
- 9
- 10
- 11
- 12IR
Hey HN! I built a proof-of-concept for AI memory using Git instead of vector databases. The insight: Git already solved versioned document management. Why are we building complex vector stores when we could just use markdown files with Git's built-in diff/blame/history? How it works: Memories stored as markdown files in a Git repo Each conversation = one commit git diff shows how understanding evolves over time BM25 for search (no embeddings needed) LLMs generate search queries from conversation context Example: Ask "how has my project evolved?" and it uses git diff to show actual…
2025 · github.com
- 13
- 14
The memory layer that decides what's worth remembering
14d ago · skynetlab-cortex.com
- 15RL
Jun 2026 · github.com
- 16
- 17
- 18CO
I keep running in the same problem of each AI app “remembers” me in its own silo. ChatGPT knows my project details, Cursor forgets them, Claude starts from zero… so I end up re-explaining myself dozens of times a day across these apps. The deeper problem 1. Not portable – context is vendor-locked; nothing travels across tools. 2. Not relational – most memory systems store only the latest fact (“sticky notes”) with no history or provenance. 3. Not yours – your AI memory is sensitive first-party data, yet you have no control over where it lives or how it’s queried. Demo video:…
2025 · github.com
- 19RA
Hey HN! I built Retain as the evolution of claude-reflect (github.com/BayramAnnakov/claude-reflect). The original problem: I use Claude Code/Codex daily for coding, plus claude.ai and ChatGPT occasionally. Every conversation contains decisions, corrections, and patterns I forget existed weeks later. I kept re-explaining the same preferences. claude-reflect was a CLI tool that extracted learnings from Claude Code sessions. Retain takes this further with a native macOS app that: - Aggregates conversations from Claude Code, claude.ai, ChatGPT, and Codex CLI - Instant full-text…
Jan 2026 · github.com
- 20
- 21BA
I've been working on this tool that lets you build a personal knowledge graph from articles, blog posts, podcasts, YouTube videos, and other content you find interesting online. You can safely forget everything and trust that Recall will resurface it when something new that is related comes up. Looking forward to your thoughts and feedback on how it could be improved! The original version of Recall was posted last year nov on HN: https://news.ycombinator.com/item?id=33425947 Since then I have pivoted to a browser extension.
2023 · recall.wiki
- 22
- 23
- 24TN
Hey, HN Community! I'm a Brazilian software engineer, and my educational journey led to a significant discovery. During my master's degree, I often struggled to recall foundational concepts studied years earlier, which were crucial for my current studies. This challenge sparked a reevaluation of traditional note-taking and inspired the creation of cmaps.io. Human thinking is inherently associative, not linear. We often draw connections between learned concepts unconsciously. To leverage this natural process, making these connections explicit is essential – and that's precisely what cmaps.io…
2023 · cmaps.io
Ranked by how close each launch is in meaning, then by votes. Refine with a description →