debugging-hermes-tui-commands

Hermes slash commands fail across CLI and TUI when the Python command registry, gateway, or Ink frontend layers fall out of sync. The root cause is typically a misalignment between the backend command surface and the frontend dispatch, requiring cross-layer debugging to resolve.

Debug missing Hermes TUI slash commands by running a structured diagnostic workflow that inspects the command registry, gateway handlers, and frontend dispatch. This step-by-step investigation reproduces the issue and pinpoints which layer fails to surface the command.

Stale UI reflections in Hermes TUI stem from config updates not propagating correctly through the gateway to the Ink frontend. The mismatch occurs when one layer remains out of sync, necessitating cross-layer inspection of gateway handlers and frontend dispatch logic.

Hermes TUI debugging requires familiarity with Python for the command registry and gateway, plus TypeScript for the Ink frontend. Architecture-aware investigation spans all three layers to locate and patch cross-layer command misalignment effectively.

Fixing Hermes TUI command inconsistencies requires an architecture-aware approach that inspects the Python command registry, gateway handlers, and Ink frontend dispatch together. This ensures commands surface consistently across CLI and TUI autocomplete.

When Hermes TUI slash command autocomplete malfunctions, first inspect the Python command registry to confirm the command exists, then verify gateway handlers and frontend dispatch alignment. This structured workflow isolates which layer causes the failure.