Connect one messaging channel with an explicit allowlist

Before you start

• Working local chat, a test bot/account and private credential storage
• Explicit sender allowlist; do not enable all-user access for the trial

Prepare and connect

1. Choose one platform from the current messaging guide. Complete its credential setup locally, without including tokens in screenshots or reports.
2. Set an explicit allowlist for the test sender. Inspect the effective gateway configuration before sending messages.
3. Use hermes gateway status to distinguish a registered service from a running process. Start it with the documented command for your OS.
4. Send a unique harmless phrase in a private chat and match the received message, session and reply in gateway evidence.

Acceptance and negative test

Confirm the authorized sender receives the intended reply in the same channel. A second test account outside the allowlist must not gain tool access. Test group routing only after private routing passes. Keep sender IDs private when sharing diagnostics.

Failure handling

If no reply arrives, locate the break: platform receipt, gateway session, model response or outbound delivery. Check for duplicate gateway processes before retrying; multiple pollers can make symptoms intermittent. Stop the test gateway and revoke only the test credential when dismantling the trial.

Evidence and limits

Official documentation checked

• Original BotClaw acceptance procedure based on linked official documentation. Product commands were not executed; check your installed version.

Sources

• https://hermes-agent.nousresearch.com/docs/user-guide/messaging/