nowfound

AI · alternatives · 2026

24 alternatives to recall

Stop wasting Claude Code tokens every time you resume.

Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes. Prices are shown for the 1 we have checked on their own sites, 1 of them free or with a free tier.

  1. 1

    I got tired of Claude Code forgetting all my context every time I open a new session: set-up decisions, how I like my margins, decision history. etc. We built a shared memory layer you can drop in as a Claude Code Skill. It’s basically a tiny memory DB with recall that remembers your sessions. Not magic. Not AGI. Just state. Install in Claude Code: /plugin marketplace add https://github.com/mutable-state-inc/ensue-skill /plugin install ensue-memory # restart Claude Code What it does: (1) persists context between sessions (2) semantic & temportal search (not just…

    Dec 2025 · github.com · its alternatives →

  2. 2

    Stop wasting tokens and re-explaining your project every session. Recall gives Claude Code durable memory — entirely offline. - raiyanyahya/recall

    Jun 2026 · github.com · its alternatives →

  3. 3RG

    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…

    2025 · npmjs.com · its alternatives →

  4. 4

    Store, review, and share your Claude Code sessions

    Mar 2026 · bench.silverstream.ai · its alternatives →

  5. 5

    built this because I got tired of re-teaching Claude Code the same context every session. Preferences, decisions, “we already tried X,” “don’t touch this file,” etc. After a few days it starts to feel like onboarding the same coworker every morning. Most “agent memory” tools auto-save everything. That feels good briefly, then memory turns into a junk drawer and retrieval gets noisy. Total Recall takes the opposite approach: a write gate. Before anything gets promoted, it asks one question: “Will this change future behavior?” If not, it doesn’t get saved. How it works: Daily log first (raw…

    Feb 2026 · github.com · its alternatives →

  6. 6

    Use any model inside Claude Code, keep your Claude plan

    Mar 2026 · edgee.ai · its alternatives →

  7. 7

    I kept slamming into Claude Code limits mid-session and couldn’t find a quick way to see how close I was getting, so I hacked together a tiny local tracker. Streams your prompt + completion usage in real time Predicts whether you’ll hit the cap before the session ends Runs 100 % locally (no auth, no server) Presets for Pro, Max × 5, Max × 20 — tweak a JSON if your plan’s different GitHub: https://github.com/Maciek-roboblog/Claude-Code-Usage-Monitor It’s already spared me a few “why did my run just stop?” moments, but it’s still rough around the edges. Feedback, bug…

    2025 · github.com · its alternatives →

  8. 8

    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 · its alternatives →

  9. 9

    I got tired of sharing AI demos with terminal screenshots or screen recordings. Claude Code already stores full session transcripts locally as JSONL files. Those logs contain everything: prompts, tool calls, thinking blocks, and timestamps. I built a small CLI tool that converts those logs into an interactive HTML replay. You can step through the session, jump through the timeline, expand tool calls, and inspect the full conversation. The output is a single self-contained HTML file — no dependencies. You can email it, host it anywhere, embed it in a blog post, and it works on mobile. Repo:…

    Mar 2026 · github.com · its alternatives →

  10. 10

    Schedule recurring tasks locally and in the cloud easily

    Mar 2026 · claude.ai · its alternatives →

  11. 11

    Comprehensive memory management for Claude Code

    Mar 2026 · codeyam.com · its alternatives →

  12. 12

    Persistent memory for AI coding agents

    Apr 2026 · contextpool.io · its alternatives →

  13. 13
    Recall▲16

    One developer solves it. Every developer knows it.

    Feb 2026 · recall.team · its alternatives →

  14. 14
    Claudebin▲258

    Hi HN, We use Claude Code a lot, and after a long session there isn't a simple way to share exactly what happened with someone else. Prompts, responses, file edits, and tool calls all stay inside the terminal. We built Claudebin to make that easier. It's a plugin that lets you export the current session as a URL containing: - the full message thread - file reads and writes - bash commands - web and MCP calls You can send the link to someone, attach it to a PR, embed part of it, or resume the session locally. It's open source. GitHub:…

    Feb 2026 · claudebin.com · its alternatives →

  15. 15

    Continuous Claude is a CLI wrapper I made that runs Claude Code in an iterative loop with persistent context, automatically driving a PR-based workflow. Each iteration creates a branch, applies a focused code change, generates a commit, opens a PR via GitHub's CLI, waits for required checks and reviews, merges if green, and records state into a shared notes file. This avoids the typical stateless one-shot pattern of current coding agents and enables multi-step changes without losing intermediate reasoning, test failures, or partial progress. The tool is useful for tasks that require many…

    Nov 2025 · github.com · its alternatives →

  16. 16

    Never lose your work again

    2025 · claude-checkpoints.com · its alternatives →

  17. 17

    Did you know Claude Code deletes your session data after 30 days? I found out the hard way when I tried to check my spending history. My session files hit 3GB (2000+ files) and existing tools took 40+ seconds. Rewrote it in Rust with simd-json + rayon. - First run: ~1s (vs 40s+) - Daily use: ~0.04s (1000x faster, cached) - TUI dashboard with daily/weekly/monthly breakdown - Supports Claude Code, Codex CLI, Gemini CLI - Persistent cache — history survives even after CLI deletes files GitHub: https://github.com/mag123c/toktrack Feedback welcome!

    Feb 2026 · github.com · its alternatives →

  18. 18

    Ask Claude Code where your usage went. Token audit, limit diagnosis and usage forensics — built from the session logs already on your machine, nothing leaves it. - kelviq/tare

    Aug 2026 · github.com · its alternatives →

  19. 19

    Never miss a Claude Code session waiting for your input

    Jul 2026 · agentmgr.app · its alternatives →

  20. 20

    Built this after realizing I was spending ~$1400/week on Claude Code with almost no visibility into what was actually consuming tokens. Tools like ccusage give a cost breakdown per model and per day, but I wanted to understand usage at the task level. CodeBurn reads the JSONL session transcripts that Claude Code stores locally (~/.claude/projects/) and classifies each turn into 13 categories based on tool usage patterns (no LLM calls involved). One surprising result: about 56% of my spend was on conversation turns with no tool usage. Actual coding (edits/writes) was…

    Apr 2026 · github.com · its alternatives →

  21. 21
    CCgather▲122

    Document your Claude Code journey

    Feb 2026 · ccgather.com · its alternatives →

  22. 22

    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 · its alternatives →

  23. 23

    AI agent memory, everywhere. claude-mem is open-source memory for Claude Code; cmem links it to any MCP client — Cursor, Codex, more — via one private link.

    Dec 2025 · cmem.ai · its alternatives →

  24. 24

    I kept hitting Claude's 5-hour limit without realizing it, so I made this menu bar app to track it. Shows a color-coded ring (green/orange/red) and countdown to reset. Built it in Swift/SwiftUI, just for myself initially. Right now you have to manually grab your sessionKey from browser DevTools, which is annoying but works. Stores it in macOS Keychain so it's secure. Been actively working on it, already at v1.3.0 with much better UX now. It's open source (MIT) and works with all Claude platforms (web/CLI/desktop/mobile) since they share the quota. Currently…

    Oct 2025 · github.com · its alternatives →

Also compare

Ranked by how close each launch is in meaning, then by votes. Prices were read from each product’s own site when checked and can change. Refine with your own description →