debugging-hermes-tui-commands

Slash command execution failures occur when the Python COMMAND_REGISTRY defines a command but the tui_gateway dispatcher lacks the matching route. You must verify gateway dispatch inclusion to ensure the Ink frontend request reaches the correct handler.

To add a Hermes TUI slash command, synchronize the Python COMMAND_REGISTRY entry, the tui_gateway dispatch route, and the Ink TypeScript frontend handler. Compare canonical command definitions across all layers before testing in the running TUI.

Live Hermes TUI UI state failures indicate missing immediate state patching in the Ink frontend rendering paths. The configuration persists correctly but the TUI requires correct frontend state updates to reflect changes without restarting.

Debugging missing Hermes TUI autocomplete commands requires tracing command registration from the Python COMMAND_REGISTRY through to the Ink TypeScript slash handling code. Identify where synchronization breaks between the backend registry and frontend handlers.

Inconsistencies between Hermes CLI and TUI slash command behavior occur when the Python COMMAND_REGISTRY and the TUI gateway dispatch fall out of sync. You must align slash command names across hermes_cli and ui-tui to resolve the discrepancies.