debugging-hermes-tui-commands

Diagnose Hermes TUI slash command failures across Python registry, gateway, and Ink frontend.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps debug Hermes TUI slash commands when they disappear from autocomplete, behave differently between CLI and TUI, or fail to update the interface after a config change.

Core Features & Use Cases

  • Cross-layer diagnosis: Traces command issues across the Python registry, gateway bridge, and Ink frontend.
  • Autocomplete and dispatch fixes: Finds why a command is missing, misrouted, or only partially wired up.
  • Live UI consistency: Verifies that command actions update both persisted config and in-session UI state.
  • Use case: A slash command works in the CLI but not in the TUI, so this Skill helps identify whether the backend entry, gateway handler, or frontend local handler is out of sync.

Quick Start

Use this skill to trace a Hermes slash command from the Python registry through the gateway to the Ink frontend and identify the layer causing the failure.

Frequently Asked Questions about debugging-hermes-tui-commands

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

FAQPage Schema
Why do my Hermes TUI slash commands disappear from autocomplete?

Missing autocomplete entries occur when the Python COMMAND_REGISTRY is out of sync with the tui_gateway bridge. Diagnosing the command registration across these backend layers identifies the missing entry causing the autocomplete failure.

How do I fix slash commands that work in the CLI but fail in the TUI?

Fixing slash commands that work in the CLI but fail in the TUI requires tracing command dispatch from the Python registry through the JSON-RPC gateway to the Ink TypeScript handlers to locate the disconnected layer.

How does the JSON-RPC gateway connect Python backends to TypeScript TUIs?

The JSON-RPC gateway acts as a bridge routing slash command dispatches between the Python COMMAND_REGISTRY and the Ink TypeScript frontend, ensuring backend entries and frontend state updates remain synchronized.

Why does my Hermes TUI interface not update after a config change?

The TUI interface fails to update after a config change when the Ink TypeScript local handler does not reflect persisted config updates in the in-session UI state. Verifying this handler isolates the live UI inconsistency.

Can I trace a broken slash command across multiple layers in a TypeScript and Python stack?

You can trace broken slash commands across a TypeScript and Python stack by checking consistency between the Python registry, the JSON-RPC bridge, and the Ink handlers to find misrouted or partially wired commands.