Run a git bisect against a behavior reproducible only with muxrun-managed dev servers (e.g., "the dev server started crashing on startup", "the API began returning 500s some time last week"). Use when the user wants to find the commit that introduced a runtime regression that requires a live process to observe.
Diagnose muxrun environment and runtime issues — missing tmux, stale daemon PIDs, leftover sessions, port conflicts, broken config. Use when "muxrun isn't working", commands hang or error out, or after an unclean shutdown / crash. Read-only by default; only takes destructive action with explicit user confirmation.
Convert an existing docker-compose.yml, Procfile, or foreman/honcho config into a muxrun.toml. Use when the user wants to migrate from Compose/Procfile to muxrun, or asks to "import compose" / "convert Procfile" / "use muxrun instead of compose".
Analyze the current repository and generate a tailored muxrun.toml. Use when the user wants to start using muxrun in a project that has no config yet, or asks to "set up muxrun" / "generate muxrun.toml" / "initialize muxrun".
Diagnose and fix slow startup, restart loops, or excessive file-watch churn in a muxrun setup. Use when the user complains that muxrun is "slow", apps "keep restarting", "rebuilds too often", or that watch is "too aggressive / fires on everything".
Stream a muxrun-managed app's logs and surface anomalies (panics, stack traces, 5xx responses, slow requests) in real time. Use when the user wants to "watch", "tail", "follow", or "monitor" an app's output, or asks to be alerted when something goes wrong.
Identify which muxrun-managed app(s) are failing or restart-looping, fetch their recent output, and pinpoint a likely cause. Use when the user says something is "broken", "not working", "crashing", "won't start", or asks "why is X failing?" about a running muxrun setup.