hermes - 💡(How to fix) Fix Feature Request: Custom Slash Commands / Shortcuts for Messaging Platforms [1 participants]

Problem

Currently, Hermes Agent slash commands like /profile, /model, /skill, etc. are hardcoded in the CLI. Users on messaging platforms (Telegram, Feishu, Discord, etc.) cannot create custom shortcuts to trigger predefined actions or workflows.

For example, a user might want to:

• Type /switch-profile work to switch the active profile
• Type /shortcut daily-standup to trigger a complex multi-step automation
• Type /alias deploy-prod to run a predefined delegation/cron workflow

Proposed Solution

Introduce a custom slash commands / aliases system that:

1. Command registry — Users can register custom commands via config or CLI:

   hermes shortcut create daily-standup --prompt \"Summarize my tasks for today and send to #general\"
   hermes shortcut create switch-work --command \"profile use work\"
   hermes shortcut list
   hermes shortcut delete daily-standup

2. In-chat trigger — Registered shortcuts are callable from any messaging platform:

   /daily-standup
   /switch-work

3. Shortcut metadata — Each shortcut supports:

   • name: trigger name
   • description: shown in /help and platform command menus
   • prompt or command: either a prompt to run or a CLI command to execute
   • skills: optional skills to preload
   • platforms: optional platform-specific allowlist

4. Platform integration — Shortcuts appear in:

   • /help and /commands listings
   • Telegram bot command menu
   • Slack command shortcuts
   • Feishu bot commands

Alternatives Considered

• Skills: Skills are powerful but require a skill file and /skill <name> invocation. Shortcuts are lighter-weight and directly executable as a single command.
• Cron jobs: Too heavyweight for on-demand use cases.
• Profile aliases: Only work from server terminal, not from messaging chats.

Implementation Suggestion

Extend the existing CommandDef registry in hermes_cli/commands.py to support user-defined commands:

1. Add a ~/.hermes/shortcuts.yaml file for user shortcuts
2. Add hermes shortcut CLI subcommand group
3. Merge user shortcuts into the command registry before building autocomplete/menus
4. Shortcuts with --command run via hermes run <command> internally

This would be a non-breaking additive feature.

Would love to hear if this aligns with the project direction. Happy to contribute if pointers are given.