Microsoft released Aspire 13.2 on March 23, 2026, a feature-heavy update that reshapes the Aspire command line around AI coding agents. The old aspire mcp command became aspire agent, which now sets up skill files and an optional MCP server so assistants such as GitHub Copilot and Claude Code can inspect a running distributed application. The release also previews AppHosts written in TypeScript, adds a telemetry HTTP API to the dashboard and replaces the Azure AI Foundry integration with a broader Microsoft Foundry integration that can publish hosted agents.

Key Facts#

  • Release: Aspire 13.2.0 was published on March 23, 2026, on GitHub and NuGet.
  • Agent CLI: aspire mcp was renamed to aspire agent. aspire agent init configures skill files and MCP, and aspire agent mcp starts only the MCP server.
  • Supported assistants: Aspire's documentation lists VS Code with GitHub Copilot, Copilot CLI, Claude Code and OpenCode.
  • New commands: aspire start, aspire stop and aspire ps for detached mode, plus aspire describe, aspire doctor, aspire secret and aspire docs.
  • TypeScript AppHost: a preview that uses the same app model through createBuilder(), running as a guest process that talks to the .NET orchestration host over JSON-RPC.
  • Dashboard API: opt-in endpoints under /api/telemetry for resources, spans and logs, with NDJSON streaming.
  • Foundry: the Aspire.Hosting.Azure.AIFoundry package was replaced by Aspire.Hosting.Foundry, with support for model deployments and hosted agents.

What Happened#

The headline change is conceptual: Aspire now treats AI coding agents as first-class users of its tooling. Running aspire agent init adds skill files that teach an agent how to use Aspire CLI workflows, route tasks to focused skills and call companion tools, and it can configure the Aspire MCP server. That server, which uses the stdio transport, gives an agent runtime access to resource status, logs, traces and commands. In the documentation's words, the goal is for agents to diagnose local failures and verify fixes with runtime evidence rather than guessing from source code alone.

Several new commands support that workflow. Detached mode lets a developer or an agent start an AppHost in the background and manage it later:

Bash
aspire agent init   # add skill files and optional MCP configuration
aspire start        # run the AppHost in detached mode
aspire describe     # resource details, as shown in the dashboard
aspire stop         # stop the background AppHost

aspire describe exposes the same resource information as the dashboard, aspire doctor checks certificates, container runtimes, the .NET SDK and WSL2 configuration, and aspire docs brings the aspire.dev documentation into the terminal. On the dashboard side, a new HTTP API under /api/telemetry lists resources and queries spans and logs, and ?follow=true streams results as NDJSON. The API is disabled by default and must be enabled with the ASPIRE_DASHBOARD_API_ENABLED setting.

The TypeScript AppHost preview extends Aspire's polyglot push. Developers can describe resources with createBuilder(), addRedis and addProject in TypeScript while Aspire's .NET host still performs orchestration. The Foundry integration, meanwhile, lets a C# AppHost provision a Foundry project and model deployment and publish an agent service as a hosted agent:

C#
var builder = DistributedApplication.CreateBuilder(args);

var foundry = builder.AddFoundry("foundry");
var project = foundry.AddProject("agents");
var chat = project.AddModelDeployment("chat", FoundryModel.OpenAI.Gpt5Mini);

builder.AddPythonApp("agent", "..\\agent", "main:app")
    .PublishAsHostedAgent(project);

builder.Build().Run();

Other additions include a VS Code extension with an Activity Bar panel and health CodeLens, bulk telemetry export and import in the dashboard, new integrations for Azure Data Lake Storage, MongoDB with EF Core, Bun and Certbot, Docker Compose publishing, and an Aspire.Hosting.Azure.Network integration for virtual networks, NAT gateways, network security groups and private endpoints.

Background#

Aspire 13, released on November 11, 2025, alongside .NET 10, dropped the ".NET" prefix, moved to aspire.dev and made Python and JavaScript first-class citizens next to .NET. It also introduced aspire do pipelines, container-based builds and an MCP server that let AI assistants query resources and telemetry. Aspire 13.1 followed in December 2025 with CLI-based MCP support for AI agents, dashboard improvements and TLS termination.

Version 13.2 builds on that foundation with a clear thesis: the local development loop for distributed apps increasingly includes an AI agent, and that agent needs the same visibility into running services that a human gets from the dashboard.

Why It Matters for Developers#

Coding agents are good at editing code and weak at understanding what happens when that code runs across several services, containers and databases. Aspire already collects exactly that information through OpenTelemetry. Exposing it through MCP, skills and a CLI that an agent can drive closes the loop: an agent can start the app, reproduce a failure, read the relevant traces and logs, apply a fix and confirm that the error is gone. For .NET teams that already use Aspire, this is a practical way to make agents useful on real distributed systems rather than toy repositories. Our Aspire guide covers the AppHost model, and OpenTelemetry in .NET explains the telemetry the agent will be reading.

Treat the new capabilities with the same care as any other privileged access. The MCP server can execute resource commands, and the telemetry API can expose sensitive log data, which is presumably why the API is opt-in. Keep these features on developer machines unless you have deliberately designed for more.

The upgrade itself needs attention. Aspire 13.2 includes several breaking changes: service discovery environment variables now use the endpoint scheme instead of its name, configuration moves into a unified aspire.config.json, connection property suffixes change from Database and Model to DatabaseName and ModelName, WithSecretBuildArg becomes WithBuildSecret, and Foundry users must switch packages. For the Foundry side of the stack, see our guide to Azure OpenAI and AI Foundry for .NET developers, and for using agents effectively in day-to-day work, see AI-assisted .NET development.

What's Next#

Aspire has kept a fast cadence since 13.2. Version 13.3 arrived on May 7, 2026, with an Aspireify skill for agent-assisted onboarding of existing apps. Version 13.4 followed on June 1, 2026, making the TypeScript AppHost generally available and adding typed resource commands, server-side log and telemetry search in the CLI and more mature Kubernetes and AKS deployment. Version 13.5, released on August 18, 2026, refreshed the dashboard and aspire.dev and expanded the Interaction Service. The direction is consistent: Aspire is becoming the runtime control plane that both developers and their AI agents use to build and debug distributed applications.

Sources#