<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Temporal on Nyghtowl</title>
    <link>https://nyghtowl.com/tags/temporal/</link>
    <description>Recent content in Temporal 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/temporal/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>
    <item>
      <title>Durable, flexible multi-agent systems</title>
      <link>https://nyghtowl.com/posts/2026/08/durable-flexible-multi-agent-systems/</link>
      <pubDate>Thu, 06 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://nyghtowl.com/posts/2026/08/durable-flexible-multi-agent-systems/</guid>
      <description>&lt;p&gt;An agent system is a distributed system. You get to choose the framework and how much durability and human oversight the case demands; the tradeoffs are the part you don’t get to avoid.&lt;/p&gt;&#xA;&lt;p&gt;For the last few months, I’ve been building one system to make that concrete: the same multi-agent fleet on Google ADK, on LangGraph, and on both at once, with Temporal as a layer underneath.&lt;/p&gt;&#xA;&lt;h2 id=&#34;where-this-started&#34;&gt;Where this started&lt;/h2&gt;&#xA;&lt;p&gt;&lt;em&gt;Ziggy’s&lt;/em&gt; is the playful imaginary ice cream shop I cooked up to show what it looks like when a multi-agent system handles fleet delivery around Las Vegas. We announced our ADK integration and wanted a demo for Google Cloud Next. The first version showed a multi-agent team assigning deliveries and dealing with an agent or driver disconnecting mid-route. For the AI Engineer World’s Fair, the fleet relocated to San Francisco, picked up LangGraph as a second framework, and got reframed around a harder version of “recover from a disconnect”: keeping a human in the loop. Disconnecting an agent is a machine failing. Waiting on a human is a machine succeeding at doing nothing, correctly, for as long as it takes. A human isn’t a function that returns in 200 milliseconds. They answer in minutes, hours, or after you’ve already redeployed twice.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
