--- title: The thread is the Workflow: Durable AI agents without... description: Manetu's AgentVisor secure runtime uses Temporal Workflows to make LangGraph-based AI agents durable without modifying agent code. Each Agent Protocol Thread... canonical: https://daily.dev/posts/the-thread-is-the-workflow-durable-ai-agents-without-changing-agent-code-sr7kfnbwu twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: The thread is the Workflow: Durable AI agents without changing Agent code | daily.dev og:description: Manetu's AgentVisor secure runtime uses Temporal Workflows to make LangGraph-based AI agents durable without modifying agent code. Each Agent Protocol Thread... og:url: https://daily.dev/posts/the-thread-is-the-workflow-durable-ai-agents-without-changing-agent-code-sr7kfnbwu og:image: https://api.daily.dev/og/posts/Sr7KfnBwu.png og:image:alt: The thread is the Workflow: Durable AI agents without changing Agent code og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # The thread is the Workflow: Durable AI agents without changing Agent code **[Temporal](https://daily.dev/sources/temporal)** · 6 min read · 2 upvotes · 0 comments ## Summary Manetu's AgentVisor secure runtime uses Temporal Workflows to make LangGraph-based AI agents durable without modifying agent code. Each Agent Protocol Thread maps 1:1 to a Temporal Workflow, Runs become Activities, and checkpoints are stored as Workflow state via Update primitives, allowing crash recovery and worker rehydration transparently. The piece covers engineering challenges including long-lived thread retention limits, distinguishing human-in-the-loop resume from crash recovery, Continue-As-New rollover synchronization, and a worker identity bug caused by binary checksumming in a privilege-dropping hardened environment. It also touches on complementary trust mechanisms like host-based identity, credential brokering, and transparent payload encryption. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### how can I make a LangGraph agent durable across crashes without changing its code Run the agent inside a runtime that maps its LangGraph checkpointer onto Temporal Workflow state instead of modifying the agent itself. Each Agent Protocol Thread becomes a dedicated Temporal Workflow, each Run becomes an Activity, and checkpoints update via Temporal's Update primitive, so a crashed worker gets rehydrated elsewhere with its last checkpoint intact. _daily.dev surfaces engineering approaches like this for teams making AI agents production-durable._ ### why does the Temporal Go SDK fail to identify a worker in a hardened, privilege-dropping environment The Temporal Go SDK identifies a worker by checksumming its own binary, and this breaks when the environment aggressively drops privileges before the SDK can read that metadata. The fix is to hand the SDK an explicit build identifier, derived from version-control metadata, before privileges are dropped. _developers hardening AI agent runtimes on Temporal can find edge-case fixes like this via daily.dev._ ### should I keep full LangGraph checkpoint history when running agents on Temporal No, only the latest LangGraph checkpoint needs to be retained when Temporal already stores Workflow history, since Temporal's own Workflow replay can restore an agent to any previous state. Keeping only the latest checkpoint also reduces Temporal history footprint, which matters given Temporal's workflow history size limits, and pruning happens at every checkpoint and Continue-as-New rollover. _teams weighing state retention tradeoffs for long-running agent threads can track patterns like this on daily.dev._ --- Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#workflow-orchestration](https://daily.dev/tags/workflow-orchestration), [#langgraph](https://daily.dev/tags/langgraph) [View this post on daily.dev](https://daily.dev/posts/the-thread-is-the-workflow-durable-ai-agents-without-changing-agent-code-sr7kfnbwu) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"The thread is the Workflow: Durable AI agents without changing Agent code","url":"https://daily.dev/posts/the-thread-is-the-workflow-durable-ai-agents-without-changing-agent-code-sr7kfnbwu","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/the-thread-is-the-workflow-durable-ai-agents-without-changing-agent-code-sr7kfnbwu"},"datePublished":"2026-09-03T13:04:40.577Z","dateModified":"2026-09-03T13:19:48.566Z","description":"Manetu's AgentVisor secure runtime uses Temporal Workflows to make LangGraph-based AI agents durable without modifying agent code. Each Agent Protocol Thread...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/b1d699578f1986b0a8f725b92ce4acdf?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/b1d699578f1986b0a8f725b92ce4acdf?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Temporal","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Temporal","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/65290ca7e3ab46a7b1df76f2757800c2","url":"https://daily.dev/sources/temporal"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/the-thread-is-the-workflow-durable-ai-agents-without-changing-agent-code-sr7kfnbwu","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":2},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,workflow-orchestration,langgraph","timeRequired":"PT6M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Temporal","item":"https://daily.dev/sources/temporal"},{"@type":"ListItem","position":3,"name":"The thread is the Workflow: Durable AI agents without changing Agent code"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/the-thread-is-the-workflow-durable-ai-agents-without-changing-agent-code-sr7kfnbwu#faq","mainEntity":[{"@type":"Question","name":"how can I make a LangGraph agent durable across crashes without changing its code","acceptedAnswer":{"@type":"Answer","text":"Run the agent inside a runtime that maps its LangGraph checkpointer onto Temporal Workflow state instead of modifying the agent itself. Each Agent Protocol Thread becomes a dedicated Temporal Workflow, each Run becomes an Activity, and checkpoints update via Temporal's Update primitive, so a crashed worker gets rehydrated elsewhere with its last checkpoint intact. daily.dev surfaces engineering approaches like this for teams making AI agents production-durable."}},{"@type":"Question","name":"why does the Temporal Go SDK fail to identify a worker in a hardened, privilege-dropping environment","acceptedAnswer":{"@type":"Answer","text":"The Temporal Go SDK identifies a worker by checksumming its own binary, and this breaks when the environment aggressively drops privileges before the SDK can read that metadata. The fix is to hand the SDK an explicit build identifier, derived from version-control metadata, before privileges are dropped. developers hardening AI agent runtimes on Temporal can find edge-case fixes like this via daily.dev."}},{"@type":"Question","name":"should I keep full LangGraph checkpoint history when running agents on Temporal","acceptedAnswer":{"@type":"Answer","text":"No, only the latest LangGraph checkpoint needs to be retained when Temporal already stores Workflow history, since Temporal's own Workflow replay can restore an agent to any previous state. Keeping only the latest checkpoint also reduces Temporal history footprint, which matters given Temporal's workflow history size limits, and pruning happens at every checkpoint and Continue-as-New rollover. teams weighing state retention tradeoffs for long-running agent threads can track patterns like this on daily.dev."}}]} ```