debugging-hermes-tui-commands

Diagnose Hermes TUI slash command failures across Python registry, gateway, and Ink frontend.

Updated May 24, 2026
One-click install
npx skills add https://github.com/anxiety135790/hermes-skills --skill debugging-hermes-tui-commands-anxiety135790
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging-hermes-tui-commands
Source: https://github.com/anxiety135790/hermes-skills/tree/main/software-development/debugging-hermes-tui-commands
Command: npx skills add https://github.com/anxiety135790/hermes-skills --skill debugging-hermes-tui-commands-anxiety135790

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose and fix Hermes TUI slash commands when they are missing from autocomplete, behave differently in the CLI and TUI, or fail to update the interface after a config change.

Core Features & Use Cases

  • Cross-layer debugging: Trace a command through the Python registry, the TUI gateway, and the Ink/TypeScript frontend to find where the mismatch occurs.
  • Autocomplete repair: Add or correct CommandDef entries so commands appear with the right category, aliases, and subcommand hints.
  • Behavioral consistency: Resolve cases where a command works in one surface but not another, including local-only TUI handlers and gateway dispatch.
  • Live UI updates: Fix commands that persist settings but do not immediately refresh the rendered TUI state.

Quick Start

Use this skill to investigate why a Hermes slash command is missing or broken in the TUI, then verify the Python registry, gateway handler, and frontend command definition are aligned.

Frequently Asked Questions about debugging-hermes-tui-commands

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why do my Hermes TUI slash commands go missing from autocomplete after a config change?

Hermes TUI slash commands go missing from autocomplete when the Python registry, gateway dispatch, and Ink frontend handlers are not aligned. You must ensure consistent CommandDef registration and frontend state propagation to restore missing entries.

How do I fix slash commands that work in the CLI but fail in the TUI gateway?

To fix slash commands that work in the CLI but fail in the TUI, trace the command through the Python registry, gateway dispatch, and Ink frontend handlers to find the mismatch. Resolve local-only TUI handlers and update gateway command handling for behavioral consistency.

How do I update live interface state in a TypeScript TUI after a Python config change?

To update live interface state in a TypeScript TUI after a Python config change, verify that the gateway command handling and Ink frontend state propagation are correctly linked. Fix the frontend handlers to immediately refresh the rendered TUI state.

What causes inconsistent slash command behavior between the Python registry and the TypeScript frontend?

Inconsistent slash command behavior between the Python registry and the TypeScript frontend is caused by mismatched CommandDef entries and broken gateway dispatch. Correcting the CommandDef registration with the right category and aliases resolves this behavioral inconsistency.

How to diagnose a broken Hermes slash command across Python and TypeScript layers step by step?

To diagnose a broken Hermes slash command, trace it across the Python registry, TUI gateway, and Ink frontend handlers. Check the CommandDef registration, verify gateway command handling, and ensure frontend state propagation for reliable command discovery and execution.