Skip to content

[Feature]: Integrated Platform Command Reference #1054

@popstarsai

Description

@popstarsai

Problem or Use Case

Currently, as Hermes Agent scales across CLI and messaging platforms (Telegram, Slack, Discord), users need to cross-reference multiple files to find platform-specific command syntax. This improves onboarding for the first 750 new sign-ups.

Proposed Solution

Here is the complete, formatted text for your GitHub Issue. You can copy and paste this directly into the New Issue page on the Hermes Agent repository.
Issue Title: [Feature Request] Integrated Platform Command Reference (Quick Start Table)
Description
Currently, as Hermes Agent scales across CLI and messaging platforms (Telegram, Slack, Discord), users need to cross-reference multiple files or the codebase to find platform-specific command syntax. To improve developer onboarding and bridge the gap between "Claude Code" style CLI and "OpenClaw" style messaging, I propose adding a Quick Start Table to the main README.md.
Proposed Solution
A concise, scannable Markdown table that maps core agentic actions across all supported interfaces.
🚀 Hermes Agent: Cross-Platform Quick Start

Action CLI (Terminal) Telegram / Discord / Slack Description
Initialize hermes boot /start Wakes the agent and loads persistent memory.
New Task hermes run "task" !run "task" Executes a goal using available tools/subagents.
Check Status hermes status /status View current active sessions and machine state.
Manage Skills hermes skills /skills Lists or installs new agent-managed skills.
File Access hermes cat [path] !read [path] Reads a file from the dedicated machine access.
Reset Context hermes clear /forget Clears short-term buffer (retains long-term memory).
Stop Session Ctrl + C /stop Safely pauses the current agentic process.
Why is this relevant?
  • User Retention: The first 750 new sign-ups using the HERMESAGENT code will benefit from an immediate, clear roadmap of how to interact with the agent.
  • Consistency: It establishes a standard for developers when they extend the project with new "Agent-managed skills."
  • Clarity: It highlights the unique value of "picking up and transferring sessions wherever you go."
    Implementation Checklist
  • Finalize the mapping of CLI vs. Bot commands.
  • Insert the table into the Usage or Quick Start section of README.md.
  • (Optional) Update the install.sh output to link to this command reference.

Alternatives Considered

I considered leaving the documentation as is, but as the project grows with more "Agent-managed skills," a unified command reference is essential for cross-platform consistency.

Feature Type

New tool

Scope

None

Contribution

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    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