Back Home

GitHub Repo

Hermes Agent Community Reports Smart Approval Gap: AppleScript May Automatically Close Unsaved Documents

A report on October 19 says smart approval may automatically allow AppleScript commands that close unsaved presentations, risking user data loss. Another contributor reproduced the approval gap. The community proposed a patch branch requiring human confirmation, but no official fix has been released.

Gerald L. Nino · Public domain · Image source
zh-Hant

On October 19, the Hermes Agent community reported that while the desktop agent was creating a presentation on macOS, it used osascript to control a running instance of PowerPoint and executed “close without saving” on a pre-existing, unsaved user presentation. The reporter said the command was automatically allowed under the default smart approval mode, resulting in lost work. This is the user’s account; maintainers have not published a full incident investigation. Incident report

The issue involves two layers: the agent used active presentation to refer to the shared application’s current document, without reliably locking onto the file it had opened; and the approval system did not block the destructive close operation. Another contributor said they reproduced the gap by submitting the command text to the real approval flow on the main branch. They did not execute the document-closing command, so this supports the finding that approval failed, but does not independently verify data loss. Reproduction details

The official documentation says smart delegates risk assessment to an auxiliary language model. Low-risk commands may pass automatically, while uncertain cases are sent for human confirmation. In manual mode, commands identified as dangerous require user approval. This means that switching to manual mode still depends on the preceding detection step recognizing a command; it does not guarantee a confirmation prompt for every application operation. Security documentation

The community patch branch aims to recognize AppleScript/JXA patterns that close documents without saving and route those operations directly to a human for confirmation, bypassing model judgment. The contributor reported that new case tests passed, but the branch is still awaiting maintainer action; this does not establish that the official release has been fixed. The recommendation to track files created by the agent and limit deletion scope is also not included. Patch status

For desktop agent developers, the case highlights the need for a separate permission boundary around shared GUI state. Engineering reviews should check document identity, unsaved status, and whether destructive operations require direct human confirmation. Next, watch for the patch to be merged, a release to ship, and coverage to expand to other office software. The official documentation also cautions that command-matching rules are not a complete operating-system capability sandbox. Security boundary guidance

Sources

  1. Hermes config set writes unseeded runtime-read keys — PR #114226
  2. Documented runtime-read configuration keys refused — Issue #114107
  3. Hermes Agent Configuration
  4. Hermes Agent v0.21.3 — v2026.9.14
  5. Smart approval auto-approved osascript commands that closed the user's unsaved PowerPoint deck and deleted its export
  6. Security | Hermes Agent