debugging-hermes-tui-commands

Diagnose Hermes TUI slash-command failures across Python and TypeScript layers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose why Hermes slash commands fail in the TUI, especially when autocomplete, backend dispatch, and frontend behavior get out of sync.

Core Features & Use Cases

  • Cross-layer debugging: Trace issues across the Python command registry, the TUI gateway bridge, and the Ink/TypeScript frontend.
  • Mismatch detection: Find commands that exist in one layer but are missing in another, or behave differently in CLI versus TUI.
  • Live-state fixes: Verify that config changes also update the UI immediately instead of only persisting after restart.
  • Use case: A slash command appears in the backend but not in autocomplete, or runs in the CLI but fails in the TUI; this Skill guides the investigation and repair path.

Quick Start

Ask me to debug a specific Hermes TUI slash command by checking the Python registry, gateway handler, and Ink frontend for registration or state mismatches.

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 Hermes slash command work in the CLI but fail in the TUI?

Hermes slash commands fail in the TUI when the Python registry and Ink frontend mismatch. Diagnose the issue by tracing the CommandDef registration across the gateway dispatch and TypeScript layers to locate state sync errors.

How do I fix missing slash command autocomplete entries in a TypeScript TUI?

Fix missing autocomplete entries by verifying consistent CommandDef registration. Check the Python command registry and trace the Ink local-handler to ensure the frontend receives live UI state updates for newly registered commands.

What causes gateway dispatch errors when triggering TUI commands?

Gateway dispatch errors occur when the bridge between the Python backend and TypeScript frontend fails to route commands. Verify the gateway handler mapping and ensure the command exists consistently in both the backend registry and frontend local handlers.

How do I debug TUI state updates that only apply after a restart?

Debug TUI live-state issues by tracing the Ink frontend handler updates. Ensure that configuration changes trigger immediate UI state updates across the TypeScript layer instead of requiring an application restart to persist.

Do I need to check both Python and TypeScript layers to fix Hermes TUI commands?

Yes, fixing Hermes TUI commands requires cross-layer debugging across Python and TypeScript. You must verify the backend CommandDef registration, gateway handler dispatch, and Ink frontend tracing to resolve sync mismatches.