Editor's note
I pulled together another deliberately mixed issue today, with AI agent architecture sitting right next to core runtime and web stack material. The multi-agent framework and governance pieces are timely if you’re experimenting with LLM orchestration, while the ASP.NET Core WebApplication deep dive and fan-out concurrency postmortem are the kind of practical internals content I always like to surface.
Agents, safety, and ASP.NET internals
Jasen Fici
June 04, 2026
In partnership with
AI agents now read your docs almost as much as humans do.
Mintlify analyzed 790 million requests across its documentation platform. The finding: AI coding agents account for 45.3% of all traffic, nearly tied with traditional browsers at 45.8%.
Two tools are driving almost all of it:
-
Claude Code: 25.2% of total traffic, more requests than Chrome on Windows
-
Cursor: 18% of total traffic
-
Together they account for 95.6% of all identified AI agent traffic
The rest of the field, OpenCode, Trae, ChatGPT, and NotebookLM, is showing up but nowhere close.
One caveat: OpenAI's Codex doesn't send an identifiable user-agent header, so the real agent percentage is likely even higher.
The takeaway for anyone maintaining developer docs: your documentation now serves two audiences. Structure and machine-readability matter as much as clarity for human readers.
Enjoying the newsletter? Your feedback helps us grow and reach more developers.
Today's Articles
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Jasen's take on today's picks
Multi-Agent Frameworks for .NET — A Practical Guide
Useful primer if you're moving beyond single-prompt apps and want a clearer mental model for agent orchestration in .NET.
Database Connection Pooling vs DbContext Pooling in .NET
A good clarification piece; connection pooling and DbContext pooling get mixed up constantly, and the tradeoffs matter under load.
Collections in C# — From Basic to Advanced
Broad C# refresher content, but still handy for newer developers brushing up on collection choices and behavior.
Agent Governance Toolkit for .NET:
Governance is the less glamorous side of agent systems, which is exactly why this caught my eye.
Microsoft wants safer C# without turning it into Rust
Worth watching because safer C# without copying Rust outright is a meaningful design direction for the language.
Mission Possible : Implementing Design Patterns in .NET
A survey-style design patterns article that may be most useful for juniors or teams revisiting fundamentals.
C# Has a Null Problem. Here’s What That Means
Null remains one of the most expensive simple problems in C#, so approachable explanations still earn a spot.
To Prompt or NOT to Prompt #vscode #prompt #customization
More adjacent than deeply technical, but it reflects how prompt customization conversations keep spilling into dev workflows.
Improving C# Memory Safety: Why Modern .NET Is Quietly Becoming More Secure
This pairs nicely with the safer C# discussion and frames memory safety as an active .NET story, not someone else's concern.
When Parallel Became a Problem: A Backend Engineering Postmortem on Fan-Out Concurrency
A practical postmortem on Task.WhenAll fan-out pain; exactly the sort of failure mode backend teams should study early.
C# Barcode Library: Comparing 11 Options for .NET Developers in 2026
Niche, but comparison posts save time when you're evaluating libraries with commercial and open-source options side by side.
Deep Dive into ASP.NET Core's WebApplication — What Really Happens Under the Hood
I like internals explainers that make the startup pipeline less magical and easier to reason about.
OWASP Top 10 for .NET Developers -Part 3: Preventing Injection Attacks
Injection prevention never gets old; secure coding guidance tied to OWASP remains baseline reading.