From 2e8a9a725e00bc1e43fb1addd00669c0913e5082 Mon Sep 17 00:00:00 2001
From: "aspire-repo-bot[bot]"
 <268009190+aspire-repo-bot[bot]@users.noreply.github.com>
Date: Tue, 11 Aug 2026 14:15:12 +0000
Subject: [PATCH 1/5] docs: document project serverReadyAction override in VS
 Code extension

---
 .../docs/get-started/aspire-vscode-extension.mdx  | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx b/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx
index 4c2fd2d72..bde997e99 100644
--- a/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx
+++ b/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx
@@ -131,6 +131,21 @@ All of these commands are debuggable; you can step into custom publishers and de
 
 The `debuggers` property forwards configuration to specific debuggers. Recognized keys are: `apphost`, `project` (C#/.NET), `node`, `python`, `browser`, and `azure-functions`.
 
+For `project`, the extension normally generates a `serverReadyAction` from the project's `launchSettings.json` to automatically open the browser when the server is ready. Set `project.serverReadyAction` explicitly to override this generated default with your own action and pattern:
+
+```json title=".vscode/launch.json — override the generated serverReadyAction"
+{
+  "debuggers": {
+    "project": {
+      "serverReadyAction": {
+        "action": "openIntegratedBrowser",
+        "pattern": "Now listening on:\\s+\\[?(https?://[^\\]\\s]+)"
+      }
+    }
+  }
+}
+```
+
 Finally, you can specify `env` and `args` to set environment variables and command-line arguments for the AppHost process.
 
 ```json title=".vscode/launch.json — deploy with debugger settings, env, and args"

From 61065d84a66b790825b76392480e3b36417a84de Mon Sep 17 00:00:00 2001
From: Ella Hathaway <ellahathaway@microsoft.com>
Date: Mon, 17 Aug 2026 16:23:15 -0700
Subject: [PATCH 2/5] docs: clarify serverReadyAction setting path

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
---
 .../src/content/docs/get-started/aspire-vscode-extension.mdx  | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx b/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx
index bde997e99..b75a4aba5 100644
--- a/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx
+++ b/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx
@@ -131,9 +131,9 @@ All of these commands are debuggable; you can step into custom publishers and de
 
 The `debuggers` property forwards configuration to specific debuggers. Recognized keys are: `apphost`, `project` (C#/.NET), `node`, `python`, `browser`, and `azure-functions`.
 
-For `project`, the extension normally generates a `serverReadyAction` from the project's `launchSettings.json` to automatically open the browser when the server is ready. Set `project.serverReadyAction` explicitly to override this generated default with your own action and pattern:
+For `project`, the extension normally generates a `serverReadyAction` from the project's `launchSettings.json` to automatically open the browser when the server is ready. Set `debuggers.project.serverReadyAction` explicitly to override this generated default with your own action and pattern:
 
-```json title=".vscode/launch.json — override the generated serverReadyAction"
+```json title=".vscode/launch.json — override debuggers.project.serverReadyAction"
 {
   "debuggers": {
     "project": {

From 6a5a19445ce59383dea8d4e34a286e8719b4321e Mon Sep 17 00:00:00 2001
From: Ella Hathaway <ellahathaway@microsoft.com>
Date: Mon, 17 Aug 2026 16:31:53 -0700
Subject: [PATCH 3/5] docs: note AppHost serverReadyAction behavior

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
---
 .../src/content/docs/get-started/aspire-vscode-extension.mdx  | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx b/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx
index b75a4aba5..7b2223138 100644
--- a/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx
+++ b/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx
@@ -133,6 +133,10 @@ The `debuggers` property forwards configuration to specific debuggers. Recognize
 
 For `project`, the extension normally generates a `serverReadyAction` from the project's `launchSettings.json` to automatically open the browser when the server is ready. Set `debuggers.project.serverReadyAction` explicitly to override this generated default with your own action and pattern:
 
+:::note[AppHost behavior]
+A .NET AppHost also uses the `project` debugger, so `debuggers.project.serverReadyAction` applies to both the AppHost and .NET project resources. Because `project` settings are applied after `apphost` settings, matching AppHost output can also trigger this action.
+:::
+
 ```json title=".vscode/launch.json — override debuggers.project.serverReadyAction"
 {
   "debuggers": {

From 98c395d5812f1369da089b90fb056262950252b8 Mon Sep 17 00:00:00 2001
From: Ella Hathaway <ellahathaway@microsoft.com>
Date: Mon, 17 Aug 2026 16:34:06 -0700
Subject: [PATCH 4/5] docs: preserve IPv6 server-ready URLs

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
---
 .../src/content/docs/get-started/aspire-vscode-extension.mdx    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx b/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx
index 7b2223138..7d110d859 100644
--- a/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx
+++ b/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx
@@ -143,7 +143,7 @@ A .NET AppHost also uses the `project` debugger, so `debuggers.project.serverRea
     "project": {
       "serverReadyAction": {
         "action": "openIntegratedBrowser",
-        "pattern": "Now listening on:\\s+\\[?(https?://[^\\]\\s]+)"
+        "pattern": "\\bNow listening on:\\s+(https?://\\S+)"
       }
     }
   }

From 4a97126da745ea67ffa5ac191beb37db21b2a372 Mon Sep 17 00:00:00 2001
From: Ella Hathaway <ellahathaway@microsoft.com>
Date: Mon, 17 Aug 2026 16:39:28 -0700
Subject: [PATCH 5/5] docs: clarify AppHost server-ready precedence

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
---
 .../src/content/docs/get-started/aspire-vscode-extension.mdx    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx b/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx
index 7d110d859..35496a61b 100644
--- a/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx
+++ b/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx
@@ -134,7 +134,7 @@ The `debuggers` property forwards configuration to specific debuggers. Recognize
 For `project`, the extension normally generates a `serverReadyAction` from the project's `launchSettings.json` to automatically open the browser when the server is ready. Set `debuggers.project.serverReadyAction` explicitly to override this generated default with your own action and pattern:
 
 :::note[AppHost behavior]
-A .NET AppHost also uses the `project` debugger, so `debuggers.project.serverReadyAction` applies to both the AppHost and .NET project resources. Because `project` settings are applied after `apphost` settings, matching AppHost output can also trigger this action.
+A .NET AppHost also uses the `project` debugger, so `debuggers.project.serverReadyAction` is included in its debug configuration. If you set both `debuggers.apphost.serverReadyAction` and `debuggers.project.serverReadyAction`, the `project` value takes precedence.
 :::
 
 ```json title=".vscode/launch.json — override debuggers.project.serverReadyAction"