debugging-hermes-tui-commands

Diagnose and fix Hermes TUI slash command misalignment across Python backend, gateway, and Ink frontend.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hermes TUI slash commands often fail to appear in autocomplete or work inconsistently across the Python backend, the gateway, and the Ink frontend. This skill provides a structured approach to diagnose and align the multi-layer command pipeline so developers can quickly fix mismatches.

Core Features & Use Cases

  • Cross-layer debugging blueprint for Hermes TUI slash commands spanning Python CLI, the JSON-RPC gateway, and the Ink/TypeScript frontend.
  • Investigation steps, common failure modes (missing autocomplete, CLI-TUI mismatch, config not applying live), and concrete remediation patterns.
  • Use case: you added a new slash command but it doesn't appear in autocomplete in the TUI; this skill guides you to synchronize the registry, gateway known commands, and frontend dispatch.

Quick Start

Identify and fix a missing Hermes slash command by verifying COMMAND_REGISTRY, gateway dispatch, and frontend slash handlers, then rebuild the UI.

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 slash commands work in the CLI but not the TUI?

Hermes slash commands work in the CLI but fail in the TUI when the command pipeline is misaligned across the Python backend, gateway, and Ink frontend. You must verify the COMMAND_REGISTRY, gateway known commands, and frontend slash handlers to synchronize the layers.

How do I fix Hermes TUI slash commands missing from autocomplete?

To fix Hermes TUI slash commands missing from autocomplete, verify the COMMAND_REGISTRY in hermes_cli/commands.py, ensure the gateway dispatches the known commands, update the Ink frontend slash handler, and rebuild the TUI to apply the changes.

What is the best way to debug a multi-layer slash command mismatch in a TypeScript and Python TUI?

The best way to debug a multi-layer slash command mismatch is to systematically trace the command from the Python CLI backend through the JSON-RPC gateway to the Ink TypeScript frontend, checking the registry and dispatch handlers at each layer.

Why does my Hermes TUI config persist but not update the live UI?

Hermes TUI config persists without live UI updates when the frontend slash handler fails to dispatch the new configuration state. You need to verify the frontend slash handler and rebuild the TUI to ensure the Ink UI reflects the changes.

Do I need to rebuild the TUI after adding new Hermes slash commands?

Yes, you need to rebuild the TUI after adding new Hermes slash commands to ensure the Ink frontend reflects the updated registry and gateway dispatch changes. Rebuilding synchronizes the TypeScript frontend with the Python backend.