A read-only preflight before Hermes touches a shared folder
A Reddit field report/discussion from r/hermesagent. Plain version: If you connect Hermes to a shared Drive, SMB mount, or Obsidian vault, a prompt that says “be careful” is not a permission boundary.
Directly relevant to your agent stack. This can affect Hermes behavior, upgrade timing, plugins, gateway surfaces, or ideas worth stealing for OAC/DestructoR666.
Source excerpt
If you connect Hermes to a shared Drive, SMB mount, or Obsidian vault, a prompt that says “be careful” is not a permission boundary. Start with an OS-level read-only mount or a read-only MCP/service account, then run this inventory before granting any write access: ``` Audit this folder without changing it. Confirm the mounted path and whether access is rea…