Good Papers

FlowState: Execution State as Memory for Long-Horizon LLM Agents

FlowState treats execution state as reusable memory via typed nodes and incremental updates, boosting long-horizon agent success by up to 13.95 points while cutting token use over 40%.

Published Sep 28, 2026▲ 6 on Hugging Face

54%
OverallWorth a look
?
OverallWorth a lookVote to see the score
Readers
–

Only vote on papers you've read. Sign in to vote.

AI panel9/20reviewers recommend it
lenient 4/5
medium 4/10
strict 1/5
AI panel?Vote to see what the 20 AI reviewers said

Abstract

Long-horizon tasks require LLM agents to continually draw on information from earlier interactions. However, retaining the full history increases context costs, while compressing it risks losing details needed later, and the relevance of historical information often becomes apparent as the task progresses. To address these challenges, we propose FlowState, which treats execution state as memory that can be retained and revisited across requests, unifying current decision-making with the reuse of historical information. FlowState preserves semantically typed state nodes, their relations, and references to raw tool observations, separating persistent retention from on-demand access. Within a single execution loop, Incremental State Update (ISU) maintains the current state based on new inputs and feedback, while Progressive State Access (PSA) progressively reveals historical states and supporting evidence as needed during reasoning. Together, these mechanisms enable agents to reassess prior decisions in light of new information and guide subsequent actions. Compared with a full-context baseline using the same DeepSeek-V4-Flash model, FlowState improves the average success rate on MemoryArena and the average pass rate on τ³-Bench by 4.55 and 13.95 percentage points, respectively, while reducing total token consumption by 43.2% and 40.6%. These results demonstrate the performance and efficiency advantages of FlowState on long-horizon tasks.

Are you an author?

Good Papers badgeAuthor of this paper? Add this badge to your README or page
[![Good Papers](https://www.goodpapers.org/badge/W7214800521.svg)](https://www.goodpapers.org/paper/W7214800521)