Repository navigation
Aspire CLI warns that CLI is required... #19611
Description
Is there an existing issue for this?
- I have searched the existing issues
Describe the bug
When I look at the log file for a CLI build after aspire run, I get a warning complaining that "Some Aspire features require the Aspire CLI bundle". Despite the fact I ran the build with the Aspire CLI - aspire run
ASPIRE010: AlexCrome.Aspire.Hosting.UserJwts.AppHost is configured with AspireUseCliBundle=false. Some Aspire features require the Aspire CLI bundle. Set AspireUseCliBundle=true to enable those features, or suppress ASPIRE010 to continue without the bundle. See https://aka.ms/aspire/diagnostics/aspire010 for more information.
Expected Behavior
I ran this from the CLI, there shouldn't be a warning about needing the CLI.
Steps To Reproduce
aspire run- Look at the CLI Logfile
The above example was specifically repoed with https://github.com/afscrome/aspire-dotnet-jwts but I've seen it with several projects, so I don't think the project really matters.
Exceptions (if any)
[2026-08-23 13:09:05.696] [DBUG] [ProcessExecutionFactory] dotnet(36172) waiting for exit
[2026-08-23 13:09:06.135] [INFO] [Build] Determining projects to restore...
[2026-08-23 13:09:06.431] [INFO] [Build] All projects are up-to-date for restore.
[2026-08-23 13:09:06.454] [INFO] [Build] C:\Users\alex\.nuget\packages\aspire.hosting.apphost\13.5.0\build\Aspire.Hosting.AppHost.targets(157,5): warning ASPIRE010: AlexCrome.Aspire.Hosting.UserJwts.AppHost is configured with AspireUseCliBundle=false. Some Aspire features require the Aspire CLI bundle. Set AspireUseCliBundle=true to enable those features, or suppress ASPIRE010 to continue without the bundle. See https://aka.ms/aspire/diagnostics/aspire010 for more information. [S:\aspire-dotnet-jwts\.claude\worktrees\fix-namespace-inconsistencies-9d29a4\playground\AppHost\AlexCrome.Aspire.Hosting.UserJwts.AppHost.csproj]
Aspire doctor output
Checking Aspire environment...
Aspire Environment Check
========================
Aspire
⚠️ Aspire CLI version 13.5.1 (channel: stable) is out of date. Latest version is 13.5.2 (channel: stable)
Run 'aspire update' to update Aspire CLI.
✅ Developer Control Plane (DCP) connection health checks succeeded
AppHost
✅ AppHost version 13.5.0 (playground\AppHost\AlexCrome.Aspire.Hosting.UserJwts.AppHost.csproj)
.NET SDK
✅ .NET 10.0.400 installed (x64)
Container Runtime
⚠️ Docker: installed but not running ← active
Start Docker Desktop
Environment
✅ Operating system: Windows 10.0.26200.0
✅ HTTPS development certificate is trusted
Development Tools
✅ Aspire extension for VS Code is installed
Summary: 6 passed, 2 warnings, 0 failed
For detailed prerequisites: https://aka.ms/aspire-prerequisites
Aspire CLI Installations
========================
╭────────────────────────────────────────┬────────────────────────────────────────┬──────────┬───────────┬─────────────╮
│ Path │ Version │ Channel │ Route │ PATH status │
├────────────────────────────────────────┼────────────────────────────────────────┼──────────┼───────────┼─────────────┤
│ C:\Users\alex\.aspire\bin\aspire.exe │ 13.5.1+69db530a4816698cf1d5fa4557933e0 │ stable │ (unknown) │ active │
│ (current) │ ac4f127c6 │ │ │ │
│ C:\Users\alex\.aspire\dogfood\pr-18930 │ 13.5.0-pr.18930.g9d15e424 │ pr-18930 │ pr │ not on PATH │
│ \bin\aspire.exe │ │ │ │ │
╰────────────────────────────────────────┴────────────────────────────────────────┴──────────┴───────────┴─────────────╯
Anything else?
No response
Activity
joperezr commentedon Aug 23, 2026
🤖 Aspire triage pass — 2026-08-23 13:51 UTC
Area:
area-cliKind: bug
Repro: yes-minimal — see the "Steps To Reproduce" section (
aspire runthen inspect the CLI logfile)Affected version(s): AppHost 13.5.0 / CLI 13.5.1 (latest CLI: 13.5.2)
Severity: S4 — misleading
ASPIRE010warning is emitted even though the AppHost was launched via the CLI; build still succeeds and a workaround exists (setAspireUseCliBundle=trueor suppressASPIRE010).Urgency: ⚪ backlog — no milestone
Reason:
ASPIRE010/AspireUseCliBundleis a newly-introduced 13.5 diagnostic (not a prior-working scenario), so this is a false-positive/UX polish issue rather than a regression, and it has a clear workaround. Does not clear the raised 13.5 bar (regression or S1/S2 no-workaround).Suggested owner(s): Damian Edwards (@DamianEdwards) (feature author), backup Jose Perez Rodriguez (@joperezr)
Evidence:
AspireUseCliBundle/ASPIRE010feature end-to-end: Add AppHost CLI bundle opt-in #16811 (Add AppHost CLI bundle opt-in), Default AppHosts to use the CLI bundle #18188 (Default AppHosts to use the CLI bundle), Adjust required CLI behavior for C# AppHosts #18850 (Adjust required CLI behavior for C# AppHosts), Enable CLI bundle in C# AppHost templates #19076 (Enable CLI bundle in C# AppHost templates)ASPIRE010warning text most recently: Surface ASPIRE010 help link inline in warning text #19375 (Surface ASPIRE010 help link inline in warning text)/src/Aspire.CliConfidence: medium
Needs human?: no
DamianEdwards commentedon Aug 23, 2026
Hmm I think David Fowler (@davidfowl) and I spoke about this scenario and decided that we still wanted to force this message and project change rather than just assume based on how the AppHost was launched at a given time. The behavior between the modes is different enough and the requirements change is large enough that we felt it best to force the user to be aware of the change and opt-in before we make it mandatory.
afscrome commentedon Aug 26, 2026
So this warning only shows up in the logs - it doesn't show up directly with
aspire run. So if the goal is to warn people, many people will miss it.Somewhat related, the docs currently say this feature is Preview. It does feel wrong we are warning people to
bullyencourage users to opt in to a preview feature https://aspire.dev/get-started/aspire-sdk/#use-the-aspire-cli-bundle-for-orchestration-dependenciesDamianEdwards commentedon Aug 26, 2026
So if you use the CLI to launch, you don't see it anyway?
Not sure why it says preview, we'll get that updated.