Tracking: open VS Code extension issues with no active PR

[adamint]

Tracking the open VS Code extension work that does not yet have a non-draft implementation PR. Draft PRs stay in this queue until they are ready for review, and a PR that only mentions an issue as a follow-up does not count as its implementation.

Snapshot - 2026-08-08 14:47 UTC

18 issues remain in the no-non-draft-PR queue - down 5 (22%) from the August 5 baseline and down 4 (18%) from the July 24 baseline. There are 22 tracked open product issues, down 1 (4%) since August 5 and unchanged since July 24. Every remaining tracked issue has the canonical area-vscode-extension label.

Four issues have active non-draft implementation PRs. Thirteen queued issues are covered by 12 open draft PRs, and five have no implementation PR at all. That means 17 of 22 open product issues (77%) have implementation work, compared with one of 23 (4%) on August 5. All four non-draft implementation PRs and 11 of the 12 distinct draft implementation PRs are CI-green. #19127 is the only draft still red. Three queued issues are assigned, 15 are unassigned, and four queued issues are in the 13.5 milestone.

Since the 13:44 UTC snapshot:

• All 22 tracked issue states, the queue, implementation coverage, referenced PR states, and the label sweep are unchanged.
• No issue was filed after aspire add / integration search over-filters in polyglot hosts: zero compatible integrations returned in a TypeScript AppHost #19161.
• All four non-draft implementation PRs and 11 of the 12 distinct draft implementation PRs remain CI-green.
• Run VS Code extension E2E tests on a current VS Code #19127 remains the only red draft, with the same Linux extension bootstrap and Windows extension unit-test failures plus the two aggregate result checks.

Snapshot	Tracked open issues	No non-draft PR	Draft implementation work	No implementation PR
Now	22	18	13	5
August 5 baseline	23	23	1	22
July 24 baseline (~2 weeks)	22	22	1	21

These are fixed baselines rather than rolling cutoffs, so the comparison does not move when an older closure crosses the exact 48-hour boundary. Since August 5, eight tracked issues closed and seven were filed. Since July 24, 16 closed and 16 were filed. The raw queue is down 22% from August 5, while the number of queued issues with no implementation work is down from 22 to 5 (77%). Over two weeks, the raw queue is down 18% and the no-implementation inventory is down from 21 to 5 (76%).

Recent label sweep

I rechecked all 98 open issues filed from July 24 through this snapshot. Thirty-one lack an area label, and #19121 has both area-integrations and needs-area-label. No label change was needed. #19151 is the newest extension match and already has area-vscode-extension; there are also no recent issues using the older area-vscode or area-extension labels instead of the canonical label.

• The newest issues, Playwright CLI provenance verification fails (AttestationFetchFailed) and blocks aspire new when registry.npmjs.org is unreachable #19159 and aspire add / integration search over-filters in polyglot hosts: zero compatible integrations returned in a TypeScript AppHost #19161, are CLI behavior, not extension behavior.
• [CI Failure] AzureBicepResourceScopeTests.cs fails to compile against main (stale PR branch, unrelated to PR changes) #19149 and [CI Failure] Flaky: AppHostServerSessionTests.GetRpcClientAsync_WhenServerExitsBeforeSocketIsAvailable_FailsWithoutWaitingForConnectionTimeout takes longer than expected on Windows runner #19150 are CI failures in Azure Bicep compilation and Aspire CLI RPC timing, not extension issues.
• [CI Failure] Flaky: JsonRpcAuthenticationTests.FailedAuthentication_ClosesConnection_AndPreventsFurtherCalls times out connecting to test RPC server on Windows #19143 and [CI Failure] Windows test host process crashes with exit code 0xC0000142 after tests complete #19144 are Windows test-infrastructure failures.
• addAzureAppServiceEnvironment always produces ACR #19121 already has area-integrations; its extra needs-area-label state should not result in a second area label.
• [aw] Failed jobs: PR Documentation Check #19115, [aw] Failed jobs: PR Documentation Check #19113, [aw] Failed jobs: PR Documentation Check #19112, and the other [aw] issues are PR Documentation Check workflow failures.
• Not allowing underscores in resource names (ASPIRE006 warning) conflicts with POSIX environment variable restrictions #19063 is resource-name and environment-variable behavior in the hosting model.
• [AspireE2E]Build aspire project with warning "warning NU1903: Package 'Microsoft.OpenApi' 2.0.0 has a known high severity vulnerability" #18919 is a stale package version in the generated Aspire Starter template.
• The other recent extension matches - Debug console dedup only understands the default SimpleConsoleFormatter shape #19140, Harden Azure Functions VS Code launch lifecycle and E2E coverage #19138, WinUI3 (unpackaged) resource crashes with 0xC000027B in Microsoft.UI.Xaml.dll when debugged concurrently with the AppHost via the VS Code Aspire extension #19091, Launching aspire from different vscode launch configurations (using the extension) overrides the aspire.config.json file #19080, [main] Undismissable Extension Build notifications block copilot #19036, [main] VS Code (CLI?) incorrectly reports "The --apphost option specified a project that does not exist." if an apphost fails to build #19035, Add E2E test coverage for per-language debugger launch flows in the VS Code extension #18957, Expose the resolved environment variables to the WithDebugSupport launch configuration callback #18956, Expose a project resource child PID or evaluated AssemblyName for debugger attach #18937, WithDebugSupport argument rewriting is order-sensitive and mutates the app model #18929, and Upgrade to TS7 (tsgo) #18905 - already have area-vscode-extension.

Active non-draft PRs - out of this queue

Issue	Issue status	PR	Current PR status
#18929	Open, Karol Zadora-Przylecki (@karolz-ms), 13.5	#18999	Open, non-draft, mergeable, review-required, and CI-green.
#18956	Open, Adam Ratzman (@adamint), 13.5	#19077	Open, non-draft, mergeable, review-required, and CI-green.
#19035	Open, unassigned, 13.5	#19082	Open, non-draft, mergeable, review-required, and CI-green. It preserves the known-but-unbuildable AppHost result and reports the actual build failure.
#19080	Open, Adam Ratzman (@adamint), 13.5	#19126	Open, non-draft, mergeable, review-required, and CI-green. It keeps launch-configuration targets out of the workspace default.

Merging these four PRs would reduce total tracked open work from 22 to 18. They already have non-draft implementation PRs, so their merge does not change this queue.

Draft implementation work - still in this queue

There are 13 issue lanes here but 12 distinct PRs because #18602 now covers both debugger issues.

Issue	Issue status	Draft PR	Current PR status and remaining gate
#19036	Open, Adam Ratzman (@adamint), 13.5	#19124	Mergeable, review-required, and CI-green. It makes build/connect/dashboard notifications hideable without stopping the AppHost and makes discovery cancellable.
#18374	Open, unassigned, 13.5	#19127	Mergeable and review-required, but CI is red on Linux extension bootstrap validation and Windows extension unit tests, plus the aggregate result checks. It replaces the hardcoded old VS Code version with ExTester's current max version.
#15426	Open, unassigned, 13.5	#19125	Mergeable, review-required, and CI-green. It emits sessionTerminated when resources are stopped through DELETE /run_session.
#17845	Open, unassigned, Backlog	#19131	Mergeable, review-required, and CI-green. It adds the missing-language-debug-extension install hint.
#18047	Open, unassigned, Backlog	#19129	Mergeable, review-required, and CI-green. It removes duplicate AppHost output and preserves warning/error categories in the VS Code debug console, while explicitly leaving the non-default formatter contract to #19140.
#15850	Open, unassigned, Backlog	#19132	Mergeable, review-required, and CI-green. The PR versions the build-ownership handshake so any new side builds exactly once.
#18694	Open, unassigned, Backlog	#19128	Mergeable, review-required, and CI-green. It adds the Marketplace version check to aspire doctor, with bounded network failure handling and targeted coverage.
#18905	Open, unassigned, Backlog	#19130	Partial draft, mergeable, review-required, and CI-green. It fixes the broken TypeScript 6 scaffold, CI routing, lockfile feed drift, and extension typecheck gaps left by the TS7 bridge, but still marks follow-up work expected.
#18957	Open, Adam Ratzman (@adamint), Backlog	#19133	Partial draft, mergeable, review-required, and CI-green. It adds the real debugger E2E harness and Node proof, while Python, Go, Rust, MAUI, and Azure Functions remain follow-up work. Related split drafts #19145, #19146, and #19147 are all green. Related non-draft #18906 is also green, but it is the Rust integration that exposed this gap rather than an implementation of the E2E matrix issue.
#18324	Open, unassigned, Backlog	#19134	Mergeable, review-required, and CI-green. It adds guarded VS Code AppHost start/stop language-model tools with unit and E2E coverage; the security-sensitive boundary still needs normal review.
#18937	Open, unassigned, Backlog	#18602	Mergeable, review-required, and CI-green. The standalone draft #19136 was closed unmerged after its assembly-name commits were consolidated into this branch.
#18538	Open, Adam Ratzman (@adamint), Backlog	#18602	Mergeable, review-required, and CI-green. The same consolidated draft adds the CoreCLR attach resource action and consumes the evaluated assembly-name contract for reliable process matching.
#15575	Open, unassigned, Backlog	#19135	Partial issue coverage; the draft is mergeable, review-required, and CI-green. It implements the dashboard-inside-tests direction, but does not change extension/ and explicitly leaves the editor-side half open.

Other open extension work does not change the tracked issue counts:

• Draft Enable C# Dev Kit Hot Reload for Aspire .NET resources #19067 is separate extension work with no linked tracked product issue; it is CI-green.
• Draft Re-enable VS Code extension E2E tests in CI #19142 is related to VS Code extension E2E azure-functions shard times out waiting for e2e-functions #19151, but intentionally skips the failing Linux Azure Functions shard instead of fixing the root cause; it is CI-green.
• Drafts Fix browser debug targets, empty webRoot, and resource stop ordering #19145, Assert every VS Code extension E2E spec has a CI matrix row #19146, and Keep the E2E state file bridge out of production extension builds #19147 were split from Cover per-language debugger launch flows in extension E2E #19133. They cover browser/debug stop fixes, E2E matrix completeness, and excluding the E2E state bridge from production builds. All three are CI-green.
• Draft Stop the Aspire CLI and own its RPC connections during extension deactivation #19152 was split from Make Aspire extension activity notifications dismissible #19124 and covers extension deactivation/RPC lifecycle rather than the notification issue; it is CI-green.
• Draft Expose the evaluated project assembly name for debugger attach #19136 was closed unmerged after its assembly-name commits were folded into Add VS Code attach debugger resource action #18602.

No implementation PR

• VS Code extension E2E azure-functions shard times out waiting for e2e-functions #19151 - open, unassigned, no milestone, no implementation PR. Related green drafts Re-enable VS Code extension E2E tests in CI #19142 and Cover per-language debugger launch flows in extension E2E #19133 reference the failure, but both leave the Linux Azure Functions shard skipped rather than fixing the root cause. The next useful step is to determine why the AppHost starts successfully while the extension state never receives resources, then remove the skip.
• Debug console dedup only understands the default SimpleConsoleFormatter shape #19140 - open, unassigned, Backlog, no implementation PR. Related draft Deduplicate and colorize AppHost logs in the VS Code debug console #19129 is CI-green, but it explicitly defers this new AppHost/CLI/extension wire contract; the cross-reference is not implementation. The proposed fix is to report the effective ConsoleFormatterOptions instead of making the extension guess the log shape.
• Harden Azure Functions VS Code launch lifecycle and E2E coverage #19138 - open, unassigned, no milestone, no implementation PR. Six lifecycle/PID/shell gaps are reproduced against the real callback and the .NET 8 E2E dependency is config-confirmed. The next step is the focused lifecycle/PID/shell fix plus the real shell-sensitive Azure Functions E2E.
• WinUI3 (unpackaged) resource crashes with 0xC000027B in Microsoft.UI.Xaml.dll when debugged concurrently with the AppHost via the VS Code Aspire extension #19091 - open, unassigned, 13.5, no implementation PR; Windows repro confirmed. A minimal unpackaged WinUI 3 resource with the default bin/obj layout reproduced 3/3 on Windows ARM64, while direct dotnet run and aspire run stayed healthy. Each debug session had its own vsdbg-ui.exe, so the next useful step is root-causing the concurrent-debug path and settling whether the fix belongs in the extension, C# debugger, or WinAppSDK.
• Remove AI assistant references from VS Code extension #18751 - open, unassigned, Backlog, no implementation PR. This is waiting on the compatibility decision: a new extension can still run against an older AppHost that recognizes the removed AI-assistant environment/telemetry keys.

Recently closed

• [WebToolsE2E] Using VS Code C# Dev Kit, there is no IntelliSense for JSON editing when configuring Aspire integrations #8032 - closed after no user signal for over a year. The cross-repo draft Provide appsettings.json IntelliSense from JsonSchemaSegment MSBuild items dotnet/vscode-csharp#9652 was also closed unmerged after the SchemaStore alternative was raised.
• VS Code does not start Azure Functions with HTTPS #18872 - closed by merged Fix Azure Functions HTTPS launches in VS Code #19001. The Azure Functions launch support shipped, and Harden Azure Functions VS Code launch lifecycle and E2E coverage #19138 now tracks the post-merge correctness and coverage follow-up.
• VS Code: Code Lens shows up in weird places Take 2 #16045 - closed as completed, no PR needed. The CodeLens placement bug reproduces on the reported 1.0.7 extension but not on Marketplace 1.16.0 or current source.

The other five tracked issues closed since the August 5 baseline are #19004, #18911, #18054, #17976, and #17941.

Path to zero

There are three useful zeroes to track:

1. Queue zero: review and promote the 12 distinct draft PRs covering 13 issues. Eleven are CI-green now (Add VS Code attach debugger resource action #18602, Make Aspire extension activity notifications dismissible #19124, Emit DCP session termination when stopping resources #19125, Detect an outdated Aspire VS Code extension in aspire doctor #19128, Deduplicate and colorize AppHost logs in the VS Code debug console #19129, Close the gaps the TypeScript 7 bridge left behind #19130, Show install hint when a language debug extension is missing #19131, Version the AppHost build-ownership capability so no launch runs stale output #19132, Cover per-language debugger launch flows in extension E2E #19133, Add VS Code AppHost start/stop tools so agents use the editor instead of the CLI #19134, and Support running the Aspire dashboard from tests #19135). Run VS Code extension E2E tests on a current VS Code #19127 is the only red lane and still needs its Linux bootstrap and Windows unit-test failures investigated. Promoting valid implementations takes the queue from 18 to 5.
2. No-implementation zero: finish the five untouched lanes. VS Code extension E2E azure-functions shard times out waiting for e2e-functions #19151 needs the Azure Functions E2E root cause, Debug console dedup only understands the default SimpleConsoleFormatter shape #19140 needs the formatter-options wire contract, Harden Azure Functions VS Code launch lifecycle and E2E coverage #19138 has concrete reproduced fixes ready to implement, WinUI3 (unpackaged) resource crashes with 0xC000027B in Microsoft.UI.Xaml.dll when debugged concurrently with the AppHost via the VS Code Aspire extension #19091 needs root cause and ownership after the confirmed Windows repro, and Remove AI assistant references from VS Code extension #18751 needs the compatibility decision. Opening non-draft implementation lanes, or moving confirmed non-extension scope out, takes the queue from 5 to zero.
3. Open-issue zero: review, merge, and close the implementation work. All four active non-draft PRs are green. Eleven of the 12 distinct draft PRs are also green, leaving Run VS Code extension E2E tests on a current VS Code #19127 as the only CI repair before the draft fleet is entirely at the review/promotion gate. Close the gaps the TypeScript 7 bridge left behind #19130, Cover per-language debugger launch flows in extension E2E #19133, and Support running the Aspire dashboard from tests #19135 are partial issue coverage, so their remaining TypeScript/debugger/testing integration work still needs tracking after the current drafts are ready.

The queue and PR states are unchanged since 13:44 UTC. Compared with August 5, the raw queue is down 22% and implementation coverage moved from 4% to 77%; compared with July 24, the queue is down 18% and the no-implementation inventory moved from 21 to 5. The main bottleneck is review and promotion rather than missing code. Getting the 12 drafts through that gate produces the next large drop; the remaining five are the actual unstarted/root-cause inventory.

I'll keep this current as issues close, PRs come out of draft, or new extension reports arrive. If you take one, please assign yourself and link the PR.