A post I made on /r/moderndotnet - but why don't more .NET authors expose typed IAsyncEnumerables to consumers?
- Supports richer client / server interaction patterns
- Naturally supports backpressure, and
- Makes it much safer to support long-running operations than Task<T>
This is big release for Netclaw:
1. Native PowerShell support for Windows agents
2. Way fewer approval prompts
3. MCP OAuth / other reliability issues have been solved
4. Support for MCP Prompt resources - they're treated just like skills
Install it, connect to Slack / Discord
Netclaw 0.26.0 is out.
Your agent should do the job - not burn tool calls, fight flaky integrations, or trip over the host OS.
55 PRs focused on getting out of the way: fewer wasted moves, better MCP, server prompts as skills, and native PowerShell on Windows.
What's new:
You can view this as ragebait or it's a "where the puck is going" discussion - how long do IDEs have before they are no longer a daily driver, generally, across developer ecosystems?
Adding a Claude Code "Stop" hook to enforce a max cylomatic complexity ceiling in a new .NET project.
This is either going to work out amazingly or utterly terribly - no in-between
