All plugins

finix

Age-encrypted profile backups with verified cloud readback and offline extraction; automatic recovery is unavailable. Disclosure — Finix copies your whole Hermes profile, including .env, auth.json, config.yaml, session databases and memories, encrypts it with age to a recipient key you generate, and uploads it to your Google Drive (Hermes-managed finix:google OAuth, drive.file scope) or an rclone remote you configure; it runs scheduled backups in the background once you enable them, needs the separately installed age and age-keygen, and anyone holding the recovery key can read every secret in those backups, so keep the key off the backup host.

web3blindAutomationv0.1.0Updated 3 days ago

About

Age-encrypted profile backups with verified cloud readback and offline extraction; automatic recovery is unavailable. Disclosure — Finix copies your whole Hermes profile, including .env, auth.json, config.yaml, session databases and memories, encrypts it with age to a recipient key you generate, and uploads it to your Google Drive (Hermes-managed finix:google OAuth, drive.file scope) or an rclone remote you configure; it runs scheduled backups in the background once you enable them, needs the separately installed age and age-keygen, and anyone holding the recovery key can read every secret in those backups, so keep the key off the backup host.

Finix — encrypted Hermes profile backups

Finix creates age-encrypted backups of Hermes profiles, uploads them to the
selected storage and verifies the complete cloud object by downloading it back.
It provides a standalone CLI, native Hermes commands, a Desktop setup pane and
an offline recovery-key generator.

Experimental beta with limited recovery. Automatic named-profile import,
activation and physical-default replacement are disabled. They return
PUBLIC_RECOVERY_CONTRACT_UNAVAILABLE before reading a recovery key. Standalone
offline extraction into an empty directory remains available. This is not an
automatic restoration product.

Current capabilities

  • Encrypted profile backups, including supported conversation-history data,
    configuration and notes. Private staging and archive validation protect the
    capture/extraction boundaries; keep independent backups.
  • Local storage, configured rclone storage and Google Drive through the declared
    Hermes-managed finix:google OAuth provider with drive.file.
  • Full downloaded-object verification, durable pending-upload records and
    explicit storage selection. Unknown outcomes do not silently become success.
  • Desktop key registration, cloud connection, first-backup verification and
    explicitly enabled scheduling. Existing public recipients cannot be replaced.
  • English by default and Russian as an explicit language option.
  • Catalog previews and inert offline extraction. Existing recovery journals,
    preimages and provenance are retained but never replayed automatically.

The Google Workspace skill transport and private managed-gateway signing are
removed. Finix does not borrow another tool's login, copy legacy grants or
silently fall back to another account. Old Workspace settings are rejected with
an actionable setup error while existing data is preserved.

Verified on the released public SDK

The current runtime was tested at source commit
684a1e6
with released Hermes v0.23.1 on an isolated Linux VM and synthetic profile:

  • Actual native CLI and Linux Desktop each created and uploaded a new backup
    using its own Hermes-managed Google grant, without the Workspace skill.
  • Both objects were independently downloaded, SHA256 matched, and age decryption
    plus full manifest validation recovered 19,846 files per archive, complete
    with zero omissions.
  • The downloaded Desktop archive passed an externally orchestrated cold data
    recovery into an absent physical default-home on the same disposable VM.
    SDK startup/PM regeneration succeeded; all three synthetic conversation exports
    and a note matched, and restored cron stayed paused. Original directories were
    returned after the experiment.

That last experiment used external VM exclusivity and an existing SDK/runtime
outside the restored home. It is not automatic Default Apply, a public held
writer lease, fresh-machine recovery or a production-profile test.

Source CI passed all
four Linux/Windows focused and released-SDK jobs. The Linux SDK lane passed 62
history, Drive-protocol and backup/progress fixture tests. These are bounded
checks, not a claim that the entire historical suite passes. Current native
Windows GUI/cloud acceptance has not been rerun; older Windows evidence used a
retired implementation and is not acceptance of this runtime.

See publication status and
test boundaries for the exact scope and remaining limitations.

Install and use

Hermes plugin SDK 0.23.1 or later, Python 3.11–3.14, the declared Python
dependencies and separately installed age/age-keygen are required. Optional
rclone is not bundled. Google uses Hermes' public credentialed-provider API;
client provisioning and consent must be configured for the owning profile.
No plugin runtime downloads executable helpers.

In Desktop, generate and save the private recovery file locally outside the
backup host. Register only its public recipient. Connect and explicitly apply
storage, then run the first backup and wait for readback verification. Enable a
schedule only after a successful check. A lost private key cannot be recovered;
never send it in chat. No private recovery key is required to create a backup.

The native CLI provides hermes finix status, hermes finix check and
hermes finix schedule 24h for an already configured profile. The schedule
command is an explicit opt-in, not a required part of testing a backup.

Recovery and security boundaries

Finix does not patch Hermes core modules, take private gateway writer locks,
use private activation tickets/pipes, or pin runtime compatibility to hashes of
Hermes core source files. Unsupported automated recovery remains gated off until
a suitable public contract exists and the replacement receives new review.
Stopping a gateway and observing its status are not proof that every writer is
quiescent. Stock import is a manual fallback, not exact transactional replacement.

Backup content can include credentials and executable configuration. Archives are
encrypted before cloud upload; extraction is not permission to activate imported
grants, plugins or autoruns. Use private staging, safe local key storage and
independent backups. Do not delete old journals or replay historical Apply to
repair an interrupted operation. Historical recovery documents are retained as
records, not instructions to enable those retired paths.

Linux and native Windows/NTFS use distinct filesystem protections. WSL is not
native Windows evidence. Broad historical test discovery is not the supported
release gate: see the exact CI files and declared fixture requirements in
TEST-SDK.md. Missing fixtures and removed private APIs are not
passing tests and are not suppressed as success.

Finix first-party code is MIT licensed, copyright 2026 Denis Skripnik.
Third-party notices are preserved in THIRD-PARTY-NOTICES.md.

README from the reviewed commit b4241cd; it updates when the author re-pins.

More by web3blind

5 plugins by web3blind in the catalog.

web3blindvk-platformVK Messenger gateway with community Long Poll, media attachments, allowlists, and project-lane routing.Communityplatform2web3blindsecure-env-ingressOne-use HTTPS forms for missing .env secrets and native encrypted Browser Vault login/TOTP/card storage; retained exact-parent login, saved TOTP, protected payment fields, transient codes and approved secret operations outside chat and model input. Browser destinations follow native Vault classification, origins and stamped-control selection, with bounded frame/Shadow extensions and asynchronous owner/profile/lease/cancellation checks. No CSS/history locks, sibling-tab fallback, core override or login backend registration. Disclosure — in-process internal Hermes Vault, browser, gateway, redaction and config APIs can break on host updates; setup instructions require approval for privileged host/TLS changes; TLS listens on all interfaces by default; the gateway hook observes messages for sender binding. Native encrypted card storage includes CVC. Site input callbacks can authorize or auto-submit; unknown outcomes need external verification before retry. SHA-256-pinned administrator-allowlisted operation consumers run unsandboxed with gateway privileges, none enabled by default; cancellation cannot stop an already-running consumer. Links authorize their holder, not submitter identity. Explicit .env ingress adds approved missing keys; setup bootstrap reads selected-profile .env owner IDs.Communitytools1web3blindchrome-tab-watchdogConservative Chrome tab cleanup with in-process observation and browser-call leases. Disclosure — runs a background thread inside Hermes that proxies your local Chrome DevTools port (127.0.0.1:9222 → 127.0.0.1:9223, loopback only, you must point browser.cdp_url at it), injects a focus/activity listener into every Chrome page, rewrites browser_exec session names to a per-profile namespace, and a cron script you schedule auto-closes idle, duplicate and blank tabs (including tabs with unsaved text).Communityautomationweb3blinddeferred-questionsDurable non-blocking questions with exact answer binding and gateway continuation. Disclosure — pre_gateway_dispatch sees gateway messages, accepts answers only from the stored recipient and route, and may consume recognized stale/completed inputs; with enable_tool on, the model can send questions to any chat the gateway already authorizes, and continue_agent resumes the target chat with the answer; questions and answers are stored unencrypted in $HERMES_HOME/deferred-questions/questions.sqlite3; profile-local Unix-socket notices wake event-driven workers; pre_llm_call/on_session_end observe current input, turn IDs and terminal status to correlate technical completion for payload retirement, not business success or delivery; automatic header-only repair preserves originals in quarantine, and text-free receipts retain caller-supplied idempotency keys and request hashes; private gateway and adapter APIs can break after a Hermes update.Communityautomation

Developer Mode

Explore built-in Hermes toolsets and actions.

HermesAgent

Developer?

Create a Hermes extension for Desktop or agent workflows.

Developer Section