`aspire stop --force` to stop persistent containers (& executables)

[afscrome]

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

Whilst running persistent containers (and soon executables) can be great for improving startup time of your app host, it can become a resource leak if you have a lot of these, and you move from one app host to another.

Describe the solution you'd like

Provide a way to stop all persistent resources when an application shuts down. aspire stop --force seems like a logical way to do this, but any other command would work.

Additional context

No response

[MihuBot]

I'm a bot. Here is a possible related and/or duplicate issue (I may be wrong):

• Add an option to aspire stop to stop persistent containers too #15855

[joperezr]

🤖 Aspire triage pass — 2026-05-20 21:55 UTC

Area: area-cli
Kind: feature-request
Repro: none — feature request, no repro needed
Affected version(s): not specified (latest: 13.3.x)
Severity: S4 — quality-of-life improvement; resource leak only matters across many app-host switches and only when users opt into persistent resources

Urgency: ⚪ backlog — no milestone
Reason: S4 feature request, no regression, opt-in behavior with a known manual workaround (stopping containers via Docker/runtime CLI)

Suggested owner(s): @JamesNK (score 261), backup @mitchdenny (score 32)
Evidence:

• JamesNK authored 77 merged PRs in area-cli in the last 90 days
• JamesNK resolved 15 area-cli issues as completed in the last 180 days
• mitchdenny authored 4 merged PRs and resolved 10 area-cli issues as completed in the same windows
• No area-cli / src/Aspire.Cli entry found in .github/CODEOWNERS

Confidence: high
Needs human?: no

Dry-run mode — no labels or milestone applied. Reply /triage apply to promote, or edit and reapply.