June 21, 2026

Memory lane or markdown drama?

Stop wasting tokens and re explaining your project between sessions

A new tool promises to stop the repeated project pep talk — but commenters are already asking, “Isn’t this just a fancy notes file?”

TLDR: Recall is a local tool that saves a short project recap so users don’t have to re-explain everything in every new Claude coding session. Commenters were split between calling it a smart privacy-friendly fix and dismissing it as something a simple notes file, ticket system, or Claude itself could already handle.

A new plugin called Recall is pitching itself as the cure for one of the most annoying parts of coding with AI helpers: starting every new chat from scratch and having to re-explain your whole project again. Its big promise is simple and kind of juicy: it keeps a running memory of your work on your own computer, writes a short recap, and does it without sending your private code or notes anywhere else. For privacy-minded users, that was the headline-grabber. For everyone else? The comments instantly turned into a “do we really need another tool for this?” showdown.

The strongest reactions were split between “finally, useful!” and “isn’t this just a README with extra steps?” One commenter basically shrugged and asked how this beats a session-specific notes file, while another said they already solve the problem with a ticket system and a master project summary. In other words: some people saw a clever lifesaver, others saw a very elaborate way to reinvent a notebook.

Then came the classic AI-tool skepticism. One user asked the question hanging over the whole thread: is this actually better than just asking Claude to do it itself? Ouch. And the funniest drive-by came from the IntelliJ crowd, with a joke that the editor sends “half your project to Claude even if you’re asking some question about Star Wars.” That line pretty much captured the mood: half privacy panic, half eye-roll, with a side of meme energy.

Key Points

  • Recall is presented as a fully local memory system for Claude Code that stores session logs and generates resumable project summaries on-device.
  • The tool writes two project files under `.recall/`: `history.md` for append-only session logging and `context.md` for a condensed summary.
  • Session activity is captured through hooks, and users generate the updated summary by running `/recall:save`.
  • The summarizer uses local extractive methods including TF-IDF, cosine similarity, and TextRank rather than any LLM or external API.
  • Configuration options include output directory, history capture, summary length, redaction, git integration, input-size limits, and a file-based pause mechanism for logging.

Hottest takes

"How does this beat a Session specific README?" — tt_dev
"Is this better than asking claude to do the same things" — dimitrios1
"sends half your project to Claude even if you're asking some question about Star Wars" — comrade1234
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.
Stop wasting tokens and re explaining your project between sessions - Weaving News | Weaving News