Originally created by: sosidudku1
agent.approvalRequired already exists in config.json and turns off the approval gate, but it is not discoverable: users hit repeated approval prompts and assume there is no way around it.
"please add always yes"
Screenshot showed the approval prompt: tool: os.shell.run, reason: no shell guard rule matched; approval required.
Surface the setting where the prompt appears:
Worth stating clearly in the UI: hardline guards in src/tools/os/shell-command-guard/rules-hardline.ts still block the genuinely destructive commands (rm -rf /, rm -rf ~, mkfs, dd to a raw block device, fork bombs) regardless of the approval setting. A blanket "yes" should say this, so users understand what they are and are not turning off.
Session-scoped approval is probably a safer default than a permanent global toggle.
Ticket changed by: sosidudku1