debugging-hermes-tui-commands

Debug Hermes TUI slash commands across Python, gateway, and Ink layers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It resolves broken or missing Hermes TUI slash commands caused by inconsistencies between the Python command registry, the TUI gateway JSON-RPC dispatch, and the Ink/TypeScript frontend handlers.

Core Features & Use Cases

  • Detects command-layer mismatch across the Python registry, gateway dispatch, and Ink UI autocomplete/handlers.
  • Guides end-to-end updates so a command definition exists and behaves consistently in both CLI/TUI and gateway/messaging paths.
  • Fixes specific failure modes like commands not appearing in autocomplete, working in CLI but failing in TUI, or persisting config without applying live UI state.

Quick Start

Use this skill when you notice a Hermes TUI slash command is missing from autocomplete or behaves differently than expected, then compare the command’s presence and handler wiring across Python, the gateway, and the Ink frontend until the layers are in sync.

Frequently Asked Questions about debugging-hermes-tui-commands

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

FAQPage Schema
Why is my Hermes TUI slash command missing from autocomplete but works in the CLI?

TUI slash command autocomplete fails when the Ink/TypeScript frontend handlers and Python COMMAND_REGISTRY are out of sync. You must validate command definitions across both layers to ensure the gateway dispatch logic correctly routes the JSON-RPC bridge requests.

How do I debug slash commands failing across the TUI gateway JSON-RPC bridge?

Debug TUI gateway slash command failures by tracing the dispatch logic from the Python COMMAND_REGISTRY through the JSON-RPC bridge. Verify that gateway handler routing matches the local Ink frontend handlers to resolve command fallthrough issues.

What causes a Hermes TUI command to persist configuration without applying live UI state updates?

Live UI state synchronization breaks when frontend handler routing fails to propagate updates after the gateway dispatches the command. Fixing this requires aligning the Ink/TypeScript local handler routing with the gateway's response to ensure immediate UI state propagation.

How do I synchronize slash command definitions between the Python registry and the Ink frontend?

Synchronize slash command definitions by validating the Python COMMAND_REGISTRY entries and ensuring matching gateway dispatch logic. Then update the Ink/TypeScript frontend handler routing so command behavior remains consistent across CLI and TUI paths.

Do I need to update the Python COMMAND_REGISTRY if a slash command only fails in the TUI?

Yes, even TUI-only failures require checking the Python COMMAND_REGISTRY. A command may exist locally but fail if the tui_gateway JSON-RPC dispatch logic lacks the matching handler wiring, causing inconsistencies between the CLI and TUI layers.

What is the best way to fix slash command dispatch mismatches in a TypeScript Ink UI?

Fix TypeScript Ink UI dispatch mismatches by comparing the command's handler wiring across the Python registry, gateway, and frontend. Update the local handler fallthrough and gateway dispatch logic until all layers execute the command consistently.