QE-0047-A·————-——-——T——:——:——
Sign out
Run a coding-agent performance audit on this computer. Detect macOS or Windows and record the hardware configuration first. Use only built-in, read-only tools. Do not spawn subagents or modify anything on the first pass.
𝟭. 𝗘𝘀𝘁𝗮𝗯𝗹𝗶𝘀𝗵 𝗮 𝗯𝗮𝘀𝗲𝗹𝗶𝗻𝗲.
Take several samples, not one snapshot.
Check CPU, load average or processor queue, memory pressure or available / committed memory, swap / pagefile growth, disk I/O, free space, thermal throttling, sleep blockers, attached displays, and process / thread counts.
If a metric is unavailable, report it and continue. Do not install tools.
𝟮. 𝗕𝘂𝗶𝗹𝗱 𝗮 𝗽𝗿𝗼𝗰𝗲𝘀𝘀 𝘁𝗿𝗲𝗲.
Aggregate the main process and helpers for each application family.
Focus on: → AI: Codex, Claude Code, MCP servers, code indexers, headless browsers → Development: Node / Bun / Python, Docker / WSL / VMs, dev servers, watchers, test processes, databases → Background: browser helpers, sync processes, updaters
Record the parent process, runtime, CPU, memory, disk and network activity, listening ports, project directory, and whether a terminal, editor, or active session is still using it.
𝟯. 𝗔𝘂𝗱𝗶𝘁 𝗲𝘃𝗲𝗿𝘆 𝘀𝘁𝗮𝗿𝘁𝘂𝗽 𝘀𝗼𝘂𝗿𝗰𝗲.
macOS: → Login Items and Allow in Background → LaunchAgents, LaunchDaemons, Homebrew services → system and network extensions
Windows: → Startup Apps, Services, Scheduled Tasks, Run keys → WSL and Docker Desktop → VPN, proxy, and network filters
On both platforms, inspect browsers, menu-bar or system-tray monitors, Adobe and Office helpers, cloud sync, and stale VPN, DNS, or proxy entries.
𝟰. 𝗜𝗻𝘀𝗽𝗲𝗰𝘁 𝗹𝗮𝗿𝗴𝗲 𝗱𝗶𝘀𝗸 𝗰𝗼𝗻𝘀𝘂𝗺𝗲𝗿𝘀.
Include build outputs, node_modules, Docker data, DerivedData or simulators, Downloads, and duplicate project copies. Do not bulk-delete caches or personal files.
𝟱. 𝗟𝗮𝗯𝗲𝗹 𝗲𝗮𝗰𝗵 𝗶𝘁𝗲𝗺.
Use: active and needed / idle / orphaned / duplicate / unknown.
Prioritize items that meet all three conditions: → long-running → no longer needed → sustained CPU, memory, disk, or network use
𝟲. 𝗥𝗲𝘁𝘂𝗿𝗻 𝗮 𝗱𝗿𝘆-𝗿𝘂𝗻 𝘁𝗮𝗯𝗹𝗲.
For every item, include: → evidence → expected benefit and risk → whether a restart is required → recommended action: keep / quit normally / stop / disable at startup / uninstall / investigate → reversible commands and rollback steps
Without my item-by-item approval, do not kill processes, delete files, uninstall software, unload services, change startup items or network settings, or restart the computer. If sudo or Administrator access is required, explain the purpose and risk, then wait for approval.
Do not disable FileVault, BitLocker, firewalls, Defender, or other system security controls. Preserve the active agent sessions, terminals, editors, databases, sync jobs, VPNs, and security tools that I explicitly say are still in use.
After I approve the plan, handle one group at a time and remeasure after each. Once done, reboot, wait 5–10 minutes, and measure again. Use the computer normally for a day, then repeat the audit. Show the before / after results and flag any processes or services that returned.