Agent State Management — Stateless API, Stateful Workflow

Key Takeaways

• Claude's API is inherently stateless — each invocation is context-free; stateful multi-turn behaviour requires an explicit external state store (Redis, DynamoDB, or a vector DB) that your orchestration layer reads and writes on every turn.
• In agentic workflows, state has three distinct scopes — turn-level (current message), session-level (conversation thread), and workflow-level (long-running task progress) — and each scope demands a different persistence strategy and TTL policy.
• For regulated workloads (BFSI, legal, healthcare), state stores must satisfy the same data-residency, encryption-at-rest, and audit-trail requirements as your primary transactional systems — state management is not a backend afterthought, it is a compliance surface.
• Memory anchor: treat agent state exactly like an OAuth token relay — the orchestrator is the token store, every Claude API call presents a short-lived reconstructed context, and the backing store is the source of truth; the API itself holds nothing between calls.