🧵 You told the agent on day one to never expose internal DB IDs. Sixty messages later it builds a new auth flow. Does it still remember? Title: Coding Agents Don't Need Longer History — They Need Intent Continuity URL: The article's premise: bigger context windows and RAG don't fix this. What's missing is a mechanism to check whether past intent still applies right now. Highlight ①🔍 A new axis: intent continuity RAG answers "what's relevant?" Longer context solves capacity. Neither answers "is this still true?" The framework splits recovery, validity checking, and application into distinct steps. Highlight ②⚙️ Supersession detection as the verification core When two records share the same target but disagree, the later one wins chronologically — but records in different scopes (prod vs. prototype) both stay active. This verification layer, the author argues, does heavier lifting than retrieval itself. Highlight ③📊 The numbers back it up On 70 synthetic interactions, keyword search hit 0.57 recall and passed only 4 of 8 tasks. The intent-aware approach hit 1.00 recall, zero violations, and passed all 8 — for about 28% more tokens. A quiet but essential lens for running coding agents on long-lived projects. #AIAgents# #CodingAgents#