Connecter Hermes Agent à une messagerie

Cette page fait partie du guide pratique francophone consacré à Hermes Agent. Elle répond à l'intention de recherche : choisir une plateforme de messagerie.

Le contenu s'appuie sur la documentation officielle Hermes Agent associée à cette page. L'objectif n'est pas de remplacer la documentation de Nous Research, mais de fournir une lecture claire en français, structurée pour aller vite, avec un maillage logique vers les pages complémentaires du même site.

À retenir

Sujet principal : hermes agent messagerie.
Type de page : hub.
Cluster : messagerie.
Source canonique : documentation officielle Hermes Agent.
Aucun lien vers l'autre domaine n'est utilisé dans cette page.

Comment utiliser cette section

Cette section regroupe les pages du cluster messagerie. Commencez par cette page si vous voulez comprendre le sujet dans son ensemble, puis ouvrez les guides détaillés selon votre contexte.

Chaque page interne contient des liens vers les prérequis, les pages voisines et les suites logiques. Le but est de créer un parcours utile, pas une liste brute de pages SEO.

Base officielle

Chat with Hermes from Telegram, Discord, Slack, WhatsApp, Signal, SMS, Email, Home Assistant, Mattermost, Matrix, DingTalk, Feishu/Lark, WeCom, Weixin, BlueBubbles (iMessage), QQ, Yuanbao, Microsoft Teams, LINE, ntfy, or your browser. The gateway is a single background process that connects to all your configured platforms, handles sessions, runs cron jobs, and delivers voice messages.

For the full voice feature set — including CLI microphone mode, spoken replies in messaging, and Discord voice-channel conversations — see Voice Mode and Use Voice Mode with Hermes.

Bots need both a model provider and tool providers (TTS, web). A Nous Portal subscription bundles all of them.

Platform Comparison

Platform — Voice — Images — Files — Threads — Reactions — Typing — Streaming
Telegram — ✅ — ✅ — ✅ — ✅ — — — ✅ — ✅
Discord — ✅ — ✅ — ✅ — ✅ — ✅ — ✅ — ✅
Slack — ✅ — ✅ — ✅ — ✅ — ✅ — ✅ — ✅
Google Chat — — — ✅ — ✅ — ✅ — — — ✅ — —
WhatsApp — — — ✅ — ✅ — — — — — ✅ — ✅
Signal — — — ✅ — ✅ — — — — — ✅ — ✅
SMS — — — — — — — — — — — — — —
Email — — — ✅ — ✅ — ✅ — — — — — —
Home Assistant — — — — — — — — — — — — — —
Mattermost — ✅ — ✅ — ✅ — ✅ — — — ✅ — ✅
Matrix — ✅ — ✅ — ✅ — ✅ — ✅ — ✅ — ✅
DingTalk — — — ✅ — ✅ — — — ✅ — — — ✅
Feishu/Lark — ✅ — ✅ — ✅ — ✅ — ✅ — ✅ — ✅
WeCom — ✅ — ✅ — ✅ — — — — — — — —
WeCom Callback — — — — — — — — — — — — — —
Weixin — ✅ — ✅ — ✅ — — — — — ✅ — ✅
BlueBubbles — — — ✅ — ✅ — — — ✅ — ✅ — —
QQ — ✅ — ✅ — ✅ — — — — — ✅ — —
Yuanbao — ✅ — ✅ — ✅ — — — — — ✅ — ✅
Microsoft Teams — — — ✅ — — — ✅ — — — ✅ — —
LINE — — — ✅ — ✅ — — — — — ✅ — —
ntfy — — — — — — — — — — — — — —
Raft — — — — — — — — — — — — — —
IRC — — — — — — — — — — — — — —

Voice = TTS audio replies and/or voice message transcription. Images = send/receive images. Files = send/receive file attachments. Threads = threaded conversations. Reactions = emoji reactions on messages. Typing = typing indicator while processing. Streaming = progressive message updates via editing.

Architecture

            tg[Telegram]
            dc[Discord]
            wa[WhatsApp]
            sl[Slack]
            gc[Google Chat]
            sig[Signal]
            sms[SMS]
            em[Email]
            ha[Home Assistant]
            mm[Mattermost]
            mx[Matrix]
            dt[DingTalk]
    fs[Feishu/Lark]
    wc[WeCom]
    wcb[WeCom Callback]
    wx[Weixin]
    bb[BlueBubbles]
    qq[QQ]
    yb[Yuanbao]
    ms[Microsoft Teams]
    wh[Webhooks]


    tg --> store
    dc --> store
    wa --> store
    sl --> store
    gc --> store
    sig --> store
    sms --> store
    em --> store
    ha --> store
    mm --> store
    mx --> store
    dt --> store
    fs --> store
    wc --> store
    wcb --> store
    wx --> store
    bb --> store
    qq --> store
    yb --> store
    ms --> store
    api --> store
    wh --> store
    store --> agent
    cron --> store

Each platform adapter receives messages, routes them through a per-chat session store, and dispatches them to the AIAgent for processing. The gateway also runs the cron scheduler, ticking every 60 seconds to execute any due jobs.

Intentional Silence Tokens

For group chats, hooks, and automation flows, Hermes supports explicit silence tokens. If the agent's final response is exactly one supported token, the gateway suppresses outbound delivery and sends nothing to the chat.

Supported tokens:

[SILENT]
SILENT
NO_REPLY
NO REPLY

Whitespace and case are normalized, but the whole final response must be the token. A sentence like "Use [SILENT] when nothing changed" is delivered normally.

Silence is a delivery decision only. Hermes keeps the assistant silence turn in the session transcript, so the conversation still alternates normally:

user: side-channel chatter
assistant: [SILENT]   # stored, not delivered
user: next message

Failed turns still surface as errors; Hermes does not hide failures just because the text resembles a silence token.

Quick Setup

The easiest way to configure messaging platforms is the interactive wizard:

hermes gateway setup        # Interactive setup for all messaging platforms

This walks you through configuring each platform with arrow-key selection, shows which platforms are already configured, and offers to start/restart the gateway when done.

Gateway Commands

hermes gateway              # Run in foreground
hermes gateway setup        # Configure messaging platforms interactively
hermes gateway install      # Install as a user service (Linux) / launchd service (macOS)
sudo hermes gateway install --system   # Linux only: install a boot-time system service
hermes gateway start        # Start the default service
hermes gateway stop         # Stop the default service
hermes gateway status       # Check default service status
hermes gateway status --system         # Linux only: inspect the system service explicitly

Chat Commands (Inside Messaging)

Command — Description
/new or /reset — Start a fresh conversation
/model [provider:model] — Show or change the model (supports provider:model syntax)
/personality [name] — Set a personality
/retry — Retry the last message
/undo — Remove the last exchange
/status — Show session info
/whoami — Show your slash command access on this scope (admin / user / unrestricted)
/stop — Stop the running agent
/approve — Approve a pending dangerous command
/deny — Reject a pending dangerous command
/sethome — Set this chat as the home channel
/compress — Manually compress conversation context
/title [name] — Set or show the session title
/resume [name] — Resume a previously named session
/usage — Show token usage for this session
/insights [days] — Show usage insights and analytics
/reasoning [level\ — show\ — hide] — Change reasoning effort or toggle reasoning display
/voice [on\ — off\ — tts\ — join\ — leave\ — status] — Control messaging voice replies and Discord voice-channel behavior
/rollback [number] — List or restore filesystem checkpoints
/background <prompt> — Run a prompt in a separate background session
/reload-mcp — Reload MCP servers from config
/update — Update Hermes Agent to the latest version
/help — Show available commands
/<skill-name> — Invoke any installed skill

Session Management

Session Persistence

Sessions persist across messages until they reset. The agent remembers your conversation context.

Reset Policies

Sessions reset based on configurable policies:

Policy — Default — Description
Daily — 4:00 AM — Reset at a specific hour each day
Idle — 1440 min — Reset after N minutes of inactivity
Both — (combined) — Whichever triggers first

A live background process (started with terminal(background=true)) normally

protects its session from resetting so output isn't lost. To stop a forgotten

process — say a preview server — from pinning a session open forever, a

background process older than bg_process_max_age_hours (default 24) no

longer blocks reset. The process is not killed, only ignored by the reset

guard. Set it to 0 to disable the cutoff (any live process blocks reset, the

old behavior), or raise it if you run legitimate multi-day jobs whose liveness

should keep the conversation open.

Configure per-platform overrides in ~/.hermes/gateway.json:

{
  "reset_by_platform": {
    "telegram": { "mode": "idle", "idle_minutes": 240 },
    "discord": { "mode": "idle", "idle_minutes": 60 }
  }
}

Security

By default, the gateway denies all users who are not in an allowlist or paired via DM. This is the safe default for a bot with terminal access.

TELEGRAM_ALLOWED_USERS=123456789,987654321
DISCORD_ALLOWED_USERS=123456789012345678
SIGNAL_ALLOWED_USERS=+155****4567,+155****6543
SMS_ALLOWED_USERS=+155****4567,+155****6543
EMAIL_ALLOWED_USERS=trusted@example.com,colleague@work.com
MATTERMOST_ALLOWED_USERS=3uo8dkh1p7g1mfk49ear5fzs5c
MATRIX_ALLOWED_USERS=@alice:matrix.org
DINGTALK_ALLOWED_USERS=user-id-1
FEISHU_ALLOWED_USERS=ou_xxxxxxxx,ou_yyyyyyyy
WECOM_ALLOWED_USERS=user-id-1,user-id-2
WECOM_CALLBACK_ALLOWED_USERS=user-id-1,user-id-2
TEAMS_ALLOWED_USERS=aad-object-id-1,aad-object-id-2

GATEWAY_ALLOWED_USERS=123456789,987654321

GATEWAY_ALLOW_ALL_USERS=true

DM Pairing (Alternative to Allowlists)

Instead of manually configuring user IDs, unknown users receive a one-time pairing code when they DM the bot. Email is the exception: unknown email senders are ignored unless email pairing is explicitly enabled.

Connecter Hermes Agent à une messagerie