Problem
A drag entering the Command Code desktop window can leave the “drop to attach” overlay stuck if the source process exits before the app receives a terminal drag event. The report describes the overlay remaining until reload and the renderer using 30–66% CPU while otherwise idle.
Expected behavior
The overlay should clear when the drag ends, including when the source disappears and no drop or dragleave arrives. An inactive overlay should not keep the renderer busy.
Reproduction
- Start dragging an item from another app over the Command Code window.
- End the source process during the drag.
- Check whether the overlay clears without reloading the desktop app.
Environment and evidence
Reported on Command Code GUI 0.1.37, macOS 27.0 (build 26A428), Apple silicon. The original report includes a renderer sample and CPU observations in the issue filed in the wrong repository.
Proposed direction
Please inspect the private desktop application code that owns the drag overlay and determine how to guarantee teardown when terminal drag events are missing. Candidate safeguards include handling all available end/focus/cancel paths, a bounded watchdog, and pausing overlay work when no drag is active. These are options for investigation, not a prescribed implementation; the renderer source is not present in this public repository, so the root cause remains to be confirmed by maintainers.
The public desktop repository contains installers, documentation, and issue tracking. Application source is private, so this report tracks the GUI behavior and does not claim to provide or test an application-code fix.
Automated posting by agentic team with human oversight.
Problem
A drag entering the Command Code desktop window can leave the “drop to attach” overlay stuck if the source process exits before the app receives a terminal drag event. The report describes the overlay remaining until reload and the renderer using 30–66% CPU while otherwise idle.
Expected behavior
The overlay should clear when the drag ends, including when the source disappears and no
dropordragleavearrives. An inactive overlay should not keep the renderer busy.Reproduction
Environment and evidence
Reported on Command Code GUI 0.1.37, macOS 27.0 (build 26A428), Apple silicon. The original report includes a renderer sample and CPU observations in the issue filed in the wrong repository.
Proposed direction
Please inspect the private desktop application code that owns the drag overlay and determine how to guarantee teardown when terminal drag events are missing. Candidate safeguards include handling all available end/focus/cancel paths, a bounded watchdog, and pausing overlay work when no drag is active. These are options for investigation, not a prescribed implementation; the renderer source is not present in this public repository, so the root cause remains to be confirmed by maintainers.
The public desktop repository contains installers, documentation, and issue tracking. Application source is private, so this report tracks the GUI behavior and does not claim to provide or test an application-code fix.