Use when local .codex state needs maintenance — sessions/logs/worktrees/config bloat cleanup, thread metadata bloat detection, or provider metadata sync between SQLite and JSONL records. Covers both storage cleanup and metadata consistency.
Use for a health check when a user reports a slow computer, high memory use, swap/pagefile pressure, CPU saturation, thermal throttling, disk I/O pressure, slow code execution, profiler needs, Rosetta/runtime architecture concerns, WSL/Docker/Linux container resource pressure, or asks for a reproducible health report on macOS, Windows, or Linux.
Use for desktop stability or battery health when a macOS laptop or desktop is used as a mostly plugged-in workstation — always-plugged-in behavior, sleep/wake instability, USB device dropouts, audio device disappearance, display sleep issues, or battery charge limits.
Use when watching a folder for file changes to run commands on edit, restart a local service, trigger a backup, send a notification, or debug file-change automation on macOS or Linux.
Use to establish a baseline when a user reports slow internet, unstable latency, packet loss, DNS delays, Wi-Fi or Ethernet issues, poor speedtest results, MTU/path-MTU problems, loaded latency, browser-only or terminal-only slowness, IPv4/IPv6 differences, background bandwidth contention, stale saved networks, mDNS/Bonjour/LLMNR noise, VPN-on networking, proxy/PAC/TUN overlap, or Clash/V2Ray/Xray/Mihomo routing conflicts on macOS, Windows, or Linux.
Use for path conversion when a user sends a Windows UNC path, macOS smb:// URL, /Volumes path, mounted share path, or asks to convert, normalize, open, or list a file-system path across Windows and macOS.
Use when a macOS app, script, launchd job, CLI, or background process gets permission denied / Operation not permitted, Full Disk Access, Files and Folders, TCC, sandbox, or protected Library/Containers access errors, or TCC permission drift after moving, rebuilding, or re-signing a binary.
Use when monitoring long-running local commands with heartbeat liveness checks — background jobs, builds, scripts, services, downloads, or batch automation that may hang, timeout, crash, or lose logs.