
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Nimbus Systems</title>
      <link>https://nimbusarchitect.com/blog</link>
      <description>Solutions Architect at AWS. Writing about AI/ML, cloud architecture, cybersecurity, and quantitative research.</description>
      <language>en-us</language>
      <managingEditor>lilphd99@gmail.com (Benjamin Lee)</managingEditor>
      <webMaster>lilphd99@gmail.com (Benjamin Lee)</webMaster>
      <lastBuildDate>Mon, 03 Nov 2025 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://nimbusarchitect.com/tags/langgraph/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://nimbusarchitect.com/blog/langgraph-agentic-workflows</guid>
    <title>State of the Agent</title>
    <link>https://nimbusarchitect.com/blog/langgraph-agentic-workflows</link>
    <description>A ReAct loop dazzles in a demo and buckles in production. LangGraph makes an agent’s state explicit—the dull discipline that keeps real systems standing.</description>
    <pubDate>Mon, 03 Nov 2025 00:00:00 GMT</pubDate>
    <author>lilphd99@gmail.com (Benjamin Lee)</author>
    <category>ai-agents</category><category>langgraph</category><category>langchain</category><category>python</category><category>llm</category>
  </item>

  <item>
    <guid>https://nimbusarchitect.com/blog/langgraph-stateful-agents-production</guid>
    <title>State of Grace</title>
    <link>https://nimbusarchitect.com/blog/langgraph-stateful-agents-production</link>
    <description>A demo agent that crashes loses everything; a production one must not. How LangGraph keeps state, survives failures and resumes where it left off.</description>
    <pubDate>Wed, 12 Nov 2025 00:00:00 GMT</pubDate>
    <author>lilphd99@gmail.com (Benjamin Lee)</author>
    <category>ai-agents</category><category>langgraph</category><category>langchain</category><category>python</category><category>llm</category>
  </item>

    </channel>
  </rss>
