<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Memory on Nyghtowl</title>
    <link>https://nyghtowl.com/tags/memory/</link>
    <description>Recent content in Memory on Nyghtowl</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>&lt;a href=&#34;https://creativecommons.org/licenses/by-nc-sa/4.0/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;CC BY-NC-SA 4.0&lt;/a&gt;</copyright>
    <lastBuildDate>Thu, 03 Sep 2026 17:02:58 +0000</lastBuildDate>
    <atom:link href="https://nyghtowl.com/tags/memory/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What Does an AI Agent Need to Remember?</title>
      <link>https://nyghtowl.com/posts/2026/09/what-does-an-agent-need-to-remember/</link>
      <pubDate>Thu, 03 Sep 2026 17:02:58 +0000</pubDate>
      <guid>https://nyghtowl.com/posts/2026/09/what-does-an-agent-need-to-remember/</guid>
      <description>&lt;p&gt;&lt;strong&gt;TL;DR:&lt;/strong&gt; We use “memory” as a catch-all, but an AI agent needs different information for different jobs. Context gives the model what it needs for the current decision. Memory brings useful information forward. State tells the application what is true and where the work stands. Understanding those roles matters more as the agent capabilities grow and work stretches across model calls, tool calls, waits on humans and failures. The separation is a tool for clarity. You could call all of it memory; the point is that each piece needs to be handled differently, and handling them well is what makes the agent more capable.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
