Update dashboard overview AI-debugging section for MCP + external agents - #1184
Update dashboard overview AI-debugging section for MCP + external agents#1184David Pine (IEvangelist) with Copilot wants to merge 4 commits into
Conversation
Co-authored-by: IEvangelist <7679720+IEvangelist@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Updates the Aspire Dashboard overview documentation to reflect the current AI-debugging model by clarifying how external AI agents access dashboard telemetry via the Aspire MCP server, and by pointing readers to the dedicated agent workflow guide.
Changes:
- Added a new MCP server section explaining that dashboard telemetry can be exposed to external AI coding agents via the Aspire MCP server.
- Added a Using agents with the dashboard subsection linking to
/dashboard/ai-coding-agents/for end-to-end setup/examples. - Added a
TODO(screenshot)note intended to prompt adding an external-agent workflow screenshot.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| ### Using agents with the dashboard | ||
|
|
||
| Use AI coding agents with the dashboard by connecting your agent to Aspire CLI and MCP tools, then letting it query dashboard telemetry as part of debugging workflows. For setup and end-to-end examples, see [AI coding agents and the Aspire Dashboard](/dashboard/ai-coding-agents/). |
|
|
||
| The Aspire dashboard data can be exposed to external AI coding agents through the [Aspire MCP server](/get-started/aspire-mcp-server/). This gives agents access to resource status, structured logs, traces, and console output so they can investigate issues with the same telemetry data you see in the dashboard. | ||
|
|
||
| {/* TODO(screenshot): Before this docs update is shipped, add a screenshot that shows an external agent (for example, GitHub Copilot CLI) calling Aspire/MCP to fetch dashboard data and displaying reasoning/results. Do not use an in-dashboard Copilot chat UI screenshot. */} |
Adam Ratzman (adamint)
left a comment
There was a problem hiding this comment.
I found a few docs issues that should be addressed before merge: the page still contains a pre-ship screenshot TODO, the new heading implies the dashboard hosts the MCP server even though the CLI does, and the capability list does not distinguish AppHost-backed and standalone dashboard modes. The links resolve and the current MCP command surface otherwise matches the docs.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Clarify MCP startup, distinguish AppHost and dashboard-only tool access, and remove the screenshot TODO. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Frontend HTML artifact readyThe latest frontend build uploaded the This comment updates automatically when a new frontend build artifact is uploaded. |
The dashboard overview page no longer reflected the current AI debugging model: Copilot UI-in-dashboard content was removed, but the page still needed explicit agent guidance and a non-misleading screenshot path. This update keeps MCP server coverage, adds agent usage guidance, and removes dependence on outdated in-dashboard Copilot imagery.
Dashboard overview content refresh
## MCP serversection to clarify that dashboard telemetry is exposed to external AI agents via Aspire MCP.### Using agents with the dashboardsubsection with a direct link to/dashboard/ai-coding-agents/.Screenshot handling cleanup
TODO(screenshot)next to the MCP section to require a replacement image before shipping.Scope
src/frontend/src/content/docs/dashboard/overview.mdx