Persistia: Give Claude Code the persistent memory it was missing (open source)
Persistia introduces a self-updating persistent memory feature for Claude Code, enhancing its functionality as an operational co-pilot. This tool scans projects for relevant information and maintains an up-to-date memory without manual input. It allows users to schedule tasks and manage their projects more efficiently, all while being open-source and free to use.
- ▪Persistia provides Claude Code with persistent memory, eliminating the need for repetitive context input.
- ▪The tool scans entire projects and updates automatically, ensuring it stays current with changes.
- ▪Users can schedule tasks in plain language, allowing for automated execution with full context.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/bernardohcrocha/persistia-for-claude-code |
| Publication time | Wed, 03 Jun 2026 17:44:13 +0000 |
| Retrieval time | 2026-06-03T17:52:51.848Z |
| Last seen | 2026-06-03T17:52:51.848Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 2ndRJ4aHSJUF |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Persistia Self-updating persistent memory for Claude Code. Give Claude Code the persistent memory it was missing and turn it into your operational co-pilot. Claude Code has no operational memory. Every session starts from zero. You re-explain your stack, paste context, repeat yourself. Persistia fixes that. On first run, it scans your entire project — code, architecture, docs, and configs. Reads your .env files and uses credentials you already have. Stores everything in small, focused files with a navigation index. Then monitors changes via git diff: 1,000 files, 3 changed, it reads 3. Token-efficient by design. The result: an agent that always knows your full project and stays up-to-date automatically — even as you ship new features, add docs, or change your stack. Minimum input.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.