Coding agents increasingly rely on automated approvers to decide whether a proposed shell command may run. Existing approvers, from rule-based checkers to guardrail models and deployed permission clas
Caper pre-executes shell commands in isolated sandboxes to evaluate real-world effects before approval, reducing harmful outcomes compared to text-based approvers.
Coding agents increasingly rely on automated approvers to decide whether a proposed shell command may run. Existing approvers, from rule-based checkers to guardrail models and deployed permission classifiers, base their decisions on the text of the request and command. Yet a command's behavior depends on the code it invokes and the state of the workspace, and systems that observe file changes leave the assessment to the agent or a human after execution. We present Caper, a consequence-aware approval mechanism that pre-executes each command in a snapshotted sandbox, provides an independent approver with a bounded report of its observed effects, commits allowed commands, and rolls back…
Summary and abstract excerpt via Hugging Face Papers ↗ · arXiv.
"Shall We Approve?" Consequence-Aware Approval for Autonomous Coding Agents was first seen on Hugging Face · Daily papers on Nov 4, 2026. Since then it has appeared in 12 checks on 2 different days. Its best position was #14 of 30, reached on Nov 5, 03:28 UTC. It dropped off the list after Nov 5, 05:28 UTC.
Position on Hugging Face · Daily papers at every check (lower is better).
Best rank per day (UTC).
Platform metric as reported by Hugging Face.
Archived daily, weekly and monthly lists that include this entry.
Not at the moment. It was last on the list on Nov 5, 05:28 UTC, after 2 days of trending.
#14 on Hugging Face · Daily papers, on Nov 5, 03:28 UTC. Trendoday checks this list every 120 minutes.
It was first seen on Nov 4, 2026 and has been on the list on 2 days (12 checks) since.