hermes-messaging-setup

النجوم١١

التفرعات٢

آخر تحديث١٠ أبريل ٢٠٢٦ في ٠٠:١٣

Configure WhatsApp and Telegram messaging platforms on Hermes Agent

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

المصدر

wu-xiaochen

wu-xiaochen/ontology-clawra

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

SKILL.md

readonly

name	hermes-messaging-setup
description	Configure WhatsApp and Telegram messaging platforms on Hermes Agent

Hermes Agent Messaging Platforms Setup

Key Discovery

Hermes Agent uses TWO separate config systems:

~/.hermes/config.yaml — general agent config
~/.hermes/.env — messaging platforms, API keys, credentials

Messaging platforms (WhatsApp, Telegram, Discord, etc.) MUST be configured via .env, NOT config.yaml. Use hermes config set command, never edit .env directly.

WhatsApp Setup

Config in ~/.hermes/.env:

WHATSAPP_MODE=bot
WHATSAPP_ALLOWED_USERS=13920378337   # International format, no + sign

Important: WhatsApp Personal Account Limitation

WhatsApp personal account connected via QR code becomes the bot
Cannot message yourself to test — WhatsApp doesn't relay self-messages to the bot
Need another person to message your number, OR use WhatsApp Business as a separate bot account
Channel directory built: 0 target(s) = no active sessions yet

If bridge keeps disconnecting:

This is a known Baileys bridge issue with WhatsApp personal accounts
Try hermes whatsapp to re-pair if session was invalidated

Telegram Setup

Step 1: Create bot via @BotFather

Message @BotFather on Telegram
Send /newbot, follow prompts
Copy the bot token (format: 123456789:ABCdef...)

Step 2: Get your Telegram User ID

Search @userinfobot on Telegram
Send any message — it replies with your numeric User ID

Step 3: Configure Hermes (in ~/.hermes/.env)

hermes config set TELEGRAM_BOT_TOKEN "123456789:ABCdef..."
hermes config set TELEGRAM_ALLOWED_USERS "123456789"  # Your Telegram user ID, NOT phone number

Step 4: Restart gateway

hermes gateway restart

Step 5: Verify

Check logs: tail -20 ~/.hermes/logs/gateway.log Should see: ✓ telegram connected

macOS + SOCKS Proxy (China Firewall)

If Telegram fails with httpx.ConnectError or NetworkError:

Check if you have a SOCKS proxy running:

networksetup -getsocksfirewallproxy Wi-Fi

If proxy exists (e.g., ClashX at 127.0.0.1:7897), set env vars:

launchctl setenv HTTP_PROXY socks5://127.0.0.1:7897
launchctl setenv HTTPS_PROXY socks5://127.0.0.1:7897

Install socksio for httpx:

uv pip install httpx[socks] --python ~/.hermes/hermes-agent/venv/bin/python

Restart gateway:

hermes gateway restart

Note: Common proxy port is 7890 (Clash) or 7897 (ClashX), not 1080.

Common Issues

approvals.mode: manual

All messages require manual approval — bot won't respond
Fix: hermes config set approvals.mode auto

Channel directory built: 0 target(s)

No active messaging sessions yet
For WhatsApp: need someone to send a message to your number
For Telegram: need to message the bot from your account

Gateway not picking up new config

Always run hermes gateway restart after config changes

Verification Commands

hermes gateway status        # Check gateway and platform status
tail -20 ~/.hermes/logs/gateway.log  # View recent logs

المزيد من هذا المستودع

نفس المستودع

ontology-clawra

wu-xiaochen/ontology-clawra

🧠 ontology-clawra v5.1 - Local Ontology Reasoning & Learning Engine **USE THIS SKILL WHENEVER** you need structured reasoning, knowledge graph management, logical inference, or learning from interactions. This is your go-to tool for: - Building and querying ontology knowledge graphs (concepts, entities, relationships) - Performing confidence-based reasoning with evidence tracking - Recording insights and patterns from completed tasks - Local memory search and knowledge retrieval **Key Use Cases:** - Before making complex decisions: "Let me use ontology-clawra to reason about this" - After completing tasks: "Record this learning to ontology-clawra" - Building domain expertise: "Create concepts for [domain] in ontology-clawra" - Analyzing patterns: "Query ontology-clawra for similar past cases" **Core Capabilities:** ✅ Local ontology storage in `~/.openclaw/skills/ontology-clawra/memory/` ✅ Confidence calculation (CONFIRMED/ASSUMED/SPECULATIVE) ✅ Learning from user confirmations ✅ Local memory search (no ne

2026-07-2811

hermes-agent

wu-xiaochen/ontology-clawra

Complete guide to using and extending Hermes Agent — CLI usage, setup, configuration, spawning additional agents, gateway platforms, skills, voice, tools, profiles, and a concise contributor reference. Load this skill when helping users configure Hermes, troubleshoot issues, spawn agent instances, or make code contributions.

2026-04-1011

git-https-push-with-token

wu-xiaochen/ontology-clawra

Git push to HTTPS remote using token authentication — avoids SSH setup, works in CI/automated environments.

2026-04-1011

github-history-cleanup

wu-xiaochen/ontology-clawra

从 GitHub 历史中彻底清除敏感文件的完整流程 — 使用 git filter-repo + force push，适用于清理意外提交的个人文件、工作文件等

2026-04-1011

github-clawhub-privacy-cleanup

wu-xiaochen/ontology-clawra

清理 GitHub 历史和 ClawHub 中意外泄露的个人/工作文件

2026-04-1011

hermes-telegram-setup

wu-xiaochen/ontology-clawra

Configure Telegram bot messaging channel for Hermes Agent, especially useful when behind Chinese firewall with SOCKS proxy

2026-04-1011

name	hermes-messaging-setup
description	Configure WhatsApp and Telegram messaging platforms on Hermes Agent

Hermes Agent Messaging Platforms Setup

Key Discovery

Hermes Agent uses TWO separate config systems:

~/.hermes/config.yaml — general agent config
~/.hermes/.env — messaging platforms, API keys, credentials

Messaging platforms (WhatsApp, Telegram, Discord, etc.) MUST be configured via .env, NOT config.yaml. Use hermes config set command, never edit .env directly.

WhatsApp Setup

Config in ~/.hermes/.env:

WHATSAPP_MODE=bot
WHATSAPP_ALLOWED_USERS=13920378337   # International format, no + sign

Important: WhatsApp Personal Account Limitation

WhatsApp personal account connected via QR code becomes the bot
Cannot message yourself to test — WhatsApp doesn't relay self-messages to the bot
Need another person to message your number, OR use WhatsApp Business as a separate bot account
Channel directory built: 0 target(s) = no active sessions yet

If bridge keeps disconnecting:

This is a known Baileys bridge issue with WhatsApp personal accounts
Try hermes whatsapp to re-pair if session was invalidated

Telegram Setup

Step 1: Create bot via @BotFather

Message @BotFather on Telegram
Send /newbot, follow prompts
Copy the bot token (format: 123456789:ABCdef...)

Step 2: Get your Telegram User ID

Search @userinfobot on Telegram
Send any message — it replies with your numeric User ID

Step 3: Configure Hermes (in ~/.hermes/.env)

hermes config set TELEGRAM_BOT_TOKEN "123456789:ABCdef..."
hermes config set TELEGRAM_ALLOWED_USERS "123456789"  # Your Telegram user ID, NOT phone number

Step 4: Restart gateway

hermes gateway restart

Step 5: Verify

Check logs: tail -20 ~/.hermes/logs/gateway.log Should see: ✓ telegram connected

macOS + SOCKS Proxy (China Firewall)

If Telegram fails with httpx.ConnectError or NetworkError:

Check if you have a SOCKS proxy running:

networksetup -getsocksfirewallproxy Wi-Fi

If proxy exists (e.g., ClashX at 127.0.0.1:7897), set env vars:

launchctl setenv HTTP_PROXY socks5://127.0.0.1:7897
launchctl setenv HTTPS_PROXY socks5://127.0.0.1:7897

Install socksio for httpx:

uv pip install httpx[socks] --python ~/.hermes/hermes-agent/venv/bin/python

Restart gateway:

hermes gateway restart

Note: Common proxy port is 7890 (Clash) or 7897 (ClashX), not 1080.

Common Issues

approvals.mode: manual

All messages require manual approval — bot won't respond
Fix: hermes config set approvals.mode auto

Channel directory built: 0 target(s)

No active messaging sessions yet
For WhatsApp: need someone to send a message to your number
For Telegram: need to message the bot from your account

Gateway not picking up new config

Always run hermes gateway restart after config changes

Verification Commands

hermes gateway status        # Check gateway and platform status
tail -20 ~/.hermes/logs/gateway.log  # View recent logs