All tasks

Hermes contribution

Proposed Secure ENV catalog update to 0.8.7

This open PR proposes changing only the Secure ENV catalog entry in Hermes: pin the published 0.8.7 SHA, revise the description and add install-visible warnings. Linux scope, the Hermes ≥0.22.2 floor and community tier remain. The plugin version aligns password, saved TOTP and card destination selection with native Browser Vault; it does not move plugin code into core or automatically update installations. A maintainer decision under rule 11 is still required: approved-key ingress reads and writes the selected .env, and setup directly reads owner IDs from it; no exemption is claimed. The plugin runs in-process, depends on internal APIs and retains a CAUTION scanner warning. One-use links authorize their holder; CVC is stored in the encrypted Vault, and sites may authorize or submit operations in response to input. Allowlisted operation consumers run unsandboxed with gateway privileges. Filling does not confirm sign-in or payment. The PR is not merged, and inclusion in a Hermes release is unverified.

This Hermes contribution comes from the source PR. See the source PR for status and discussion; release inclusion is checked separately.

GitHub data verified: 2026-11-08

PR status

Open — proposal

PR inclusion in a release is unverified

Open GitHub

Topics for this object

• Improve Hermes
• Automation
• Plugins
• Hermes contributions

Help with this task

• AI consultation and workflow review

  Diagnosis of the workflow, bottlenecks, risks, and ROI: what is worth automating, where an agent helps, and where manual control is safer.

  Discuss the task

• AI agent setup for a specific business task

  An agent for a concrete process: data sources, rules, quality checks, safe autonomy boundaries, and ongoing support.

  Discuss the task

• Telegram bots / backend / API / automation

  The implementation layer after diagnosis: bots, APIs, integrations, monitoring, internal panels, and self-hosted Node.js tools.

  Discuss the task