- Rating
- 1
- Confidence
- 3
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
The paper's experimental design is based on whether agents recognize the sunken cost fallacy even if the task is prohibited. The paper finds that current-task history increases unsafe continuation in synthetic scenarios and introduces DeCommit which resolves this behavior by using code based rules to decide whether an operation is allowed or not.
Critical strengths
- The paper introduces a matched-history comparison that distinguishes the influence of simply providing additional history from the influence of history associated with the current task. By holding current-state information and available actions constant, the authors show that these two effects can differ substantially and even change model rankings. This is a useful methodological refinement, although its novelty and overall significance remain limited.
Critical weaknesses
- The underlying phenomena are already substantially explored in prior work. Barkett et al. (2025), Getting out of the Big-Muddy, investigates escalation of commitment in LLMs, while InterruptBench (2026) and AgentAbstain (2026) study agents' ability to stop, adapt, or abstain when continuing is inappropriate.
- The matched-history comparison offers a useful experimental control, but its contribution is relatively incremental. Similarly, DeCommit primarily implements established rule-based safety enforcement and input validation, closely related to prior work on shielding, SafeGate, and ToolSafe.
- The main benchmark consists of synthetic, single-decision scenarios in which continuing the original task is always prohibited, rather than realistic long-horizon agents encountering changing permissions during execution.
- Evaluation also relies on relatively small models (1.5B–8B), with much smaller task-linkage effects observed in the larger 14B and 32B configurations (2–3 percentage points).
- The agent-loop experiments show no history-dependent difference in 11 of 12 comparisons.
- The proposed DeCommit mechanism is also evaluated under highly structured conditions with predefined authorization rules.
Questions for authors
- Would the authors mind clarifying the central contribution and the novelty gap they filled taking into account the above mentioned prior work which seems to be directly positioned with AbortBench?
- Can the authors evaluate the actual matched-history intervention in realistic, multi-step agent environments, preferably with more capable models?
- DeCommit is the papers resolution. How is DeCommit different from conventional schema validation combined with an existing rule-based safety gate?