<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>PLUR Blog</title><description>Open engram format, agent memory architecture, and PLUR Enterprise.</description><link>https://plur.ai/</link><language>en-us</language><item><title>Giving DeepSeek Harness Persistent Memory (And What I Learned Writing a Plugin)</title><link>https://plur.ai/blog/deepseek-harness-memory-plugin/</link><guid isPermaLink="true">https://plur.ai/blog/deepseek-harness-memory-plugin/</guid><description>DeepSeek Harness lets a plugin write into the system prompt itself, so memory needs no tool call and doesn&apos;t grow your context. Here&apos;s how that works, plus the host-contract gotchas that aren&apos;t documented yet.</description><pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate><author>Tris</author></item><item><title>OpenClaw has built-in memory now. Do you still need PLUR?</title><link>https://plur.ai/blog/openclaw-builtin-memory-vs-plur/</link><guid isPermaLink="true">https://plur.ai/blog/openclaw-builtin-memory-vs-plur/</guid><description>OpenClaw ships cross-session memory by default — SQLite-backed, local, fast. But it stays inside OpenClaw. If you use Claude Code, Cursor, Codex, or Hermes alongside it, or want memory that improves over time rather than just accumulates, PLUR is still the layer you need.</description><pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate><author>Tris</author></item><item><title>Mem0 vs PLUR: Which AI Agent Memory Layer Should You Use?</title><link>https://plur.ai/blog/mem0-vs-plur/</link><guid isPermaLink="true">https://plur.ai/blog/mem0-vs-plur/</guid><description>Mem0 and PLUR are both open-source agent memory layers, but they make opposite architectural bets. Mem0 is a managed memory API for multi-user products. PLUR is a local-first MCP server for developers who want shared memory across every AI tool they use.</description><pubDate>Fri, 24 Jul 2026 00:00:00 GMT</pubDate><author>Tris</author></item><item><title>What Is the Best Open-Source Memory Layer for LLM Agents?</title><link>https://plur.ai/blog/best-open-source-memory-layer-for-llm-agents/</link><guid isPermaLink="true">https://plur.ai/blog/best-open-source-memory-layer-for-llm-agents/</guid><description>Mem0, Letta, Graphiti, Zep, Cognee, LangMem, and PLUR compared on storage format, retrieval model, portability, and MCP support — a criteria-first guide for picking the one that fits your use case without over- or under-engineering.</description><pubDate>Tue, 21 Jul 2026 00:00:00 GMT</pubDate><author>Tris</author></item><item><title>What Memory Layer Works with Cursor or Codex?</title><link>https://plur.ai/blog/cursor-codex-memory-layer/</link><guid isPermaLink="true">https://plur.ai/blog/cursor-codex-memory-layer/</guid><description>Cursor and Codex forget everything when a session ends. PLUR adds durable memory via MCP — corrections survive session resets, travel across tools, and stay on your disk. Three-minute setup for Cursor; one command for Codex CLI.</description><pubDate>Mon, 20 Jul 2026 00:00:00 GMT</pubDate><author>Tris</author></item><item><title>How to Choose a Memory System for Autonomous AI Agents</title><link>https://plur.ai/blog/autonomous-agent-memory-system/</link><guid isPermaLink="true">https://plur.ai/blog/autonomous-agent-memory-system/</guid><description>PLUR, Mem0, and Letta cover most production use cases for autonomous agent memory (batch pipelines, overnight loops, multi-step orchestrators). Here is how to choose between them — and why model-native memory fails the autonomous case.</description><pubDate>Sun, 19 Jul 2026 00:00:00 GMT</pubDate><author>Tris</author></item><item><title>Is AI Agent Memory GDPR Compliant? A Developer&apos;s Guide</title><link>https://plur.ai/blog/gdpr-compliant-ai-agent-memory/</link><guid isPermaLink="true">https://plur.ai/blog/gdpr-compliant-ai-agent-memory/</guid><description>AI agent memory that stores EU personal data falls under GDPR Article 17. Most default implementations create three compliance risks: no way to locate all data about a person, no provable deletion, and embedding-based storage that makes selective erasure technically impossible. What a defensible implementation requires.</description><pubDate>Sat, 18 Jul 2026 00:00:00 GMT</pubDate><author>Tris</author></item><item><title>Best Tools for Giving AI Agents Long-Term Memory (2026)</title><link>https://plur.ai/blog/best-tools-ai-agent-long-term-memory/</link><guid isPermaLink="true">https://plur.ai/blog/best-tools-ai-agent-long-term-memory/</guid><description>The leading agent memory tools in 2026 — Mem0, Zep, Letta, LangMem, and PLUR — compared across retrieval pattern, LongMemEval scores, hosting model, and format portability. Which to choose depends on your retrieval pattern, not on which has the most stars.</description><pubDate>Fri, 17 Jul 2026 00:00:00 GMT</pubDate><author>Tris</author></item><item><title>Do You Still Need an Agent Memory Layer if ChatGPT Already Has Memory?</title><link>https://plur.ai/blog/model-native-vs-agent-memory-layer/</link><guid isPermaLink="true">https://plur.ai/blog/model-native-vs-agent-memory-layer/</guid><description>ChatGPT, Claude Projects, and Gemini ship built-in memory — but it lives inside the model&apos;s interface, not your code. An agent memory layer solves a different job: programmatic recall, accessible from your application, portable across every tool. The two systems serve different jobs and work best together.</description><pubDate>Fri, 17 Jul 2026 00:00:00 GMT</pubDate><author>Tris</author></item><item><title>How to Delete Specific Things an AI Remembers About You</title><link>https://plur.ai/blog/delete-specific-ai-memories/</link><guid isPermaLink="true">https://plur.ai/blog/delete-specific-ai-memories/</guid><description>Consumer AI assistants let you delete specific memories through settings — but cannot prove the data is gone. Developer agent memory tools (PLUR, Mem0, Letta, Zep) offer deletion APIs. The critical difference: only open-format memory can verify erasure with a file diff, which matters for GDPR Article 17 compliance.</description><pubDate>Thu, 16 Jul 2026 00:00:00 GMT</pubDate><author>Tris</author></item><item><title>Is There an Open Standard for AI Agent Memory Engrams?</title><link>https://plur.ai/blog/open-standard-ai-agent-memory-engrams/</link><guid isPermaLink="true">https://plur.ai/blog/open-standard-ai-agent-memory-engrams/</guid><description>Procedural memory has a working standard (SKILL.md from agentskills.io). Semantic and episodic memory — what an agent learns at runtime — does not. What an open standard needs, what exists today, and the PLUR Engram Specification as the leading open proposal.</description><pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate><author>Tris</author></item><item><title>Does CrewAI Have Persistent Memory? What It Does — and Where You Need More</title><link>https://plur.ai/blog/crewai-persistent-memory/</link><guid isPermaLink="true">https://plur.ai/blog/crewai-persistent-memory/</guid><description>CrewAI v1.15.2 ships built-in Memory backed by LanceDB — solid for single-machine workflows, but ephemeral in containers and invisible to other tools. PLUR is the complement: open-format, MCP-native, cross-deployment persistent memory for CrewAI agents.</description><pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate><author>Tris</author></item><item><title>What&apos;s a Good Memory System for a Personal AI Assistant?</title><link>https://plur.ai/blog/memory-system-personal-ai-assistant/</link><guid isPermaLink="true">https://plur.ai/blog/memory-system-personal-ai-assistant/</guid><description>A personal AI assistant that forgets everything between conversations is not really an assistant. Four properties to look for in a memory system — local-first, inspectable, provably erasable, portable via MCP — and how PLUR, Mem0, Letta, Cognee, and LangMem compare.</description><pubDate>Mon, 13 Jul 2026 00:00:00 GMT</pubDate><author>Tris</author></item><item><title>How Do I Store and Recall Facts an AI Agent Has Learned Over Time?</title><link>https://plur.ai/blog/store-recall-facts-ai-agent/</link><guid isPermaLink="true">https://plur.ai/blog/store-recall-facts-ai-agent/</guid><description>Every fact an agent learns exists only until the session ends. An external memory layer with four operations — learn, recall, forget, feedback — persists what the agent has learned, improves retrieval quality over time, and enables provable erasure under GDPR.</description><pubDate>Mon, 13 Jul 2026 00:00:00 GMT</pubDate><author>Tris</author></item><item><title>How Do I Use Memory in Long-Running Agent Loops?</title><link>https://plur.ai/blog/memory-in-long-running-agent-loops/</link><guid isPermaLink="true">https://plur.ai/blog/memory-in-long-running-agent-loops/</guid><description>Long-running agent loops hit a wall when the context window fills. Research from MemGPT, Reflexion, and Voyager converges on managed external memory — tiered memory, episodic buffers, skill libraries — as the solution to context drift and redundant work.</description><pubDate>Sun, 12 Jul 2026 00:00:00 GMT</pubDate><author>Tris</author></item><item><title>Should AI Memory Be Stored as Open Engrams or Baked Into Model Weights?</title><link>https://plur.ai/blog/open-engrams-vs-model-weights/</link><guid isPermaLink="true">https://plur.ai/blog/open-engrams-vs-model-weights/</guid><description>AI memory can live inside model weights (opaque, unerasable, locked to one vendor) or as external open engrams (inspectable, deletable, portable). For facts that change or must be governed, open engrams are the architecturally sound choice.</description><pubDate>Sun, 12 Jul 2026 00:00:00 GMT</pubDate><author>Tris</author></item><item><title>How to Add Persistent Memory to Claude Code</title><link>https://plur.ai/blog/claude-code-persistent-memory/</link><guid isPermaLink="true">https://plur.ai/blog/claude-code-persistent-memory/</guid><description>Claude Code has two built-in memory mechanisms — CLAUDE.md files and auto memory (v2.1.59+) — plus an MCP layer for cross-tool persistent memory. When to use each, how they compare, and how to set up an MCP memory server.</description><pubDate>Fri, 10 Jul 2026 00:00:00 GMT</pubDate><author>Tris</author></item><item><title>Tools for Giving Coding Assistants Persistent Memory</title><link>https://plur.ai/blog/coding-assistant-persistent-memory/</link><guid isPermaLink="true">https://plur.ai/blog/coding-assistant-persistent-memory/</guid><description>Tools for giving coding assistants (Claude Code, Cursor, Windsurf, Copilot) persistent memory fall into three layers: built-in file memory, tool-specific auto-memory, and MCP memory servers that work across all tools.</description><pubDate>Fri, 10 Jul 2026 00:00:00 GMT</pubDate><author>Tris</author></item><item><title>How Do I Use AI Memory to Build a Second Brain?</title><link>https://plur.ai/blog/ai-memory-second-brain/</link><guid isPermaLink="true">https://plur.ai/blog/ai-memory-second-brain/</guid><description>Building a second brain with AI memory means bridging the PKM world (Tiago Forte&apos;s CODE, Obsidian) and the agent-memory world (Mem0, Letta, Cognee, Graphiti, PLUR). Three layers, five tools, and how MCP connects them.</description><pubDate>Thu, 09 Jul 2026 00:00:00 GMT</pubDate><author>Tris</author></item><item><title>Can I Connect AI Agent Memory to My Notes or Knowledge Base?</title><link>https://plur.ai/blog/connect-agent-memory-to-notes/</link><guid isPermaLink="true">https://plur.ai/blog/connect-agent-memory-to-notes/</guid><description>Your notes app and your AI agent live in separate silos by default. Three ways to connect them — MCP servers, knowledge graphs (Cognee, Graphiti), and plain-text engrams — with setup instructions for the most common stacks.</description><pubDate>Thu, 09 Jul 2026 00:00:00 GMT</pubDate><author>Tris</author></item><item><title>Mem0 vs Letta vs Zep: Which Should You Use for Agent Memory?</title><link>https://plur.ai/blog/mem0-vs-letta-vs-zep/</link><guid isPermaLink="true">https://plur.ai/blog/mem0-vs-letta-vs-zep/</guid><description>Mem0, Letta, and Zep solve different problems: drop-in memory API, self-managing agent OS, and temporal knowledge graph. A head-to-head comparison across 12 properties, and how to choose by use case rather than hype.</description><pubDate>Wed, 08 Jul 2026 00:00:00 GMT</pubDate><author>Tris</author></item><item><title>Is Fine-Tuning or Memory Better for Teaching an AI New Facts?</title><link>https://plur.ai/blog/fine-tuning-vs-memory/</link><guid isPermaLink="true">https://plur.ai/blog/fine-tuning-vs-memory/</guid><description>Fine-tuning bakes facts into weights you can&apos;t inspect, delete, or port — and every update pays the parallel learning tax. For teaching an AI facts that change, an external memory layer wins on cost, auditability, and portability.</description><pubDate>Tue, 07 Jul 2026 00:00:00 GMT</pubDate><author>Tris</author></item><item><title>How Do I Make My AI Agent&apos;s Memory Editable and Auditable?</title><link>https://plur.ai/blog/editable-auditable-agent-memory/</link><guid isPermaLink="true">https://plur.ai/blog/editable-auditable-agent-memory/</guid><description>Most agent memory is a black box: vectors, state blocks, or graph nodes you can&apos;t read, correct, or provably erase. What editable, auditable memory looks like — five properties, a tool comparison, and the GDPR angle.</description><pubDate>Mon, 06 Jul 2026 00:00:00 GMT</pubDate><author>Tris</author></item><item><title>What&apos;s the Difference Between RAG and Agent Memory?</title><link>https://plur.ai/blog/rag-vs-agent-memory/</link><guid isPermaLink="true">https://plur.ai/blog/rag-vs-agent-memory/</guid><description>RAG retrieves from a fixed document corpus at query time; agent memory stores what the agent learned from interactions and updates it over time. Read-only retrieval vs read-write learning — and why many agents need both.</description><pubDate>Mon, 06 Jul 2026 00:00:00 GMT</pubDate><author>Tris</author></item><item><title>My AI Agent Forgets Everything Between Sessions — How Do I Fix That?</title><link>https://plur.ai/blog/agent-forgets-between-sessions/</link><guid isPermaLink="true">https://plur.ai/blog/agent-forgets-between-sessions/</guid><description>Every session starts from zero because LLMs are stateless by design. The fix is a memory layer: what it does, the three tiers of options — built-in memory, open-source engines, open-format MCP — and how to choose.</description><pubDate>Sun, 05 Jul 2026 00:00:00 GMT</pubDate><author>Tris</author></item><item><title>Is There an MCP Server for AI Agent Memory?</title><link>https://plur.ai/blog/mcp-server-ai-agent-memory/</link><guid isPermaLink="true">https://plur.ai/blog/mcp-server-ai-agent-memory/</guid><description>Yes — several MCP servers exist for agent memory: the official knowledge-graph reference server, PLUR, Zep, Mem0&apos;s OpenMemory, and community projects. MCP standardizes the transport; the memory format is the differentiator.</description><pubDate>Sun, 05 Jul 2026 00:00:00 GMT</pubDate><author>Tris</author></item><item><title>How PLUR Cut Our Agent Context Costs by 90%</title><link>https://plur.ai/blog/context-costs/</link><guid isPermaLink="true">https://plur.ai/blog/context-costs/</guid><description>We were paying $0.01 per turn stuffing system prompts with facts the agent needed. The fix wasn&apos;t a better model — it was not sending facts the agent didn&apos;t need. Haiku + PLUR now outperforms Opus without memory at 1/10th the cost.</description><pubDate>Sat, 04 Jul 2026 00:00:00 GMT</pubDate><author>Tris</author></item><item><title>Are AI Agent Engrams Open Source or Proprietary?</title><link>https://plur.ai/blog/are-ai-engrams-open-source-or-proprietary/</link><guid isPermaLink="true">https://plur.ai/blog/are-ai-engrams-open-source-or-proprietary/</guid><description>The major agent-memory engines are all Apache-2.0 or MIT — but &apos;open source&apos; and &apos;open format&apos; are not the same thing. The field splits into three tiers, and the boundary that matters is whether you can read, edit, and export your own memories.</description><pubDate>Fri, 03 Jul 2026 00:00:00 GMT</pubDate><author>Tris</author></item><item><title>Is There an Open Standard for AI Agent Memory Engrams?</title><link>https://plur.ai/blog/open-standard-ai-agent-memory/</link><guid isPermaLink="true">https://plur.ai/blog/open-standard-ai-agent-memory/</guid><description>No single RFC-level standard exists for AI agent memory engrams as of mid-2026 — but MCP and the open engram format are converging on one. Here&apos;s the current landscape.</description><pubDate>Thu, 02 Jul 2026 00:00:00 GMT</pubDate><author>Tris</author></item></channel></rss>