u/AshP91

I posted about AgentBlazor on here three weeks ago when 0.1 went on NuGet. Shipping 0.2.0 today and wanted to share what changed, since most of it came directly from feedback on the original threads.

Live demo (no install): https://demo.agentblazor.com/

The architectural argument hasn't changed: the LLM operates your Blazor app through the typed C# methods you've already written, not by getting database access or generating SQL. The pitch is narrow — one route, one chat surface, one capability class, one deterministic UI change after the prompt.

The demo now uses a support queue because the behaviour is concrete. This morning I asked the agent to draft replies for three highlighted tickets. One came back blocked: "TCK-1055 is missing order evidence, so the reply needs escalation first." The workflow's check held. The agent didn't bypass the gate or fabricate evidence — it surfaced the block and stopped.

That's the trust boundary v0.2 is built around. Your typed methods are the agent's contract.

What's new since April:

Structured capability errors with LLM-readable recovery hints (instead of raw exceptions that make the agent spiral)

Schema-only entity exposure via optional AgentBlazor.EntityFrameworkCore — agent reasons about allowlisted EF entities as planning context, can't query the DB directly

Cleaner install path: dotnet add package AgentBlazor (no more swap-files-in-order starter)

Hosted demo with structured per-turn logging

Six package fixes from the April feedback (ambiguous endpoint method, misleading "default agent" copy, friendlier exception when API key missing, shell rendering logic, etc.)

Honest limits:

Preview-grade overall, MudBlazor-first for built-in wrappers

OpenAI is the default provider today

Built on Microsoft Agent Framework (GA core + preview hosting transport)

Multi-library wrapper support (Radzen, Telerik, etc.) is v0.3 work

Install: dotnet add package AgentBlazor Repo: https://github.com/ashpeterson/AgentBlazor Quickstart: https://github.com/ashpeterson/AgentBlazor/blob/master/docs/quickstart.md

Happy to answer questions about the architecture, the trust-boundary design, or what shipping the April feedback cycle taught me about building this in the open.

I posted about AgentBlazor on here three weeks ago when 0.1 went on NuGet. Shipping 0.2.0 today and wanted to share what changed, since most of it came directly from feedback on the original threads.

Live demo (no install): https://demo.agentblazor.com/

The architectural argument hasn't changed: the LLM operates your Blazor app through the typed C# methods you've already written, not by getting database access or generating SQL. The pitch is narrow — one route, one chat surface, one capability class, one deterministic UI change after the prompt.

The demo now uses a support queue because the behaviour is concrete. This morning I asked the agent to draft replies for three highlighted tickets. One came back blocked: "TCK-1055 is missing order evidence, so the reply needs escalation first." The workflow's check held. The agent didn't bypass the gate or fabricate evidence — it surfaced the block and stopped.

That's the trust boundary v0.2 is built around. Your typed methods are the agent's contract.

What's new since April:

• Structured capability errors with LLM-readable recovery hints (instead of raw exceptions that make the agent spiral)
• Schema-only entity exposure via optional AgentBlazor.EntityFrameworkCore — agent reasons about allowlisted EF entities as planning context, can't query the DB directly
• Cleaner install path: dotnet add package AgentBlazor (no more swap-files-in-order starter)
• Hosted demo with structured per-turn logging
• Six package fixes from the April feedback (ambiguous endpoint method, misleading "default agent" copy, friendlier exception when API key missing, shell rendering logic, etc.)

Honest limits:

• Preview-grade overall, MudBlazor-first for built-in wrappers
• OpenAI is the default provider today
• Built on Microsoft Agent Framework (GA core + preview hosting transport)
• Multi-library wrapper support (Radzen, Telerik, etc.) is v0.3 work

Install: dotnet add package AgentBlazor
Repo: https://github.com/ashpeterson/AgentBlazor
Quickstart: https://github.com/ashpeterson/AgentBlazor/blob/master/docs/quickstart.md

Happy to answer questions about the architecture, the trust-boundary design, or what shipping the April feedback cycle taught me about building this in the open.

Has anyone used a dye on their system? Got a system from lordhair in Feb thus year, the system itself is onay but the color has gone from a light brown to orangey/ginger tones. Anyone had succces dying their system? If so any products that worked well?

Cheers!

I work in a team of 4 C# devs theres the techinical director (who still codes), a lead dev (who doesn't have much dotnet knowledge but has been at the company for 10+ years) me as a senior dev and another dev. I have previously worked in larger more corporate teams where everything went through PRs and code review but current is more like a startup than corporate. So things I find strange that we do:

- We don't use PR's or any reviews of code in any way we all just push and it gets tested by another team, if something is broke we fix it then go again.

- Morning is what everyone's doing, EOD is what everyone did. That's it. No discussion of quality, no hey this bit of code concerns me, just a status recitation and everyone goes back to work.

My question has anyone ever worked in a similar team env, it feels strange and took me some time to get used to but I feel there is so much we could be doing better? Is this just small team life? Do others have this? And if you do — does it bother you, or have you made peace with it?