debugging-hermes-tui-commands

Debug slash command definitions across Python backend, TUI gateway, and TypeScript frontend.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves synchronization issues between the Python backend, TUI gateway, and TypeScript frontend, ensuring slash commands function correctly across all layers of the Hermes Agent.

Core Features & Use Cases

  • Cross-Layer Debugging: Identifies why commands fail to appear in autocomplete or behave inconsistently between the CLI and TUI.
  • Registry Synchronization: Ensures command definitions are correctly registered in the Python COMMAND_REGISTRY for proper gateway and frontend dispatch.
  • Use Case: When a newly added slash command works in the CLI but is missing from the TUI autocomplete menu, this skill provides the steps to verify the registry and rebuild the frontend.

Quick Start

Use the debugging-hermes-tui-commands skill to identify why the custom slash command is not appearing in the TUI autocomplete menu.

Frequently Asked Questions about debugging-hermes-tui-commands

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

FAQPage Schema
How do I fix a slash command that works in the CLI but is missing from the TUI autocomplete menu?

Debugging TUI slash commands involves verifying command registration in the Python backend, checking TUI gateway dispatch logic, and confirming TypeScript frontend handler implementation. Systematic verification across these three layers resolves command registry mismatches that cause UI or execution failures.

Why does my Hermes Agent slash command behave inconsistently between the CLI and TUI?

Yes, cross-layer debugging identifies why commands fail to appear in autocomplete or behave inconsistently. It traces execution failures across the Python COMMAND_REGISTRY, TUI gateway dispatch, and TypeScript frontend handlers to pinpoint the exact layer causing the mismatch.

How to synchronize slash command definitions across Python backend and TypeScript frontend layers?

Registry synchronization requires verifying command definitions in the Python COMMAND_REGISTRY to ensure proper gateway and frontend dispatch. You must check that the TypeScript frontend handler implementation matches the backend definitions to restore TUI autocomplete functionality.

What causes command registry mismatches and UI failures in Hermes TUI applications?

When a newly added slash command is missing from the TUI autocomplete menu, use this debugging process to verify the Python command registry, validate gateway dispatch logic, and rebuild the TypeScript frontend to restore proper command synchronization.