hermes-admin/hermes-agent
1
0
Fork 0
Code Issues Pull Requests Actions 4 Packages Projects Releases Wiki Activity

chore(plugin-catalog): bento disclosure at merge

Browse Source 
Applies the reviewed Disclosure line from the catalog sweep review (catalog PR #133524).
This commit is contained in:
Teknium
2026-10-05 23:34:15 -07:00
parent 07405b8330
commit 651350b2de
1 changed files with 1 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
plugin-catalog/bento.yaml
View File

@@ -1,14 +1,7 @@
name: bento
repo: https://github.com/shagghiesuperstar/hermes-plugin-bento
sha: "f490ed02c0e377acc9112bf57192bacedbbcd9b1"
description: >-
Bento (bentonow.com) email marketing: subscribers, tags, fields, events incl. $purchase, stats,
draft/scheduled broadcasts and transactional email, with dry-run + human-approval gates on every
send. Native Python plugin, no dependencies. Disclosure: sends real email and can trigger Bento
Flows; calls only app.bentonow.com with your keys from .env; no telemetry; no self-update;
the approval gate fails closed under cron/gateway only while approvals.cron_mode is not
"approve" (with cron_mode=approve, or YOLO, no human is asked; the token and hard guards
still apply). environment=staging does not block sends; only environment=disabled does.
description: "Bento (bentonow.com) email marketing: subscribers, tags, fields, events incl. $purchase, stats, draft/scheduled broadcasts and transactional email, with dry-run + human-approval gates on every send. Native Python plugin, no dependencies. Disclosure — sends real email (bento_email_send, bento_broadcast_schedule), and events, purchases and consent changes can trigger Bento Flows that email people; calls only app.bentonow.com (an operator base_url override is limited to https *.bentonow.com or loopback) with the BENTO_* keys from the profile .env; no telemetry, no self-update; T2/T3 calls go to the Hermes approval prompt, which asks no human under YOLO, approvals.mode off, or cron/single-query/unattended mode set to approve. T3 sends then still need a dry-run confirm token and hard guards, but T2 writes (events, purchases, consent, bulk upserts) need no token unless safety.tier2 is token_only; T1 writes (tags, tag/field definitions, drafts, upserts up to bulk_threshold) are never gated and still run under environment=disabled; environment=staging does not block sends, only environment=disabled blocks T2/T3."
maintainer: shagghiesuperstar
tier: community
category: tools