---
id: "concept-workflow-state-separation"
type: "concept"
source_timestamps: ["00:10:52"]
tags: ["state-management", "architecture"]
related: ["concept-complete-session-persistence", "action-separate-workflow-state", "prereq-system-state-machines"]
definition: "Maintaining a distinct state object that tracks an agent's progress through a task, separate from its conversational history."
sources: ["s46-anthropic-25b-leak"]
sourceVaultSlug: "s46-anthropic-25b-leak"
originDay: 46
---
# Workflow State Separation

## Definition
Maintaining a **distinct state object** that tracks an agent's progress through a task, separate from its conversational history.

## The Conflation Problem
Nate identifies a common error in agentic frameworks: confusing **conversation state** with **task / workflow state**. When an agent resumes after a crash, knowing *what was said* (conversation history) does not automatically tell the agent *what it was doing* (workflow state).

## What Workflow State Tracks
A proper workflow state answers questions like:

- **What step are we on?**
- **What side effects have already occurred?**
- **Is this operation safe to retry?**
- **What should happen after a restart?**

## Implementation
[[entity-claude-code-d46|Claude Code]] models long-running work as **explicit states** — for example: `planned`, `awaiting approval`, `executing`, `waiting on external party`. These checkpoints are persisted alongside the conversation.

## Mental Model
Likened to **saving a video game state**. Recovery doesn't just restore memory — it restores the agent's exact place in the execution pipeline. This prevents expensive or destructive duplicate actions when resuming.

## Action
[[action-separate-workflow-state]].

## Prerequisite
Requires basic familiarity with [[prereq-system-state-machines]].

## Validation (Enrichment)
Confirmed best practice. Separates episodic memory (chat) from procedural state (tasks), as in AutoGen, CrewAI, and LangGraph state machines.