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"