debugging-hermes-tui-commands

Hermes TUI slash commands fail when the Python backend, gateway, and Ink frontend are misaligned. You must verify consistency across the COMMAND_REGISTRY, gateway dispatch, and frontend slash handlers to resolve missing autocomplete or broken execution.

To debug inconsistently mirrored slash commands, reproduce the failure in the Hermes TUI, then trace logs to locate the source. Check that the COMMAND_REGISTRY, gateway dispatch, and Ink frontend slash handlers are synchronized across all layers.

Local state synchronization issues occur when the Ink frontend loses consistency with the Python backend and gateway during reloads. Investigating the COMMAND_REGISTRY and slash handlers ensures the UI state properly mirrors the backend command definitions.

Yes, diagnosing Hermes TUI command integration requires access to the Python backend code, gateway implementation, and Ink frontend. Validating consistency across these three layers is necessary to identify where slash commands fail to dispatch or execute.

The best way to investigate a non-executing slash command is to run the Hermes TUI, trigger the command to reproduce the failure, and observe logs to locate the issue. Verify that gateway dispatch correctly routes to the Python backend handlers.

Yes, if Ink frontend slash autocomplete is broken, the debugging approach applies by tracing the command from the frontend back to the Python backend. It checks whether the COMMAND_REGISTRY correctly populates the frontend autocomplete suggestions.