[Feedback]: Guard against CPU saturation from concurrent background work

The issue describes a problem in the private desktop application source, which is not in this repository. The first step is to understand the architecture by reading the linked issue in the command-code repository. The goal is to design a concurrency safeguard or visibility feature for background work. 'Done' means a design proposal for the GUI behavior, not a code fix.

Problem

In Command Code GUI 0.1.37, the desktop app launched more than 20 concurrent CPU-heavy test processes as child shells. The reported machine became unusable, with load average above 220, delayed or unresponsive UI, and no clear indication or limit for the number of heavy jobs running.

The work was legitimate and eventually completed. The issue is the desktop experience when agent work fans out beyond the machine's capacity: users have no visible guardrail or clear feedback before the system becomes unresponsive.

Expected behavior

The desktop app should make concurrent background work visible and provide a safe, predictable way to limit or manage excessive fan-out, without silently breaking normal parallel tasks.

Reproduction

This depends on workload. Run an agent task that launches many CPU-bound subprocesses in the desktop app and observe system responsiveness and whether the app exposes active work or a concurrency safeguard.

Environment and evidence

Reported on Command Code GUI 0.1.37, macOS 27.0 (build 26A428), Apple silicon with 10 cores and 64 GB RAM. The original report and measurements are in the issue filed in the wrong repository.

Questions for maintainers

Please trace which layer owns desktop-launched background work and where admission control or visibility can be implemented. Possible approaches include an app-side concurrency limit, a warning or queue, or a visible active-work indicator. The failure should be investigated against the app's actual process and task lifecycle before choosing a design; this public repository does not contain application source, and the report alone does not establish which layer should own the safeguard.

The public desktop repository contains installers, documentation, and issue tracking. Application source is private, so this issue tracks the GUI behavior and does not claim to provide or test an application-code fix.

Automated posting by agentic team with human oversight.