- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 1
- Soundness
- 1
Read review
Paper summary
This paper argues that cognitive continuity should be developed as an intrinsic capability of language-model agents rather than primarily implemented through external orchestration. The authors categorize existing approaches into external orchestration, continuous autoregressive processing, and persistent recurrent state. They further propose a shared recurrent latent workspace that continuously updates the agent's internal state, together with memory and output mechanisms. The paper is presented as a position paper and does not report new empirical results.
Critical strengths
Reasonable motivation. Enabling agents to maintain and update internal states across interaction boundaries is a relevant research direction. The discussion of different approaches to cognitive continuity provides some useful conceptual organization.
Critical weaknesses
-
Limited novelty. The proposed architecture largely combines established ideas, including recurrent hidden-state computation, shared latent representations, persistent memory, and output gating. Although the paper emphasizes extending recurrence beyond individual inference episodes, it does not clearly establish a fundamentally new mechanism or sufficiently distinctive research insight compared with existing approaches.
-
Insufficient technical substantiation. The paper provides neither an implemented and trained system nor theoretical evidence supporting its central architectural hypothesis. Important technical decisions, including the backbone architecture, training objectives, and learning procedure, remain unspecified. Consequently, the proposed architecture remains largely conceptual, and its feasibility and potential advantages are not demonstrated.
-
Unconvincing justification for intrinsic continuity. External orchestration and recurrent internal computation operate at different levels of abstraction and can coexist within the same agent system. While the authors acknowledge this possibility, the paper does not convincingly explain why moving continuity into the model should provide meaningful advantages over strong existing orchestration-based approaches. The claimed benefits in coordination, generalization, and long-term adaptation remain speculative.
Questions for authors
-
What is the key technical or conceptual contribution that distinguishes the proposed persistent recurrent workspace from existing recurrent architectures and memory-augmented agent systems?
-
What concrete evidence or argument supports the hypothesis that intrinsic recurrent continuity offers advantages over learned external orchestration, particularly under comparable computational budgets and model capabilities?
5 comments
I still have concerns about the overall research contribution. Being a position paper does not mean that one can simply combine existing engineering components, introduce a new taxonomy, and outline hypothetical future experiments. A convincing position paper should articulate a clear scientific question and provide meaningful conceptual insights or arguments to support its position. The additional details in the rebuttal remain largely speculative, focusing on architectural descriptions and proposed experimental plans rather than concrete technical developments or evidence. Overall, this work reads more like an engineering assembly accompanied by an ambitious architectural blueprint than a well-formulated scientific research contribution. I therefore maintain my original rating.
Thank you for taking the time to read our revised manuscript. While we acknowledge that the paper does not provide experimental validation, we would like to emphasize that it does articulate a clear scientific question: whether the locus of cognitive continuity affects an agent's capabilities. Section 4 develops several conceptual arguments supporting our position. If the reviewer could clarify why these arguments remain unconvincing or insufficient as a scientific contribution, we would greatly appreciate the feedback.
Thank you for the review. We respond to each point below.
W1/Q1 — What is novel beyond combining existing modules? The paper makes two contributions.
The first is defining and organizing a new class of systems. Always-on agents have quickly become a central direction of the field: xAI's Grok Bot, Meta's Muse, and OpenAI's Dots all launched this year, and OpenClaw became GitHub's most-starred software project. To our knowledge, no prior work defines the property these systems share or classifies them by where their continuity lives. The paper does both (Secs. 2–3, Table 5).
The second is the architecture. We do not claim to invent recurrence, shared latent states, memory, or a speak/silent gate. What is new is the role the shared state plays: a fixed-size state, rewritten at every step, that remains the agent's current cognitive situation after it acts, including during silence. Existing work uses recurrent state differently. Recurrent sequence models (LSTMs, state-space models) and recurrent reasoners (TRM, HRM-Text) carry state through one sequence or problem, and it ends there. Memory-augmented agents keep memories that survive between calls, but stored memory does not keep thinking. In our proposal, the gate that decides when to speak reads the live state, the decoder keeps reading it while speaking, and retrieved memories are written back into it, so one memory can bring up another.
W2 — Technical substantiation and position-paper scope. We agree that feasibility and superiority are not yet demonstrated. The paper presents them as hypotheses and states the results that would refute each one (Introduction, "Three claims"). ICLR has accepted position papers on this basis (e.g., Ngo et al., ICLR 2024, https://openreview.net/forum?id=fh8EYKFKns). Still, we have added the details you asked for. The new Appendix B.5 gives a reference implementation: a pretrained encoder–decoder in which the encoder updates the state at every step and the decoder reads only from it; a speaking gate trained to match reference timings as distributions; training through time over long trajectories; and a curriculum that adds one capability at a time. The new Appendix C.7 specifies how to test it against strong baselines.
W3/Q2 — Why move the carrier inside the model, and how is coexistence handled? We agree that orchestration and recurrence can coexist; our own system uses a runtime clock, an autoregressive decoder, and an external memory. The taxonomy does not classify which modules a system contains, but which state carries the agent's ongoing situation from one step to the next. In OpenClaw, that is the session state kept by the runtime, so it is external orchestration. In our architecture, the runtime only advances the clock and the situation lives in Z, so it is persistent recurrent state; the decoder and memory store are components. The revised Appendix G.4 turns this into a simple two-question test and works through borderline cases.
We do not claim that external systems cannot achieve continuity. Our hypothesis is that learning it inside the model works better in three situations: when what must persist is hard to write into a record (half-finished deliberation, how long a silence has lasted); when capabilities interact in orders not seen in training (further thought makes a memory relevant, retrieving it changes the conclusion, and a correction becomes warranted); and when perception, thinking, and action overlap. A learned controller improves routing, but each call still starts from the record, and what is written there is sampled text, so its long-term effects are learned only from sparse reward rather than from gradients through time. If the controller is instead given a latent state rich enough to hold the agent's situation, continuity has moved into a learned state, which is our proposal (Appendix G.4). A fixed-size state also keeps the cost of each step constant, however long the agent runs (Sec. 4.2).
The new Appendix C.7 tests this directly. A learned orchestrator, a bounded autoregressive model, shared Z, and partitioned Z share the backbone, training data, memory, and compute, and are tested on chains of reasoning, memory, perception, and timing in orders never seen in training. Baselines are also given 2× and 4× post-answer compute, so an advantage that disappears there is efficiency, not capability. If the orchestrator or the autoregressive model matches shared Z, the corresponding hypothesis weakens.