/dotnet-helpers:cleanup

Kill orphaned .NET compiler processes using the cleanup MCP tool and report what was reclaimed.

Steps

Call the cleanup MCP tool with no additional parameters:

Wait for the result.

Present the output clearly:

List each process that was killed (name + PID if available).
Report the total estimated memory reclaimed (e.g., "freed ~380 MB").
If nothing was killed, report that no orphaned processes were found — this is a good outcome.

Suggest running cleanup proactively in these situations:

on a resource-constrained machine (under 8 GB RAM, integrated graphics) — stale VBCSCompiler instances from previous sessions accumulate ~100–400 MB each.

Kill orphaned .NET compiler processes using the cleanup MCP tool and report what was reclaimed.

Call the cleanup MCP tool with no additional parameters:

Wait for the result.

Present the output clearly:

List each process that was killed (name + PID if available).
Report the total estimated memory reclaimed (e.g., "freed ~380 MB").
If nothing was killed, report that no orphaned processes were found — this is a good outcome.

Suggest running cleanup proactively in these situations:

on a resource-constrained machine (under 8 GB RAM, integrated graphics) — stale VBCSCompiler instances from previous sessions accumulate ~100–400 MB each.