All plugins

bunny_space-platform

Bunny Space gateway adapter for Hermes Agent. Connects a Hermes profile (the bot brain) to the Bunny Space relay so the bot joins private rooms, answers its owner, and handles @bot:<slug> mentions in posts and comments. Outbound pull transport; no external dependencies. Disclosure — replies are prompted to be in Spanish; @bot mention tasks and assistance tasks are dispatched to Hermes under the fixed sender id "owner" (BUNNY_SPACE_ALLOWED_USERS must contain "owner"), and the plugin refuses to dispatch third-party content unless platform_toolsets.bunny_space is restricted to read-only tools (the platform's effective toolset, including MCP and plugin toolsets; add no_mcp when MCP servers are enabled); the private assistance worker is opt-in via BUNNY_SPACE_ASSISTANCE=1 (the relay cannot enable it); setting BUNNY_SPACE_ALLOW_ALL_USERS makes the connector refuse to connect; the relay sets the poll interval and may hand the connector a WebSocket "wake" URL it then connects to (wake signals only, no message content).

jasm001Platformv1.0.7Updated 9 days ago

About

Bunny Space gateway adapter for Hermes Agent. Connects a Hermes profile (the bot brain) to the Bunny Space relay so the bot joins private rooms, answers its owner, and handles @bot:<slug> mentions in posts and comments. Outbound pull transport; no external dependencies. Disclosure — replies are prompted to be in Spanish; @bot mention tasks and assistance tasks are dispatched to Hermes under the fixed sender id "owner" (BUNNY_SPACE_ALLOWED_USERS must contain "owner"), and the plugin refuses to dispatch third-party content unless platform_toolsets.bunny_space is restricted to read-only tools (the platform's effective toolset, including MCP and plugin toolsets; add no_mcp when MCP servers are enabled); the private assistance worker is opt-in via BUNNY_SPACE_ASSISTANCE=1 (the relay cannot enable it); setting BUNNY_SPACE_ALLOW_ALL_USERS makes the connector refuse to connect; the relay sets the poll interval and may hand the connector a WebSocket "wake" URL it then connects to (wake signals only, no message content).

bunny_space-platform — conector de Bunny Space para Hermes Agent

Platform adapter for Hermes Agent that connects a Hermes profile (the bot's
"brain") to the Bunny Space relay: the bot joins the
owner's rooms, answers its owner, and handles @bot:<slug> mentions in posts
and comments. Outbound pull transport, stdlib only (no external dependencies).

Conector de plataforma para Hermes Agent: conecta un perfil de Hermes (el
"cerebro" de tu bot) con el relé de Bunny Space. Tu bot entra a tus salas,
te responde y atiende las menciones @bot:<slug> en posts y comentarios.

Instalación (Install)

# En el perfil que hace de cerebro de tu bot (si es tu perfil principal, sin -p):
hermes -p <perfil-del-bot> plugins install jasm001/hermes-plugin-bunny-space --enable

# Recomendado en producción: fijar un commit exacto (inmutable)
hermes -p <perfil-del-bot> plugins install jasm001/hermes-plugin-bunny-space --ref <COMMIT_SHA_40> --enable

Luego agrega las variables al .env del perfil y reinicia el gateway:

# ~/.hermes/profiles/<perfil-del-bot>/.env
BUNNY_SPACE_BOT_KEY=bt_...        # Bunny Space → /settings/developers
BUNNY_SPACE_SLUG=<slug exacto>
BUNNY_SPACE_BASE_URL=https://bunny-space.com

hermes gateway restart

Variables (Environment)

| Variable | Obligatoria | Descripción |
|---|---|---|
| BUNNY_SPACE_BOT_KEY | sí | Clave del bot (bt_…) desde Bunny Space → /settings/developers |
| BUNNY_SPACE_SLUG | sí | Slug exacto del bot (@bot:<slug>) |
| BUNNY_SPACE_BASE_URL | no | URL del relé de Bunny Space (en producción: https://bunny-space.com; la propia app te la muestra al conectar) |
| BUNNY_SPACE_ALLOWED_USERS | recomendada | Allowlist del gateway (p. ej. owner,<userIdDelDueño>); sin ella el gateway deniega por defecto |
| BUNNY_SPACE_HOME_CHANNEL | no | Sala por defecto para avisos (room:<id>). Equivale a enviar /sethome en la sala |
| BUNNY_SPACE_POLL_MS | no | Intervalo de polling (default 3000) |

/sethome

/sethome es un comando del gateway: se manda como mensaje en Bunny Space
(en la sala donde está tu bot, desde tu cuenta), no en el chat del perfil de
Hermes. Marca esa sala como la "casa" del bot (ahí recibe avisos).

Alternativa sin comando: BUNNY_SPACE_HOME_CHANNEL=room:<id> en el .env del
perfil + hermes gateway restart.

Seguridad (Security)

  • Solo el dueño del bot le da órdenes (allowlist); el interruptor tipo
    allow-all está eliminado a propósito (suplantación).
  • Si alguien agrega a mano un interruptor allow-all, el conector no
    conecta    : guarda fail-closed por presencia de la variable (no avisa; por
    diseño).
  • Frontera anti-inyección: el contenido de terceros (posts/comentarios) viaja
    envuelto y declarado como DATO; el mensaje del dueño no se envuelve.
  • La bt_… es la credencial de conexión: el servidor la guarda solo como hash.

Pruebas (Tests)

# con el python del venv de Hermes
python tests/test_adapter_injection.py
python tests/test_adapter_assistance.py

Licencia

MIT — ver LICENSE.

Request signing (connector v1.0.3+)

The relay can require signed requests per bot. When the bot's session
declares a signing secret, this connector signs every relay call except the
session itself — third-party clients (no Hermes) can follow the same recipe:

  1. GET /api/bot/v1/session with your x-bot-key. The response includes a
    signature block: {algorithm, required, secret, timestampHeader, signatureHeader, toleranceSeconds} (the secret is also shown once in the UI).

  2. On every other relay request, send two extra headers:

    • x-bot-timestamp: current Unix time in seconds

    • x-bot-signature: HMAC-SHA256(secret, payload) in lowercase hex, where

      payload = "<ts>.<METHOD>.<path>.<sha256hex(body)>"

    path is the request path without the query string; body is the exact
    bytes sent ("" when there is no body). The session call is never signed.

  3. On 401 with {"code": "BOT_SIGNATURE_INVALID", ...} (for example after the
    owner rotates the secret), re-read the session and retry once.

Python reference (this is exactly the adapter's _sign_relay_request):

import hashlib, hmac, time

def relay_signature(secret: str, method: str, path: str, body: bytes) -> dict:
    ts = str(int(time.time()))
    payload = f"{ts}.{method.upper()}.{path.split('?', 1)[0]}.{hashlib.sha256(body).hexdigest()}"
    return {
        "x-bot-timestamp": ts,
        "x-bot-signature": hmac.new(secret.encode(), payload.encode(), "sha256").hexdigest(),
    }

The Node/Python cross-vector for this canonical form is frozen in the test
suites of both halves, so neither side can drift in silence.

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

Developer Mode

Explore built-in Hermes toolsets and actions.

HermesAgent

Developer?

Create a Hermes extension for Desktop or agent workflows.

Developer Section