Is there an existing issue for this?
Describe the bug
This particular issue repos fairly reliably when you run the app host w/out debugging, but I'm not certain that it's exclusive to running without debugging.
Process is disconnected from Aspire
Aspire claims that process is running, but I see no console output from it in aspire. Also, aspire thinkis the process id is 0, which is interesting...
Copilot also found the following in the logs
[AppHost/IdeExecutableRunner] Recycling connection...
{"error": "received IDE run session notification with empty session ID"}
If I look in VS Code, VS code seems to be spawning this process into a new terminal window

So the process is being created. Just not being fully linked up with DCP
DCP Proxy doesn't work
VS Code output suggests that the process is actually running
2026-08-27T17:45:52.590326Z INFO aspire_sample_rust_app: starting rust sample address=0.0.0.0:59411
And if you hit that endpoint directly, you get a response.
But if you try to access it through the DCP proxy, it hangs. (And hence the rust app ends up in an unhealthy state).
Disconnected process doesn't get killed
If I stop the apphost process, the process in this terminal window doesn't get killed along with it, so continues running.
Even more problematic, if you ctrl+c the process and then try to use the terminal as a regular window, aspire run doesn't work.
OTLP doesn't work
When starting this project without debugging, OTLP doesn't work. It seems that the OTLP endpoint is wrong. The Aspire dashboard thinkis it's https://localhost:50497. But hte process think's its on port 4318.
OTEL_BLRP_SCHEDULE_DELAY 1000
OTEL_BSP_SCHEDULE_DELAY 1000
OTEL_EXPORTER_OTLP_ENDPOINT http://localhost:4318/
OTEL_EXPORTER_OTLP_HEADERS x-otlp-api-key=2798545f9ec84d46fb9a05356e81987d
OTEL_EXPORTER_OTLP_PROTOCOL grpc
OTEL_INSTRUMENTATION_GENAI_CA… false
OTEL_METRIC_EXPORT_INTERVAL 1000
OTEL_METRICS_EXEMPLAR_FILTER trace_based
OTEL_RESOURCE_ATTRIBUTES service.instance.id=jayzjuvw
OTEL_SERVICE_NAME app
Expected Behavior
- My resource should be running
- If aspire failed to properly link up the process, (e.g.
received IDE run session notification with empty session ID, it should have been marked FailedToStart
Steps To Reproduce
- Open VS Code
- Run the rust sample from this repo w/out debugging
Exceptions (if any)
No response
Aspire doctor output
Aspire Environment Check
========================
Aspire
✅ Aspire CLI version 13.5.1 (channel: stable)
✅ Developer Control Plane (DCP) connection health checks succeeded
AppHost
✅ AppHost version 13.5.1 (apphost.rs)
Container Runtime
✅ Docker v29.7.2: running (auto-detected (default)) ← active
Environment
✅ Operating system: Windows 10.0.26100.0
✅ HTTPS development certificate is trusted
Development Tools
✅ Aspire extension for VS Code is installed
Summary: 7 passed, 0 warnings, 0 failed
Aspire CLI Installations
========================
╭───────────────────────────────────────────┬───────────────────────────────────────────┬──────────┬────────┬─────────────╮
│ Path │ Version │ Channel │ Route │ PATH status │
├───────────────────────────────────────────┼───────────────────────────────────────────┼──────────┼────────┼─────────────┤
│ C:\Users\alexanderc\.aspire\bin\aspire.ex │ 13.5.1+69db530a4816698cf1d5fa4557933e0ac4 │ stable │ script │ active │
│ e (current) │ f127c6 │ │ │ │
│ C:\Users\alexanderc\.aspire\dogfood\pr-18 │ 13.5.0-pr.18906.g90007b1b │ pr-18906 │ pr │ not on PATH │
│ 906\bin\aspire.exe │ │ │ │ │
╰───────────────────────────────────────────┴───────────────────────────────────────────┴──────────┴────────┴─────────────
Anything else?
Is there an existing issue for this?
Describe the bug
This particular issue repos fairly reliably when you run the app host w/out debugging, but I'm not certain that it's exclusive to running without debugging.
Process is disconnected from Aspire
Aspire claims that process is running, but I see no console output from it in aspire. Also, aspire thinkis the process id is
0, which is interesting...Copilot also found the following in the logs
If I look in VS Code, VS code seems to be spawning this process into a new terminal window

So the process is being created. Just not being fully linked up with DCP
DCP Proxy doesn't work
VS Code output suggests that the process is actually running
And if you hit that endpoint directly, you get a response.
But if you try to access it through the DCP proxy, it hangs. (And hence the rust app ends up in an unhealthy state).
Disconnected process doesn't get killed
If I stop the apphost process, the process in this terminal window doesn't get killed along with it, so continues running.
Even more problematic, if you
ctrl+cthe process and then try to use the terminal as a regular window,aspire rundoesn't work.OTLP doesn't work
When starting this project without debugging, OTLP doesn't work. It seems that the OTLP endpoint is wrong. The Aspire dashboard thinkis it's
https://localhost:50497. But hte process think's its on port 4318.Expected Behavior
received IDE run session notification with empty session ID, it should have been markedFailedToStartSteps To Reproduce
Exceptions (if any)
No response
Aspire doctor output
Anything else?