hotplex-diagnostics

Diagnose HotPlex Gateway runtime issues from symptoms to root cause.

47|15|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/hrygo/hotplex --skill hotplex-diagnostics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hotplex-diagnostics
Source: https://github.com/hrygo/hotplex/tree/main/.agents/skills/hotplex-diagnostics
Command: npx skills add https://github.com/hrygo/hotplex --skill hotplex-diagnostics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hotplex-diagnostics helps you diagnose why the HotPlex Gateway appears healthy while users see no updates, slow responses, stuck tasks, or stalled streaming—by narrowing down failures from process state to the feedback pipeline and platform adapters.

Core Features & Use Cases

  • Process & Port Verification: Check Gateway/WebChat/Admin worker subprocesses, PID-file consistency, and expected localhost listening to confirm the system is truly alive.
  • Session State Consistency: Analyze HotPlex session counts and running/idle states across SQLite and on-disk Claude Code session files to detect orphaned/zombie/stale-resume conditions.
  • Feedback Continuity & Stall Classification: Cross-validate Worker output timestamps against platform delivery timestamps to detect pipeline stalls, backpressure drops, adapter failures, or client disconnects (including silent stalls).
  • Targeted Log Forensics: Search for meaningful WARN/ERROR patterns, reconstruct per-session timelines, and map symptoms to specific bridge/hub/platform/adapter failure modes.
  • Adapter Connectivity Checks: Investigate Feishu/Slack reconnection patterns and potential connection leaks that can cause recurring streaming failures.
  • Cross-platform Guidance: Provide Linux/macOS vs Windows command alternatives for practical debugging.

Quick Start

Ask to run hotplex-diagnostics when a user reports that HotPlex streaming is stuck or no longer produces output during a session, or before/after deployment to verify Gateway/Worker/adapters are functioning.

Frequently Asked Questions about hotplex-diagnostics

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

FAQPage Schema
How do I diagnose HotPlex Gateway streaming stalls when the system appears healthy?

Diagnose HotPlex Gateway streaming stalls by cross-validating Worker output timestamps against platform delivery timestamps to detect pipeline stalls, backpressure drops, adapter failures, or client disconnects causing silent stalls despite healthy status.

Why does my HotPlex session show no updates or stuck tasks during runtime?

HotPlex sessions show no updates or stuck tasks due to session state inconsistencies. Analyze running and idle states across SQLite and on-disk Claude Code session files to detect orphaned, zombie, or stale-resume conditions blocking task progression.

What is the best way to troubleshoot Feishu or Slack adapter reconnection leaks?

Troubleshoot Feishu or Slack adapter reconnection leaks by investigating reconnection patterns and potential connection leaks. Targeted adapter connectivity checks identify recurring streaming failures caused by platform adapter network drops.

How do I verify HotPlex Gateway subprocesses are truly alive during incident response?

Verify HotPlex Gateway subprocesses are alive by checking Gateway, WebChat, and Admin worker processes, PID-file consistency, and expected localhost listening. Process and port verification confirms the system is truly running during incident response.

Can I run HotPlex Gateway diagnostics on both Linux and Windows environments?

You can run HotPlex Gateway diagnostics on Linux, macOS, and Windows environments. The diagnostic process provides cross-platform command alternatives to ensure practical debugging across different operating systems during health checks.

How do I reconstruct per-session timelines from HotPlex WARN and ERROR log patterns?

Reconstruct per-session timelines from HotPlex WARN and ERROR log patterns using targeted log forensics. Search for meaningful error patterns and map symptoms to specific bridge, hub, platform, or adapter failure modes for actionable reporting.