debugging-hermes-tui-commands

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you diagnose and resolve inconsistencies between the Hermes CLI/Python command registry, the TUI gateway JSON-RPC dispatch, and the Ink/TypeScript frontend so slash commands appear correctly and behave the same across surfaces.

Core Features & Use Cases

  • Cross-layer command verification: Identify whether a slash command is missing from autocomplete, present but unhandled, or incorrectly wired between Python, gateway, and frontend.
  • Targeted autocomplete and dispatch troubleshooting: Determine whether the failure is in COMMAND_REGISTRY, gateway dispatch routing, or Ink local handler/fallthrough behavior.
  • Live UI state debugging guidance: Address cases where config persists but the TUI does not update immediately, including pathways where rendering must be patched beyond simple state saves.
  • Practical fix recipes: Provides concrete steps for adding/updating CommandDef entries and wiring handlers in both Python and gateway.

Quick Start

Use debugging-hermes-tui-commands to trace why a specific Hermes slash command is not showing in TUI autocomplete or is not executing as expected, then apply the corresponding fix across the Python registry, gateway dispatch, and Ink frontend handlers.

Frequently Asked Questions about debugging-hermes-tui-commands

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

FAQPage Schema
Why is my Hermes TUI slash command missing from autocomplete but works in the CLI?

Hermes TUI slash command autocomplete failures occur when command registrations are mismatched across the Python command registry, TUI gateway dispatch, and Ink/TypeScript frontend handlers. You must verify the command exists in all three layers to resolve the inconsistency.

How do I debug slash command execution failures in a TypeScript TUI gateway?

Debugging slash command execution failures requires layer-by-layer verification of JSON-RPC dispatch routing and Ink local handler fallthrough behavior. You need to check whether the command is correctly wired between the gateway dispatch and the TypeScript frontend handlers.

What causes a TUI to not update immediately after config is persisted?

Live UI state fails to reflect persisted configuration when rendering pathways require patching beyond simple state saves. You must trace the UI state update mechanism to ensure the frontend re-renders after the configuration is saved.

How do I add a new slash command to the Python command registry and TUI frontend?

Adding a slash command requires updating the CommandDef entry in the Python registry and wiring corresponding handlers in both the gateway dispatch and Ink/TypeScript frontend. You must ensure rebuild and runtime testing across all layers.

Does Hermes TUI command behavior diverge from the CLI when registrations are mismatched?

Yes, TUI behavior diverges from CLI behavior when a command exists in one layer but not another. You must canonicalize the command registry and verify that gateway dispatch and frontend handlers are aligned to ensure consistent execution.