|
| 1 | +--- |
| 2 | +title: "Dev Proxy v2.1 with configuration hot reload and stdio proxying" |
| 3 | +description: "We're excited to announce the release of Dev Proxy v2.1.0! This release brings two major productivity features that developers have been asking for: automatic configuration hot reload and stdio traffic proxying." |
| 4 | +date: 2026-01-29 |
| 5 | +author: "Waldek Mastykarz, Garry Trinder" |
| 6 | +tags: ["release"] |
| 7 | +image: "/blog/images/og-image-dev-proxy-v2-1-with-configuration-hot-reload-and-stdio-proxying.webp" |
| 8 | +--- |
| 9 | + |
| 10 | +We're excited to announce the release of Dev Proxy v2.1.0! This release brings two major productivity features that developers have been asking for: automatic configuration hot reload and stdio traffic proxying – perfect for testing MCP servers and other stdio-based tools. In this version: |
| 11 | + |
| 12 | +- **Configuration hot reload** – Dev Proxy automatically restarts when you change the config file |
| 13 | +- **Stdio traffic proxying** – Intercept, inspect, and mock stdin/stdout/stderr traffic |
| 14 | +- **New `--api-port` command-line option** |
| 15 | +- **LatencyPlugin** now supports delays greater than 10 seconds |
| 16 | +- **CORS support** for the Dev Proxy web API |
| 17 | +- Multiple bug fixes and improvements |
| 18 | + |
| 19 | +## Configuration hot reload |
| 20 | + |
| 21 | +No more manual restarts when tweaking your proxy configuration. Dev Proxy now watches your configuration file and automatically restarts when you save changes. |
| 22 | + |
| 23 | +This was one of our oldest feature requests – dating back to April 2023. Whether you're adjusting failure rates, adding plugins, or changing URL patterns, your changes take effect immediately. Just save the file and keep working. |
| 24 | + |
| 25 | +### Why this matters |
| 26 | + |
| 27 | +When you're iterating on your proxy configuration – fine-tuning error rates, adjusting mock responses, or testing different plugin combinations – stopping and restarting the proxy breaks your flow. With hot reload, your development loop gets tighter and more productive. |
| 28 | + |
| 29 | +## Stdio traffic proxying |
| 30 | + |
| 31 | +Modern AI development increasingly relies on tools that communicate via stdin/stdout/stderr – particularly MCP (Model Context Protocol) servers. Now you can intercept and manipulate this traffic just like you do with HTTP. |
| 32 | + |
| 33 | +### How it works |
| 34 | + |
| 35 | +Wrap any executable with Dev Proxy: `devproxy stdio npx my-mcp-server` |
| 36 | + |
| 37 | +Dev Proxy proxies all stdin, stdout, and stderr traffic, letting you: |
| 38 | + |
| 39 | +- **Inspect messages** in Chrome DevTools Network tab (appear as `stdio://` URLs) |
| 40 | +- **Mock responses** using the new MockStdioResponsePlugin |
| 41 | +- **Simulate latency** with the existing LatencyPlugin |
| 42 | +- **Use placeholders** like `@stdin.body.id` in your mock responses |
| 43 | + |
| 44 | +This opens up Dev Proxy to an entirely new category of applications – anywhere you need to test, debug, or mock stdio-based communication. |
| 45 | + |
| 46 | +## New `--api-port` command-line option |
| 47 | + |
| 48 | +Running multiple Dev Proxy instances? Need the default port 8897 for something else? You can now configure the API port directly from the command line: `devproxy --api-port 9000` |
| 49 | + |
| 50 | +No need to create a separate config file just to change the port. |
| 51 | + |
| 52 | +## LatencyPlugin improvements |
| 53 | + |
| 54 | +Previously, the LatencyPlugin schema artificially limited `maxMs` to 10,000 milliseconds (10 seconds). This restriction never existed in the actual code – it was just a schema limitation. |
| 55 | + |
| 56 | +### What changed |
| 57 | + |
| 58 | +The schema now allows any value for `maxMs`, letting you simulate delays of any duration – useful for testing timeout handling and slow network conditions. |
| 59 | + |
| 60 | +## CORS support for Dev Proxy web API |
| 61 | + |
| 62 | +Building browser-based developer tools that interact with Dev Proxy? The API on port 8897 now supports cross-origin requests, so your web applications can call endpoints like `/proxy/jwtToken` without CORS errors. |
| 63 | + |
| 64 | +## Bug fixes |
| 65 | + |
| 66 | +- **`-e` flag now works correctly** – Starting Dev Proxy with environment variable presets no longer throws a `FormatException` |
| 67 | +- **AuthPlugin ApiKey validation fixed** – The plugin no longer incorrectly reports missing `ApiKey.Parameters` when they're properly configured |
| 68 | +- **GenericRandomErrorPlugin method matching** – Error responses without a specified HTTP method now correctly match all methods (GET, POST, PUT, DELETE, etc.) instead of only GET |
| 69 | +- **MockResponsePlugin Content-Type handling** – No more spurious JSON parsing warnings when using form data or other non-JSON content types |
| 70 | +- **CRUD API data file hot reload** – Data file changes now take effect immediately without restarting Dev Proxy |
| 71 | + |
| 72 | +## Dev Proxy Toolkit 1.12.0 |
| 73 | + |
| 74 | +[Dev Proxy Toolkit](https://marketplace.visualstudio.com/items?itemName=garrytrinder.dev-proxy-toolkit) is an extension that makes it easier to work with Dev Proxy from within Visual Studio Code. This release focuses on configuration validation and developer experience improvements: |
| 75 | + |
| 76 | +- **Custom installation paths** — New `devProxyPath` setting for non-standard Dev Proxy locations |
| 77 | +- **Smarter config validation** — Config section properties are now validated against the Dev Proxy schema, catching invalid values, unknown properties, and schema version mismatches |
| 78 | +- **Enhanced diagnostics** — More precise highlighting, unique diagnostic codes with documentation links, and new warnings for empty `urlsToWatch` and optional plugin configurations |
| 79 | +- **More quick fixes** — Add optional or missing plugin config sections, update schema versions across files, and remove unknown properties |
| 80 | +- **Better plugin support** — `AuthPlugin` and `LanguageModelFailurePlugin` fixes, plus new snippets for `GraphConnectorGuidancePlugin` and `MockStdioResponsePlugin` |
| 81 | + |
| 82 | +Checkout out the [changelog](https://marketplace.visualstudio.com/items/garrytrinder.dev-proxy-toolkit/changelog) for more information on changes and bug fixes. |
| 83 | + |
| 84 | +## Why upgrade to v2.1.0? |
| 85 | + |
| 86 | +- **Faster iteration** – Configuration hot reload means no more manual restarts |
| 87 | +- **MCP server testing** – Inspect, mock, and debug stdio traffic with familiar workflows |
| 88 | +- **More flexibility** – Runtime port configuration and unlimited latency simulation |
| 89 | +- **Cleaner experience** – Multiple bug fixes reduce friction and noise |
| 90 | + |
| 91 | +## Try it now |
| 92 | + |
| 93 | +Download **Dev Proxy v2.1.0** today and build better API-connected applications with confidence! |
| 94 | + |
| 95 | +Thanks to [Nitesh Singhal](https://github.com/niteshsinghal85) for contributing to this release. |
| 96 | + |
| 97 | +Got feedback or ideas? [Join us](https://github.com/dotnet/dev-proxy/discussions) and be part of the conversation. |
0 commit comments