debugging-hermes-tui-commands

Debug broken Hermes TUI slash commands across frontend, gateway, and Python layers.

Updated May 26, 2026
One-click install
npx skills add https://github.com/ruiyangruiyi/hermes-agent --skill debugging-hermes-tui-commands-ruiyangruiyi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-hermes-tui-commands
Source: https://github.com/ruiyangruiyi/hermes-agent/tree/main/skills/software-development/debugging-hermes-tui-commands
Command: npx skills add https://github.com/ruiyangruiyi/hermes-agent --skill debugging-hermes-tui-commands-ruiyangruiyi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hermes TUI slash commands can fail or appear inconsistent when the Python command registry, the TUI gateway JSON-RPC dispatch, and the Ink/TypeScript frontend are out of sync.

Core Features & Use Cases

  • Cross-layer command debugging: Trace issues across Python registry, gateway dispatch, and frontend autocomplete/handlers.
  • Autocomplete and dispatch consistency checks: Ensure canonical command definitions propagate so suggestions and execution match.
  • Live UI state validation: Confirm that config persistence also updates the correct nanostore/UI state paths for immediate TUI behavior.
  • Use case: A command works in the CLI but not in the TUI, or a command persists configuration but never updates the visible UI.

Quick Start

Use the debugging-hermes-tui-commands skill to locate which layer is missing or out of sync when a slash command is not autocompleting or not executing in the Hermes TUI.

Frequently Asked Questions about debugging-hermes-tui-commands

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my slash command work in the CLI but not in the Hermes TUI?▼

Slash command behavior differs between CLI and TUI when the Python command registry, gateway JSON-RPC dispatch, and Ink/TypeScript frontend are out of sync. You need to validate command presence in TypeScript handlers and check gateway dispatch routes.

How do I fix missing slash commands in Hermes TUI autocomplete?▼

To fix missing autocomplete suggestions, ensure canonical CommandDef alignment including aliases and subcommands propagates correctly across the Python registry and TypeScript frontend layers.

What causes a Hermes TUI slash command to persist configuration but not update the visible UI?▼

Configuration persists without UI updates when config changes fail to trigger immediate nanostore-driven UI state updates in the frontend, requiring validation of the correct nanostore paths.

How do I trace slash command execution failures across Python registry and gateway dispatch?▼

Trace execution failures by validating command presence in TypeScript handlers, checking gateway JSON-RPC dispatch routes, and ensuring canonical CommandDef alignment across all layers.

What should I check when a slash command is ignored by gateway dispatch in Hermes TUI?▼

When gateway dispatch ignores a slash command, verify that the canonical CommandDef including aliases and subcommands is properly registered and that gateway JSON-RPC dispatch routes are correctly configured.

Do I need to update the Python command registry when adding new slash commands to Hermes TUI?▼

Yes, the Python command registry must be updated and kept in sync with the TypeScript frontend and gateway JSON-RPC dispatch to ensure slash commands appear in autocomplete and execute consistently.