What problem does it solve? Managing a distributed Aspire application involves many CLI operations—starting resources, waiting for health, rebuilding single services, and reading logs or traces—and doing them wrong (like restarting the whole AppHost for one change) wastes time and breaks state. ## Core Features & Use Cases - Resource Lifecycle Control: Start, stop, restart, rebuild, and wait on individual AppHost resources with commands like aspire start --isolated and aspire resource <name> rebuild. - Observability & Debugging: Inspect resource status, console logs, structured OpenTelemetry logs, and distributed traces via aspire describe, aspire otel logs, and aspire otel traces. - Integrations & MCP Tools: Add integrations with aspire add, search official docs with aspire docs search, and invoke resource-exposed MCP tools via aspire mcp call. - Use Case: While working in a git worktree, run aspire start --isolated, wait for your API with aspire wait myapi, then rebuild only the changed .NET service instead of restarting the entire AppHost. ## Quick Start Ask the assistant to start the Aspire AppHost in isolated mode and wait until the API resource is healthy before making changes.
