debugging-hermes-tui-commands

Hermes TUI slash commands go missing from autocomplete when command definitions are mismatched across the Python COMMAND_REGISTRY, the TUI gateway dispatcher, and the Ink frontend. Validating the registry as the canonical source and checking frontend handler registration resolves the inconsistency.

Debugging non-executing slash commands involves verifying that the TUI gateway dispatches the known command and that the Ink frontend handler fallthrough routes to the correct handler with consistent arguments and category metadata, bridging the Python backend to the TypeScript UI.

Live UI state debugging addresses cases where persisted configurations are saved correctly but the Hermes TUI fails to reflect changes immediately, requiring validation of frontend state synchronization and command handler updates across the Ink TypeScript layer.

Command registry synchronization works by treating the Python COMMAND_REGISTRY as the canonical source, ensuring the gateway JSON-RPC dispatches known commands, and verifying the Ink TypeScript frontend handlers match the registered aliases, subcommands, and category metadata.

Adding new slash commands requires updating the Python COMMAND_REGISTRY first, then confirming the TUI gateway recognizes the new command for dispatch, and finally verifying the Ink frontend handler implements the execution logic and autocomplete entries correctly.

Fixing inconsistent slash command behavior between CLI and TUI requires an end-to-end command-layer diagnosis that checks the Python registry definitions, gateway dispatch coverage, and frontend handler fallthrough to ensure the correct handler executes with consistent arguments.