Series
What's new in Aspire 13.3
-
Part 1
Stop alt-tabbing to DevTools: WithBrowserLogs makes Chromium an Aspire resource
Aspire 13.3 introduces WithBrowserLogs, an extension that attaches a tracked Chromium browser to an endpoint-capable resource. Console logs and network activity stream back into the Aspire dashboard alongside your backend traces. For anyone debugging a frontend that talks to a distributed backend, this is the hop you've been making manually for years.
-
Part 2
Aspire's dashboard keeps a record: notification center and markdown messages
Aspire 13.3 adds a notification center to the dashboard: a bell-icon panel that catches every command response with a markdown body and a clickable "View response" entry. It is small, it is dev-loop sized, and it is the thing that finally makes resource commands worth writing for your local AppHost instead of just for ops.
-
Part 3
`aspire init` is no longer one-size-fits-all. The aspireify skill and your coding agent tailor the AppHost to your repo.
Aspire 13.3 ships aspire init with most of its detection-and-scaffolding code stripped out. What used to be deterministic file generation is now a handover: init drops a minimal skeleton, then a one-time skill called aspireify drives a coding agent through the wiring that needs to actually read your repo. I ran that handover six times across three Claude models and two un-aspirified eval apps to see where the skill earns its keep, and where it still leans on the model.