Skip to content

Update dashboard overview AI-debugging section for MCP + external agents - #1184

Open
David Pine (IEvangelist) with Copilot wants to merge 4 commits into
mainfrom
copilot/improve-ai-powered-debugging
Open

Update dashboard overview AI-debugging section for MCP + external agents#1184
David Pine (IEvangelist) with Copilot wants to merge 4 commits into
mainfrom
copilot/improve-ai-powered-debugging

Conversation

Copilot AI commented Jun 2, 2026

Copy link
Copy Markdown
Contributor

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

    • Added an ## MCP server section to clarify that dashboard telemetry is exposed to external AI agents via Aspire MCP.
    • Added a ### Using agents with the dashboard subsection with a direct link to /dashboard/ai-coding-agents/.
  • Screenshot handling cleanup

    • Added a clearly marked TODO(screenshot) next to the MCP section to require a replacement image before shipping.
    • The TODO explicitly requires an external agent workflow screenshot (e.g., Copilot CLI invoking Aspire/MCP) and disallows in-dashboard Copilot chat UI imagery.
  • Scope

    • Changes are limited to:
      • src/frontend/src/content/docs/dashboard/overview.mdx
    • No unrelated documentation or code paths were modified.
## MCP server

The Aspire dashboard data can be exposed to external AI coding agents through the [Aspire MCP server](/get-started/aspire-mcp-server/).

{/* TODO(screenshot): Before this docs update is shipped, add a screenshot that shows an external agent ... Do not use an in-dashboard Copilot chat UI screenshot. */}

### Using agents with the dashboard

...see [AI coding agents and the Aspire Dashboard](/dashboard/ai-coding-agents/).

Co-authored-by: IEvangelist <7679720+IEvangelist@users.noreply.github.com>
Copilot AI changed the title [WIP] Update dashboard overview page for AI-powered debugging Update dashboard overview AI-debugging section for MCP + external agents Jun 2, 2026
@IEvangelist
David Pine (IEvangelist) marked this pull request as ready for review June 30, 2026 08:38
Copilot AI review requested due to automatic review settings June 30, 2026 08:38

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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. */}
Comment thread src/frontend/src/content/docs/dashboard/overview.mdx Outdated
Comment thread src/frontend/src/content/docs/dashboard/overview.mdx Outdated
Comment thread src/frontend/src/content/docs/dashboard/overview.mdx Outdated

@adamint Adam Ratzman (adamint) left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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>
@aspire-repo-bot

Copy link
Copy Markdown
Contributor

Frontend HTML artifact ready

The latest frontend build uploaded the frontend-dist artifact for PR #1184. Use the VS Code button below to open this PR with GitHub Artifacts Explorer and browse the built HTML locally.

VS Code: Open PR #1184 artifacts

This comment updates automatically when a new frontend build artifact is uploaded.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve "AI-powered debugging" on dashboard page

4 participants