cmux-diagnostics

Diagnose cmux integration failures with read-only runtime and config evidence.

1|Updated Sep 6, 2015
One-click install
npx skills add https://github.com/deerawan/dotfiles --skill cmux-diagnostics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cmux-diagnostics
Source: https://github.com/deerawan/dotfiles/tree/main/agents/skills/cmux-diagnostics
Command: npx skills add https://github.com/deerawan/dotfiles --skill cmux-diagnostics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

cmux-diagnostics helps troubleshoot when cmux hooks, notifications, session restore, settings, browser automation, socket access, CLI control, or agent resume behavior is not working by producing a read-only, support-safe diagnostics report.

Core Features & Use Cases

  • Read-only cmux health checks: Verifies cmux CLI availability, connectivity (ping), and capabilities without dumping sensitive content.
  • Settings validation and auto-resume checks: Checks current cmux settings and the value of terminal.autoResumeAgentSessions to explain session restore outcomes.
  • Hook and session store evidence review: Summarizes whether expected hook configs exist and whether *-hook-sessions.json stores are present (without printing raw JSON contents).
  • Agent binary presence audit: Confirms which supported agent executables are available on PATH to explain hook setup gaps.

Quick Start

Run the bundled read-only script to generate a health report: ~/.agents/skills/cmux-diagnostics/scripts/cmux-diagnostics --include-context

Frequently Asked Questions about cmux-diagnostics

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

FAQPage Schema
Why is cmux not working when I try to restore agent sessions or run hooks?

cmux session restore failures often stem from missing hook configs, invalid settings, or absent session-store files. A read-only diagnostics report can validate settings, verify terminal.autoResumeAgentSessions, and check hook marker presence without exposing raw secrets.

How do I run a health check to troubleshoot cmux integration failures?

To run a cmux health check, execute the bundled read-only diagnostics script with the --include-context flag. This verifies CLI reachability, validates settings, inspects session-store file existence, and generates a support-safe summary of your runtime environment.

What is a support-safe cmux diagnostics report?

A support-safe cmux diagnostics report is a read-only health summary that validates settings, checks CLI connectivity, and audits hook config presence. It avoids printing raw secrets or file contents, ensuring you can safely share the output for troubleshooting.

Can I diagnose cmux socket access and agent binary issues without exposing sensitive config data?

Yes, you can diagnose cmux socket access and agent binary presence safely. The diagnostic script confirms which supported agent executables are available on PATH and checks socket health while strictly avoiding printing raw JSON contents or secrets.

Does cmux diagnostics require write access to fix session-store and hook configuration problems?

No, cmux diagnostics operates entirely in read-only mode. It checks CLI reachability, validates settings via cmux-settings, and inspects session-store file existence to explain restore behavior gaps without modifying any workspace configurations.

What should I check when cmux notifications and agent resume behavior stop functioning?

When cmux notifications or agent resume behavior stops, check the terminal.autoResumeAgentSessions setting value, verify hook config markers, and audit supported agent executables on PATH. Running a doctor-style diagnostics script provides this evidence quickly.