hermes - 💡(How to fix) Fix Bug: /sessions command is registered but has no handler — silent no-op in gateway and CLI

Summary

The /sessions command is registered in COMMAND_REGISTRY (hermes_cli/commands.py L113) but has no handler in either the gateway dispatcher (gateway/run.py) or the CLI dispatcher (cli.py). It results in a silent no-op — the user sends /sessions and gets zero response.

Details

1. Command is registered without cli_only=True

# hermes_cli/commands.py L112-113
# Configuration
CommandDef("sessions", "Browse and resume previous sessions", "Session"),

No cli_only=True → sessions is included in GATEWAY_KNOWN_COMMANDS → the gateway recognizes it as valid.

2. No handler in gateway dispatcher

The gateway command dispatch chain in gateway/run.py (starting ~L5892) has canonical == "resume" (L6003) but no canonical == "sessions" branch. Unrecognized registered commands hit the "agent is running" guard or fall through silently.

3. No handler in CLI dispatcher

cli.py process_command() (~L6748) also has no elif canonical == "sessions" branch.

4. Result: silent failure

Since sessions is in GATEWAY_KNOWN_COMMANDS:

• Gateway does not emit the "Unknown command" fallback
• Gateway does not forward it as plain text to the LLM
• No handler runs → zero response to the user

The CLI hermes sessions browse works fine — this is specifically about the /sessions slash command inside an active chat session.

Suggested fixes (pick one)

Option A: Mark as cli_only (minimal)

The interactive session picker (hermes sessions browse) needs keyboard navigation and is not feasible in a messaging gateway. Mark it cli_only=True so the gateway properly rejects it:

CommandDef("sessions", "Browse and resume previous sessions", "Session",
           cli_only=True),

Option B: Add a gateway handler (full experience)

Add _handle_sessions_command() to gateway that lists recent sessions (similar to /resume with no args, but showing all sessions, not just titled ones). Users could then /resume <name> to switch.

Environment

• Hermes Agent version: current main
• Platform: Telegram gateway (affects all gateway platforms)
• Reproduction: send /sessions in any gateway chat → no response