cmux-diagnostics

Diagnose cmux integration issues via read-only health checks and support-safe reports.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/selfagency/agentsy --skill cmux-diagnostics-selfagency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cmux-diagnostics
Source: https://github.com/selfagency/agentsy/tree/main/.agents/skills/cmux-diagnostics
Command: npx skills add https://github.com/selfagency/agentsy --skill cmux-diagnostics-selfagency

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you diagnose why cmux hooks, notifications, session restore, settings, socket/automation access, or agent resume behavior is failing or behaving unexpectedly, without leaking sensitive local data.

Core Features & Use Cases

  • Read-only health checks for the cmux CLI and socket connectivity, including quick failure classification.
  • Settings validation focused on cmux configuration health and specifically terminal auto-resume behavior.
  • Hook installation and session-restore evidence checks across common agent integrations by verifying expected markers and presence of support-safe session store files.
  • Support-safe reporting that summarizes paths and timestamps while avoiding raw hook configs, session JSON contents, logs, tokens, and secrets.
  • Use case: When an agent doesn’t auto-resume after reopening panes in cmux, run the diagnostics to confirm whether hooks are installed, session stores exist, and terminal.autoResumeAgentSessions allows resume.

Quick Start

Run the bundled diagnostics script to generate a read-only report for your current cmux setup.

Frequently Asked Questions about cmux-diagnostics

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

FAQPage Schema
Why doesn't my agent auto-resume when reopening cmux panes?

Agent auto-resume failures usually result from missing hook installations or disabled terminal.autoResumeAgentSessions settings. A cmux CLI health check verifies hook installation evidence and confirms whether session restore artifacts exist to enable proper session recovery.

How do I check if my cmux socket path is unreachable or misconfigured?

Run a read-only cmux diagnostics script to test socket accessibility and validate configuration health. This generates a support-safe report classifying connectivity failures without exposing raw environment data or sensitive tokens.

What is the safest way to diagnose cmux hook installation issues?

Execute a local read-only cmux diagnostics script to verify expected hook markers and summarize installation status. This approach deliberately avoids exposing raw hook configs, session logs, or environment secrets during troubleshooting.

Can I troubleshoot cmux settings validation without leaking sensitive environment data?

Yes, you can troubleshoot cmux settings validation safely by generating a support-safe health report. The diagnostics process summarizes configuration paths and timestamps while strictly avoiding printing raw session JSON contents, tokens, or environment-sensitive data.

What should I do when cmux session restore artifacts are missing or failed?

When cmux session restore artifacts are missing, run a CLI health check to confirm the absence of support-safe session store files. This identifies whether broken hook installs or misconfigured terminal auto-resume behavior caused the capture failure.