aspire-orchestration

Manage Aspire AppHost lifecycle with start, stop, wait, and describe commands.

13|4|Updated Feb 8, 2025

Search Tags:#automation #recovery #lifecycle #orchestrator #aspire #resource-management #apphost

Ready to run

npx skills add https://github.com/jonathanpotts/aspire-nextjs-keycloak --skill aspire-orchestration-jonathanpotts

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aspire-orchestration
Source: https://github.com/jonathanpotts/aspire-nextjs-keycloak/tree/main/.agents/skills/aspire-orchestration
Command: npx skills add https://github.com/jonathanpotts/aspire-nextjs-keycloak --skill aspire-orchestration-jonathanpotts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manage the Aspire AppHost lifecycle and recover from file locks, port conflicts, and orphaned processes, ensuring a predictable, non-interactive runtime for AI agents.

Core Features & Use Cases

Lifecycle orchestration: start, stop, wait, describe, and resource-level commands for Aspire AppHost-based projects.
Safe recovery workflows: detect and recover from common failures (e.g., MSB3491, CS2012, port conflicts) without manual intervention.
Guardrails and non-interactive operation: enforce safe, agent-friendly operation with consistent behavior across environments.

Quick Start

Start the Aspire AppHost with aspire start and monitor resources with aspire ps.

Frequently Asked Questions about aspire-orchestration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate Aspire AppHost lifecycle management for start and stop operations?▼

Aspire AppHost lifecycle management is automated by orchestrating start, stop, wait, describe, and resource commands across projects. This enforces prerequisites like the Aspire CLI and .NET tooling to provide a predictable, non-interactive runtime for AI agents.

What is the best way to recover from Aspire AppHost port conflicts and file locks?▼

Recovering from Aspire AppHost port conflicts, file locks, and orphaned processes is handled through safe recovery workflows. These detect and resolve common operational failures like MSB3491 and CS2012 errors automatically without manual intervention.

Do I need the Aspire CLI and .NET tooling to run AppHost lifecycle commands?▼

Yes, the Aspire CLI and .NET tooling are required prerequisites. The orchestrator enforces these dependencies along with safety guardrails to ensure consistent, agent-friendly operation across different environments.

How does non-interactive operation work when managing Aspire AppHost projects?▼

Non-interactive operation works by enforcing safety guardrails that deliver consistent behavior across environments. This allows AI agents to coordinate end-to-end workflows predictably without requiring manual user input during execution.

Can I monitor Aspire resources and describe their state during orchestration?▼

Yes, you can monitor Aspire resources and describe their state using the aspire ps and describe commands. These resource-level operations allow you to track state and handle errors across Aspire projects throughout the lifecycle.

Why does Aspire AppHost orchestration enforce safety guardrails for AI agents?▼

Safety guardrails are enforced to ensure safe, agent-friendly operation with consistent behavior. They prevent unpredictable states during automated lifecycle management, allowing reliable recovery from failures without manual intervention.