stuck

Diagnosing a frozen CLI session requires inspecting process states, sampling CPU and memory, and tracing child processes. This skill performs these checks to identify high CPU usage, zombie processes, or I/O hangs without terminating the session.

Processes become stuck due to high CPU usage, stopped states, zombie processes, I/O hangs, memory pressure, or stuck child processes. Identifying these health issues helps explain what the session was doing before it stalled.

Yes, you can check for zombie processes and memory pressure across Windows, macOS, and Linux. The skill discovers relevant processes on these operating systems and examines them for signs of stalls, stopped states, and I/O hangs.

To generate a diagnostic report for a slow session without killing the process, request an investigation. The skill collects process details and debug log clues, producing a summary with likely causes and recommended next steps without terminating anything.

The best way to trace child processes during an unresponsive session is to use child-process tracing alongside CPU and memory sampling. This identifies stuck child processes and collects follow-up details to explain the stall.

Yes, session debugging works when CPU usage is maxed out. The skill specifically checks for signs of high CPU usage and memory pressure to determine if these factors are causing the session to freeze or become unusually slow.