Yesterday I had the pleasure of presenting “Bending Aspire to Your Will” at VISUG XL , where we celebrated 20 years of the Visual Studio User Group (VISUG). It was a great occasion to share ideas with the developer community, get inspired and see a lot of familiar faces again. I started with a quick tour of Aspire 'as-is': its AppHost, dashboard, resources and observability features. Then, using an API-testing scenario as an example, I showed how to shape and customize Aspire around a developer’s workflow: Customizing dashboard icons and URLs to make resources easier to navigate. Adding a command to export an OpenAPI specification. Running a test call against an API endpoint from the dashboard. Resetting application state by clearing Redis and recreating the database. Creating a custom Scalar resource to bring API references together in one place. The takeaway: Aspire isn’t just a way to run your application locally. Its resource model and extension p...
There’s a moment when you hand a bigger task to Copilot CLI and wonder what it’s going to cost you. By default GitHub Copilot runs until the task is done or until you step in. Yesterday I showed how to tackle this in Claude Code. Today let’s have a look on how GitHub lets you cap that. Remark: Like with Claude Code, this isn’t a token limit. Copilot tracks AI credits, where each credit equals $0.01 USD. Usage depends on the model and the number of tokens consumed. Setting a limit in an interactive session Use /limits set : /limits set max-ai-credits 100 That’s a ceiling of $1.00. The limit applies to the entire session and depletes with every message, no matter how many messages you send. To remove it again: /limits unset Setting a limit in non-interactive mode When you run the CLI programmatically, pass --max-ai-credits : copilot -p "Run the test suite and fix the failing tests" --max-ai-credits 100 Here the limit applies for the duration of Copilot’s...