- Rating
- 1
- Confidence
- 3
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper introduces a context management method for coding agents called Perdura. Their motivation comes from three challenges for current coding agents: computational state reconstruction, execution evidence recovery, and unfinished-work tracking, and Perdura has four core features to tackle those challenges: it has a persistent namespace that can keep all the used variables alive, an execution ledger that can keep all execution results in memory, a work lifecycle that can wake the coding agent back up when something happens, and a control state that has a step loop for controlling everything. They compare Pedura with popular harnesses like Claude Code and Codex; though Perdura does not always perform the best, it reaches the level of Claude Code. They didn't provide detailed ablation studies to highlight each component's contribution.
Critical strengths
I would say the critical strength is the reduction of token consumption brought by the designed harness.
Critical weaknesses
There are a couple of noticeable weaknesses in this paper:
Lack of ablation studies. The paper's main claim is that it splits the execution state into a persistent namespace N, an execution ledger L, and a work lifecycle W. These contributions help the system reach performance comparable to Claude Code and achieve significantly lower token consumption. However, the authors did not provide any ablation studies to support this claim; only a case in Figure 3 shows single trajectories selected to show each mechanism working. They do not show how often each mechanism is used or how much it contributes to the score and cost. Without ablation studies, the cost reduction could equally come from Perdura’s prompt design, its tool descriptions, or simply a more aggressive truncation policy.
To me, this article reads more like a well-written engineering report than a research paper that tests a specific hypothesis. I acknowledge that solving these problems represents a good step forward for coding agents, but the motivation lacks foresight.
Questions for authors
N/A
Reply to Reviewer nniS
The hypothesis. Long-horizon agents need execution state kept by the runtime, not carried by the transcript. Two lessons from long-lived software motivate it. A log is not a database: long-running systems maintain state explicitly, recover from checkpoints and surface in-doubt transactions instead of replaying history. A for loop is not an operating system: holding resources, suspending until an event and recovering from failure become the runtime's job. Today's harnesses differ in tools, prompts and memory files, but all loop over a transcript. As agents move to long-lived work, the transcript must be compacted and loses what earlier calls did; values and live resources must survive steps and restarts; external effects must be settled, never blindly repeated; and "tell me when X happens" must hold for days without polling. Perdura tests the hypothesis: a general CodeAct harness (tasks need not involve programming) whose runtime keeps values (N), effects and their settlement (L) and unfinished work (W) as one linked state, of which the model sees a bounded projection (Π).
Three predictions, tested (GPT-5.6 Terra, 3 runs; tables in general response 2):
Over all trajectories, N is used in 99% of ToolMaze tasks and W in 92% of SentinelBench tasks.
The savings are not truncation or prompt design. Prediction 1 isolates truncation: with the state fixed, withdrawing only the bounding costs 34% more at equal score, so bounding saves cost without losing what the task needs. Each ablation keeps the rest of the prompt and tools identical, so a difference comes from the withdrawn component; its teaching is how the model uses it. Against the baselines the comparison is between harnesses as a whole: Perdura provides capabilities they lack, and its prompt lets the model use them.
What this suggests beyond our benchmarks.
Concurrent work points the same way: explicit execution state [2], task state outside the context [3], explicit belief states [4], short compacted contexts [5]; in industry, Pi Durable [6] does not replay interrupted effects and DeepSeek's Super-agent [7] wakes the agent when background jobs end. Perdura makes this state one structure grounded in the code action. We will open-source it for controlled studies of execution state (e.g., interpreter persistence [8]).
[1] Kwa et al. Measuring AI Ability to Complete Long Software Tasks. arXiv:2503.14499, 2025.
[2] Badhe et al. SKILL.state: Scalable Long-Horizon Agent Skills. arXiv:2608.26263.
[3] Ma et al. LongHorizon-Harness: Advancing Long-Horizon Agents for Real-World Tasks. arXiv:2608.01964.
[4] Luo et al. Beyond Memory: Harnessing Long-Horizon Agents with Explicit Belief States. arXiv:2610.01415.
[5] Belcak et al. You don't need long context. arXiv:2611.05306.
[6] Earendil. Pi Durable, released with Pi 1.0, 2026.
[7] DeepSeek. dsh-superagent-prototype, 2026.
[8] May et al. Evaluating Agents Across Runtime Contracts: When Mismatch Costs Efficiency or Quality. arXiv:2603.01209.