Microsoft released Aspire 13.5 last week, an update that overhauls the dashboard's visual design, expands how the AppHost communicates with developers, and introduces more deployment flexibility. According to the release, previous Aspire 13 efforts centered on widening the tool's reach across programming languages, deployment destinations, and coding agents, including full TypeScript AppHost compatibility, fresh command-line capabilities, and integration with Kubernetes and Docker Compose. This version shifts focus to refresh the interface and deliver several frequently requested quality-of-life improvements.
The dashboard received what the development team calls "a new coat of paint" while keeping the layout and feature set unchanged, ensuring everything stays where users already expect it. Microsoft reports it verified contrast and accessibility throughout the refreshed interface so the redesign works for everyone. The dashboard also gained smaller but popular enhancements, including search in console logs that ignores case, filtering of logs and traces by timestamp or precise numeric comparison, smoother reconnection when the resource-service link fails, and clearer health-check failure messages that replace raw exception stacks. The Interaction Service, which allows a resource command to request input or display a notification where the developer is already working, now handles file imports—a command can launch a file picker that accepts JSON or YAML, enforce a size cap, and provide the AppHost a stream to read, eliminating the previous workaround of dropping a file in a designated directory before executing a script. Longer operations can also show a progress dialog with optional cancellation, and commands can define named arguments that surface as input controls in the dashboard and as options in the command-line interface.
According to the release, these elements give integration authors everything needed for a complete setup or import workflow. Aspire 13.5 also embeds a terminal directly in the dashboard—adding WithTerminal() grants a resource an interactive terminal session, helpful for shells, REPLs, and other tools that expect genuine input and output, and users can type into it, switch between replicas, and return to standard console logs without halting the session, with multiple viewers able to attach to the same process simultaneously. The feature and its associated commands are flagged as experimental in this version. Another significant shift is that TypeScript AppHosts are now generally available and no longer need an experimental opt-in, and with that milestone reached, the Interaction Service, file uploads, and progress dialogs operate identically from both C# and TypeScript. The release also notes that persistent volumes for Kubernetes workloads can now be modeled by applications, configuring storage class, capacity, and access mode before binding the volume to a project or container, with Aspire then emitting the persistent volume claim and rendering the workload as specified.
On the deployment side, new methods let an application reference existing Azure resources across resource groups, subscriptions, and tenants, keeping environment specifics out of the AppHost source while references and deployment intent remain in the model. Separately, the Aspire command-line interface can now be installed and updated through package managers including Homebrew, WinGet, npm, Nix, mise, and NuGet, and the Visual Studio Code extension was rebranded to Aspire and gained several new capabilities, including opening the dashboard in a side panel, Bun and MAUI debugging support, and resource commands displayed directly in the tree view. The release also carries breaking changes, including the renaming of the ServiceProvider property to Services and the deprecation of the GitHub Models integration, while the dashboard's AI Assistant chat was removed in this version. For organizations already running Aspire at scale, the addition of terminal access and persistent volume modeling lowers the friction of managing complex distributed workloads, while the TypeScript graduation signals Microsoft's commitment to cross-language tooling beyond its .NET core. Teams evaluating whether to standardize on Aspire will need to weigh the convenience of unified orchestration against the operational overhead of adopting another abstraction layer in their deployment pipeline.