Alternatives
Products that do what CodeYam CLI & Memory does
Comprehensive memory management for Claude Code
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13PM
This is my attempt in building a memory that evolves and persist for claude code. My approach is inspired from Zettelkasten method, memories are atomic, connected and dynamic. Existing memories can evolve based on newer memories. In the background it uses LLM to handle linking and evolution. I have only used it with claude code so far, it works well with me but still early stage, so rough edges likely. I'm planning to extend it to other coding agents as I use several different agents during development. Looking for feedbacks!
Jan 2026 · github.com
- 14
- 15
- 16
- 17AM
Hi HN, I have been recently geeking on agentic memories, and I believe I finally came up with something that works. I spent the last couple of weeks building a memory[0] for Claude Code that dynamically evolve as you talk with it. I followed a new paradigm inspired from zettelkasten method. Whenever Claude discover something new in the codebase or during your conversation with it, it writes a note about it, link it with related memories, update the related memories accordingly, and store it in chromaDB (this part where it keeps self-evolving based on new inputs). Later when you ask it to…
Jan 2026 · github.com
- 18AA
Hi HN. Live-Memory is an open-source Claude Code plugin / MCP server that serves as an always up-to-date memory of your codebase. It uses a separate, low-cost, large-context-window model to distill your repo's organization, conventions and general structure. It observes the primary agent's activity and builds an understanding of your repo passively over time. This way, when you start a new Claude Code session, your primary agent queries Live-Memory via one read-only ask_live_memory tool and bootstraps its understanding of the codebase for the particular task at hand, instead of…
Jul 2026 · github.com
- 19PM
I built an MCP server that gives Claude Code long-term memory across sessions, backed by infrastructure you control. Every Claude Code session starts from zero, no memory of previous sessions. This server uses mem0ai as a library and exposes 11 MCP tools for storing, searching, and managing memories. Qdrant handles vector storage, Ollama runs embeddings locally (bge-m3), and Neo4j optionally builds a knowledge graph. Some engineering details HN might find interesting: - Zero-config auth: auto-reads Claude Code's OAT token from ~/.claude/.credentials.json, detects token type (OAT vs…
Feb 2026 · github.com
- 20PC
Hi HN, I'm Rob. Contextify indexes every Claude Code and Codex session on your machine into one local, searchable database. The current session, in either tool, can search all of it: /total-recall in Claude Code, $total-recall in Codex. Demo: https://www.youtube.com/watch?v=FvrvRGp4C9M | Mac app: https://contextify.sh (App Store or DMG) | Linux: CLI with a one-line installer, same search. No signup. I split my work between Claude Code and Codex. When I burn through rate limits on one, I switch to the other, and new models keep leapfrogging each other, so the…
Jul 2026 · contextify.sh
- 21
- 22IB
I wanted to share a project I have been working on over the past week. It is a simple local memory system that saves your sessions into Markdown files, which can be viewed later. I developed this after using Claude Mem. I really enjoyed working with it, but it was consuming a lot of RAM, and each Claude session was becoming a major resource hog. I also tried other plugins and MCP solutions, but ran into similar issues, either slow performance or concerns about data being sent elsewhere. Because privacy was a big thing for me, I decided to build my own solution that keeps all data local.
Feb 2026 · github.com
- 23HP
Hi HN! I'm building Hopsule. If you use AI coding tools like Cursor, Copilot, or Claude, you’ve probably seen this happen: The AI writes good code - but it ignores your architecture. It doesn’t know: - why you chose a specific pattern - which conventions your team agreed on - which decisions are already locked in So it falls back to generic patterns, outdated examples, or random GitHub training data. Over time this slowly breaks the consistency of the codebase. Most teams try to fix this with: - giant Markdown files - wiki pages - long prompts - Slack threads But those aren't…
Mar 2026
- 24HN
I built Hydra because I kept losing my flow when Claude Code hit usage limits mid-task. I would copy context, open another tool, and then re-explain everything. This would be super annoying for me. Hydra wraps your AI coding CLIs (Claude Code, Codex, OpenCode, Pi, or any terminal-based tool) in a single command. It monitors terminal output for rate limit patterns, and when one provider runs out, you switch to another with one keypress. Your conversation history, git diff, and recent commits are automatically copied to your clipboard so you can paste and keep going. The fallback chain is…
Apr 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →