technical-term · Context & knowledge · maturing · Reviewed
Working state
The current, inspectable record of an agent’s task position, observations, decisions, pending actions, and budgets.
Definition
Working state is the operational state needed to continue an agent run safely: goal, plan, completed steps, tool results, unresolved questions, checkpoints, resource budgets, verifier dispositions, and terminal status. It should be explicit and durable where recovery matters.
State-machine techniques are established; consistent agent-state models and portability are still emerging.
Why it matters
State should survive model calls and, for long-running work, process or context loss.
A transcript is useful evidence but often a poor canonical state representation.
System anatomy
- Task position
- What has completed and what remains.
- Observations
- Validated results from tools and the environment.
- Budgets
- Remaining time, steps, spend, and action limits.
- Disposition
- Running, blocked, held, escalated, completed, or failed.
Important distinctions
- Conversation history
- History records exchanges; working state is a structured, current operating record.
- Durable memory
- Working state belongs to a run; durable memory can outlive it and requires separate governance.
Implementation signals
- Use typed, versioned state transitions
- Checkpoint before irreversible or long-running actions
- Separate observed facts from model hypotheses
Failure modes
- The model reconstructs critical state from a truncated transcript
- Two agents update shared state without concurrency control
Sources and further study
- Anthropic — Effective harnesses for long-running agents
Patterns for incremental progress and durable handoffs across context windows and extended execution.
Use in this library: First-party case study. This first-party account documents one organization, product, or implementation context and should not be generalized without local evidence.
engineering · engineering · Published 2025-11-26 - Anthropic — Scaling Managed Agents: Decoupling the brain from the hands
An architecture separating durable sessions and environment state from changing models and harnesses.
Use in this library: First-party case study. This first-party account documents one organization, product, or implementation context and should not be generalized without local evidence.
engineering · engineering · Published 2026-04-08 - OpenAI — An open-source spec for Codex orchestration: Symphony
An orchestration specification that connects project work, isolated agent execution, and reviewable delivery state.
Use in this library: First-party case study. This first-party account documents one organization, product, or implementation context and should not be generalized without local evidence.
engineering · engineering · Published 2026-04-27