<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Ai-Memory on John on Lee</title><link>https://john.onlee.io/en/tags/ai-memory/</link><description>Recent content in Ai-Memory on John on Lee</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 03 Aug 2026 00:00:00 +0900</lastBuildDate><atom:link href="https://john.onlee.io/en/tags/ai-memory/index.xml" rel="self" type="application/rss+xml"/><item><title>Coding Agent Memory: Why Storing Everything Fails</title><link>https://john.onlee.io/en/guides/coding-agent-memory/</link><pubDate>Mon, 03 Aug 2026 00:00:00 +0900</pubDate><guid>https://john.onlee.io/en/guides/coding-agent-memory/</guid><description>I build an agent memory platform, and this week we reversed its direction. What store-everything memory breaks, and how to route state, facts, and principles to the tracker, the code, and memory.</description></item><item><title>Does Your Coding Agent Need Memory?</title><link>https://john.onlee.io/en/blog/does-your-coding-agent-need-memory/</link><pubDate>Thu, 14 May 2026 00:00:00 +0900</pubDate><guid>https://john.onlee.io/en/blog/does-your-coding-agent-need-memory/</guid><description>Coding agents re-read the same files and re-ask the same questions every day. What memory actually does for an agent, how it differs from docs, and when it pays off.</description></item></channel></rss>