- Rating
- 3
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 3
Read review
Paper summary
The paper proposes PoS, an inference-time framework in which an LLM agent maintains an explicit belief about the world. The belief contains the current world state, plus what the agent still needs to learn or check, and what the agent still needs to do to achieve the given goal. At ecah step, PoS selects one of these unresolved information or required actions, and make an action to resolve it. After an action, LLM proposes belief updates, and a validator LLM (Sentinel in this paper) checks every belief update before it is accepted. When the agent stops making progress (e.g., repeating meaningless actions or looping), PoS detects it, diagnoses the type of stall, and gives targeted recovery instructions. Experiments on ALFWorld, LOCA-Bench, RCA-100, and ClinDiag with three backbones show that PoS outperforms all baselines in every setting.
Critical strengths
- S1. Addresses a practical failure of LLM agents. Looping between states or repeatedly observing without progress is a common failure mode of LLM agents. PoS offers a concrete, online remedy.
- S2. Clean method design. PoS separates verified from unverified belief updates, separates what to learn or check from what to do, and makes each action target an explicit subgoal, reducing aimless actions. Monitoring for unproductive actions and loops is also a sensible design choice.
- S3. Broad evaluation and supporting analysis. Evaluation covers 4 benchmarks with 3 LLM backbones. The Belief Trapping analysis (Sec. 4.2) supports both that the targeted problem is real and that the proposed method addresses it. It shows that trapping occurs frequently across benchmarks and backbones, and that the proposed factorized recovery outperforms a generic recovery prompt.
Critical weaknesses
-
W1. Missing belief-only ablation. Table 1 removes validation and recovery only one at a time, so the other component always remains. A belief-only variant, with neither validation nor trapping diagnosis, would help support the paper's claim that belief construction alone is insufficient.
-
W2. Multiple runs needed in evaluation. All results come from a single run as I understand. Please report results over multiple runs with standard deviation.
-
W3. Key definitions need clarification. Several components central to trapping detection are only loosely described:
- (a) Active-gap projection . App. B.2 only says relevant records are selected "through their existing relations." How exactly is it computed, and is it rule-based or LLM-based?
- (b) Matching of belief elements across steps. Belief elements are free-form text, so the same state can be phrased differently across steps (e.g., "Microwave 1: closed" vs. "Microwave 1 is shut"). How are elements matched when computing the Jaccard distance (Eq. 5b) and (Eq. 5a)?
Questions for authors
See weaknesses
3 comments
Thank you for the detailed response. The requested ablation and the repeated evaluations have been incorporated into the revision, and they address my concerns. I maintain my score at 3.
As a minor suggestion, showing statistics how often the baselines fall into belief trapping would make the paper more convincing.
Response to Reviewer kTHC
Dear Reviewer kTHC,
Thank you for reviewing our responses and the revised manuscript. We appreciate your confirmation that the additional ablation and repeated evaluations address your concerns.
We also appreciate your suggestion to report trapping incidence for the baselines, which would strengthen the comparison. Because trapping emerges during an agent’s interactions, measuring its incidence across methods requires a consistent way to identify it from their trajectories, including those of baselines without explicit beliefs. Given the lack of a widely accepted criterion for identifying belief trapping across different agent architectures, we plan to explore a common assessment protocol and extend this comparison to the baselines in future work.
Thank you again for your constructive feedback and careful evaluation.
Best regards, The authors of PoS
Response to Reviewer kTHC
We thank the reviewer for the comprehensive review and for recognizing the practical importance of belief trapping and the design of PoS. Below, we address the requested ablation, repeated evaluations, and implementation clarifications.
W1: Belief-only ablation without validation or recovery.
A1:
Belief-only ablation: We added the Belief-only variant with both consistency validation and trapping diagnosis/recovery removed, retaining belief construction, updates, and gap-guided interaction. We evaluated it over five runs across all four benchmarks and three backbones. Table R3 reports the complete results for PoS and all three ablation variants.
Why belief maintenance matters: Removing both consistency validation and trapping diagnosis/recovery further reduces the performance compared with removing either component alone, highlighting the importance of these two maintenance mechanisms. Full PoS exceeds Belief-only by 4.90–17.16 percentage points across all 12 settings. These comparisons further support the central point made in the Introduction: belief construction is only the starting point. And maintaining the belief by validating belief updates and diagnosing and recovering from trapping helps translate the belief representation into reliable task performance.
Table R3. Full PoS and three ablation variants. Entries report mean ± sample standard deviation (%) over five runs. “−” denotes removal from full PoS.
W2: Evaluation over multiple runs.
A2:
W3(a): Computation of the active-gap projection.
A3(a):
W3(b): Matching belief elements across steps.
A3(b):
We hope this clarification addresses your concern, and if you find our response helpful, we kindly request the reviewer to consider adjusting the rating.