We’re thrilled to announce the release of Dev Proxy v0.28. This version introduces a new ability to help you understand language models’ usage and costs in your applications, alongside many improvements to mocking, TypeSpec generation, and plugin flexibility.In this version: New OpenAITelemetryPlugin to track language models’ usage and costs Expanded OpenAI payload support New Dev Proxy extensions for .NET Aspire Improved generating PATCH operations for TypeSpec Support for JSONC in mock files Improved logging CRUD plugin CORS and JSON response fixes ...and more!Track OpenAI usage with the new OpenAITelemetryPluginLLMs are powerful. When integrated thoughtfully with applications, they can support new scenarios and significantly improve existing ones. Using LLMs typically incurs costs. But how much does it cost exactly? The new Dev Proxy OpenAITelemetryPlugin gives you visibility into how your apps interact with OpenAI or Azure OpenAI endpoints.This plugin intercepts LLM requests from your application, and for each request tracks: Model used Token count (prompt, completion, total) Cost estimation per request Grouped summaries per modelYou can visualize the usage patterns and costs using specialized solutions such as OpenLIT:OpenLIT visualizing language model usage data emitted by Dev ProxyOr generic Open Telemetry dashboards such as .NET Aspire:The .NET Aspire dashboard visualizing language model usage information emitted by Dev ProxyUse Dev Proxy and the new OpenAITelemetryPlugin and understand how your application is using language models, before you go live.Try Dev Proxy with Foundry LocalAt the recent Build conference, Microsoft announced Foundry Local - the high-performance local AI runtime stack that brings Azure AI Foundry’s power to client devices. We’re excited to share that you can configure Dev Proxy to use Foundry Local as the local language model provider. By enabling the integration, you can improve generating OpenAPI specs and TypeSpec files, and redirect cloud LLM requests to your local machine to save costs and enable offline development.To use Dev Proxy with Foundry Local, configure Dev Proxy to use Foundry Local:Our initial tests show significant improvements using Phi-4 mini on Foundry Local compared to other models we’ve used in the past. We’re planning to integrate with Foundry Local by default, in the future versions of Dev Proxy. Meanwhile, try it today!Dev Proxy .NET Aspire extensionsTo simplify integrating Dev Proxy with .NET Aspire applications, we released a preview version of Dev Proxy extensions for .NET Aspire. Using the extensions, you can integrate Dev Proxy with your .NET Aspire application with just a few lines of code. The extensions allow you to integrate the locally installed Dev Proxy instance or run it from a Docker container for easier portability across your team.Learn more about using the Dev Proxy .NET Aspire extensions and let us know how we could make it better.Bug fixes and improvementsIn this version, we include several bug fixes and improvements.Expanded OpenAI payload supportContinuing our work related to AI, we’ve expanded our support for OpenAI payloads. Previously, when redirecting OpenAI-compatible requests, we only supported text completions. In this version, we introduce support for other types of completions as well.Improved generating PATCH operations for TypeSpecIn the previous version, we introduced support for generating TypeSpec files: a new language for describing APIs. In this version, we improved generating PATCH operations, aligning with TypeSpec v1.0 features, so that merge patch operations are designated with MergePatchUpdate.Support for JSONC in all Dev Proxy filesIn this version, we introduce support for JSONC in all Dev Proxy files. With support for JSONC, you can annotate Dev Proxy’s config files with additional information. Including comments right in Dev Proxy files is highly convenient for sharing configuration with others in the team and picking it up after a while.Concurrency fixes for mocking and loggingWe resolved several issues related to logging, when Dev Proxy was processing parallel requests. Thanks to these fixes, logs are displayed properly showing all information related to the specific request together, making it easier for you to understand how Dev Proxy processed each request.CRUD API plugin enhancementsWe’ve improved how the CrudApiPlugin supports CORS and returns JSON responses. With these changes, you can reliably use it in client-side applications that issue cross-domain API calls.Breaking changesIn this version, we’re also introducing two breaking changes.First, we removed the GraphConnectorNotificationPlugin. As deploying Graph connectors using Microsoft Teams apps has been deprecated, we removed the plugin which is no longer necessary. We still offer guidance to help you build Graph connectors.The second change is related to the `devproxy jwt create` command which you can use to create mock JWT tokens. In the command, we renamed the `--audience` option to `--audiences` (plural) to more accurately reflect the fact that it supports multiple audiences. Using the short `-a` alias to specify audiences is unaffected by this change.There’s moreThis release also includes several bug fixes and improvements. Check out the release notes for the complete list of changes in this version.New version of Dev Proxy ToolkitDev Proxy Toolkit is a Visual Studio Code extension that makes it easy to create and update configuration files. Alongside the new release of Dev Proxy, we’ve also released a new version of the toolkit, v0.24.0.In this version, we’ve included: New command Discover URLs to watch starts Dev Proxy in discovery mode New snippets OpenAITelemetryPlugin instance OpenAITelemetryPlugin config section OpenAITelemetryPlugin prices file OpenAITelemetryPlugin model price Updated all snippets to use latest v0.28.0 schemas Improved support for Dev Proxy Beta Improved Dev Proxy process detectionCheck out the changelog for more information on changes and bug fixes.Try it nowDownload Dev Proxy v0.28 and start building resilient apps and AI solutions. Thanks to Artem Azaraev for contributing to this release.Got feedback or ideas? Join us and be part of the conversation.Follow us on X, LinkedIn, and subscribe to our YouTube channel to stay up to date on the latest developer news and announcements.