Sorry not a solution, but you sparked a side-thought...�� To avoid sometimes being swamped by Pre-Debug windows.�� Instead of an error bringing up an individual Pre-Debug window, we could have error go into a queue which a singleton Pre-Debug window could have a view into.��This "Error Queue Viewer"�� would have on row per error, and you click on a row to open a normal debugger, much like you click <Debug> button in the existing Pre-Debug window.�� In a headless image, the Error Queue Viewer would not appear, but the error would keep being queued until the next time the Error Queue Viewer is manually opened.�� The same error-queue might provide a similar��interface point for Pharo Remote Tools, so you can see errors that occurred while you were not connected.