debugging-hermes-tui-commands

Debug missing TUI autocomplete by aligning the Python command registry, gateway dispatch, and Ink UI definitions. This Skill diagnoses cross-layer inconsistencies to resolve why a slash command does not appear in the autocomplete suggestions.

Slash commands behave differently between CLI and TUI due to desynchronized Python command registry and frontend definitions. This Skill provides cross-layer debugging workflows to identify and resolve inconsistent command execution behavior across the gateway and UI.

Synchronize slash command updates by applying consistent command definitions across the Python registry, gateway JSON-RPC bridge, and Ink TypeScript frontend. This Skill guides cross-layer alignment to ensure backend updates reflect correctly in the TUI.

Yes, you can reproduce slash command errors by launching Hermes in TUI mode and observing the autocomplete, gateway, and TUI handling paths. This Skill provides debug templates to systematically reproduce and resolve common cross-layer issues.

The best way to troubleshoot TUI slash command failures is performing cross-layer consistency checks across the Python registry, gateway, and frontend. This Skill provides structured debugging workflows to isolate and resolve command execution errors.

The gateway JSON-RPC bridge dispatches TUI slash commands between the Python command registry and the Ink TypeScript frontend. This Skill ensures the gateway dispatch aligns with canonical command definitions to maintain consistent error handling and execution.