Menu
Fix token conflicts when Hermes and OpenClaw both try to use the same Discord/Telegram bot tokens
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Diagnose and fix Hermes messaging gateway connectivity issues (Telegram/Discord down, stale locks, PM2 problems)
Backup Hermes agent to GitHub and restore on a new VPS. Covers what to include/exclude, GitHub token requirements, and restore steps. Includes automated scripts.
GitHub auth setup: HTTPS tokens, SSH keys, gh CLI login.
Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.
Fetch YouTube video transcripts and transform them into structured content (chapters, summaries, threads, blog posts). Use when the user shares a YouTube URL or video link, asks to summarize a video, requests a transcript, or wants to extract and reformat content from any YouTube video.
Manage Linear issues, projects, and teams via the GraphQL API. Create, update, search, and organize issues. Uses API key auth (no OAuth needed). All operations via curl — no dependencies.
| name | hermes-openclaw-token-conflict |
| description | Fix token conflicts when Hermes and OpenClaw both try to use the same Discord/Telegram bot tokens |
| triggers | ["openclaw gateway telegram conflict","openclaw gateway discord conflict","telegram polling conflict hermes openclaw"] |
When both Hermes gateway and OpenClaw gateway run on the same machine with the same bot tokens, they fight over the connections.
Telegram polling conflict (1/3), will retry in 10s. Error: Conflict: terminated by other getUpdates requestopenclaw-gateway and hermes gateway run processes both visible in ps auxOpenClaw gateway (Node.js app at ~/.openclaw/) and Hermes gateway (Python) both poll the same Telegram bot and connect to the same Discord bot. Only ONE can hold the connection.
# Check for both processes
ps aux | grep -E "openclaw-gateway|hermes.*gateway" | grep -v grep
# Check OpenClaw channel config
cat ~/.openclaw/openclaw.json | python3 -c "import json,sys; d=json.load(sys.stdin); print('Telegram:', d.get('channels',{}).get('telegram',{}).get('enabled')); print('Discord:', d.get('channels',{}).get('discord',{}).get('enabled'))"
Edit ~/.openclaw/openclaw.json:
"channels": {
"telegram": { "enabled": false },
"discord": { "enabled": false }
}
OpenClaw runs via systemd user service — killing the process won't stop it from auto-restarting:
systemctl --user stop openclaw-gateway.service
Verify it's stopped:
ps aux | grep openclaw-gateway | grep -v grep # Should be empty
rm -f ~/.hermes/gateway.pid
rm -f ~/.local/state/hermes/gateway-locks/*.lock
hermes gateway run --replace
The OpenClaw systemd service (openclaw-gateway.service) auto-restarts the process if killed manually. You must either:
After restart, check connections are established:
ss -tnp | grep <hermes_pid>
# Should show ESTAB connections to:
# Discord: 162.159.x.x:443
# Telegram: 149.154.x.x:443