Skip to content

[Bug]: Telegram passes /status to agent instead of a system call returning metrics #5046

@mechovation

Description

@mechovation

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?

  • I'd like to fix this myself and submit a PR

Metadata

Metadata

Assignees

No one assigned

    Labels

    sweeper:implemented-on-mainSweeper: behavior already present on current maintype/bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions