debugging-hermes-tui-commands

Synchronize Python backend, TUI gateway, and Ink/TypeScript slash command handlers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Complex, multi-layer issues in Hermes TUI slash commands across Python backend, TUI gateway, and Ink/TypeScript frontend, leading to autocomplete gaps, missing dispatch, and out-of-sync command definitions.

Core Features & Use Cases

  • Cross-layer debugging guidance for Hermes TUI slash commands spanning Python, gateway, and frontend.
  • Investigation steps, common failure modes, and concrete remediation patterns to restore consistent behavior.
  • Use cases include when autocomplete omits commands, when CLI and TUI behave differently, or when gateway dispatch is silent.

Quick Start

Run hermes --tui and reproduce the slash command issue to observe autocomplete and dispatch behavior.

Frequently Asked Questions about debugging-hermes-tui-commands

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

FAQPage Schema
Why does a TUI slash command go missing from autocomplete in Hermes?

TUI slash command autocomplete gaps in Hermes usually occur when the command registry is out of sync with the gateway or Ink frontend. This requires cross-layer debugging to synchronize the Python backend, gateway, and TypeScript handlers.

How do I debug a Hermes TUI slash command that fails to dispatch from the gateway?

Debugging a Hermes TUI gateway dispatch failure involves investigating the Python backend command registry, verifying gateway known commands, and ensuring the Ink/TypeScript frontend slash handlers are properly synchronized.

What causes a Hermes command to behave differently in the CLI versus the TUI?

Inconsistent command behavior between the Hermes CLI and TUI stems from mismatches across the Python backend, gateway, and frontend layers, requiring synchronization of the command registry and local TUI handlers.

How do I synchronize the command registry across the Hermes Python backend and TypeScript frontend?

To synchronize the command registry, you must align the Python backend definitions, gateway known commands, and local Ink/TypeScript slash handlers, then apply verification steps to confirm consistent behavior.

Does debugging Hermes TUI commands require knowledge of both Python and TypeScript?

Yes, debugging Hermes TUI commands requires understanding Python for the backend command registry and TypeScript for the Ink frontend slash handlers to resolve cross-layer inconsistencies effectively.