Bug Description
Telegram passes /status to agent instead of a system call returning metrics
Steps to Reproduce
In Telegram, send /status
Expected Behavior
Expect system generated message with:
- Session ID, creation timestamp, last activity
- Token count
- Agent running state
- Connected platforms list
Actual Behavior
"/status" was passed to the agent and they gave me a summary of things we had been discussing/working on.
Affected Component
Gateway (Telegram/Discord/Slack/WhatsApp)
Messaging Platform (if gateway-related)
Telegram
Operating System
Ubuntu 24.04 Sever (Docker)
Python Version
3.13.5
Hermes Version
0.7.0
Relevant Logs / Traceback
Root Cause Analysis (optional)
The /status command handler exists in the code at /opt/hermes/gateway/run.py line 3109. It should return:
- Session ID, creation timestamp, last activity
- Token count
- Agent running state
- Connected platforms list
Proposed Fix (optional)
No response
Are you willing to submit a PR for this?
Bug Description
Telegram passes /status to agent instead of a system call returning metrics
Steps to Reproduce
In Telegram, send /status
Expected Behavior
Expect system generated message with:
Actual Behavior
"/status" was passed to the agent and they gave me a summary of things we had been discussing/working on.
Affected Component
Gateway (Telegram/Discord/Slack/WhatsApp)
Messaging Platform (if gateway-related)
Telegram
Operating System
Ubuntu 24.04 Sever (Docker)
Python Version
3.13.5
Hermes Version
0.7.0
Relevant Logs / Traceback
Root Cause Analysis (optional)
The /status command handler exists in the code at /opt/hermes/gateway/run.py line 3109. It should return:
Proposed Fix (optional)
No response
Are you willing to submit a PR for this?