Bug Description
After running the OpenClaw migration during Hermes agent setup, the OPENROUTER_API_KEY is not copied/set in the Hermes .env file.
When using the agent in Telegram:
⚠️ Error code: 401 - {'error': {'message': 'No cookie auth credentials found', 'code': 401}}
Actual root cause (from logs): missing OpenRouter API key.
The Telegram error message is misleading and doesn't point to the real problem.
Impact: Agent fails to work in Telegram after migration until key is manually added.
Suggested Fix:
-
After migration completes, manually add the key to Hermes .env:
OPENROUTER_API_KEY=sk-or-v1-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
Restart the Hermes agent / container.
Ideal long-term fix (for devs):
Update the migration script to explicitly copy or prompt for OPENROUTER_API_KEY and write it to the target .env file (or handle via config migration logic).
Manually adding the key resolves it immediately.
Steps to Reproduce
Have existing openclaw setup with Openrouter provider
Use the migrate from openclaw option
Try to. Message the bot on Tg
Expected Behavior
Should have a working bot on telegram
Actual Behavior
Got the error mentioned ions above
Affected Component
Gateway (Telegram/Discord/Slack/WhatsApp)
Messaging Platform (if gateway-related)
Telegram
Operating System
Popos lts
Python Version
3.14
Hermes Version
0.2.0
Relevant Logs / Traceback
Root Cause Analysis (optional)
No response
Proposed Fix (optional)
No response
Are you willing to submit a PR for this?
Bug Description
After running the OpenClaw migration during Hermes agent setup, the OPENROUTER_API_KEY is not copied/set in the Hermes
.envfile.When using the agent in Telegram:
⚠️ Error code: 401 - {'error': {'message': 'No cookie auth credentials found', 'code': 401}}
Actual root cause (from logs): missing OpenRouter API key.
The Telegram error message is misleading and doesn't point to the real problem.
Impact: Agent fails to work in Telegram after migration until key is manually added.
Suggested Fix:
After migration completes, manually add the key to Hermes
.env:Restart the Hermes agent / container.
Ideal long-term fix (for devs):
Update the migration script to explicitly copy or prompt for OPENROUTER_API_KEY and write it to the target
.envfile (or handle via config migration logic).Manually adding the key resolves it immediately.
Steps to Reproduce
Have existing openclaw setup with Openrouter provider
Use the migrate from openclaw option
Try to. Message the bot on Tg
Expected Behavior
Should have a working bot on telegram
Actual Behavior
Got the error mentioned ions above
Affected Component
Gateway (Telegram/Discord/Slack/WhatsApp)
Messaging Platform (if gateway-related)
Telegram
Operating System
Popos lts
Python Version
3.14
Hermes Version
0.2.0
Relevant Logs / Traceback
Root Cause Analysis (optional)
No response
Proposed Fix (optional)
No response
Are you willing to submit a PR for this?