Troubleshooting
Check the runtime path before guessing.
Most failures reduce to wiring, assets, route scoping, or host-shape rules.
First commands to run
agentblazor doctor ./MySolution.slnx --host MyBlazorApp
agentblazor validate ./MySolution.slnx --host MyBlazorApp
agentblazor scaffold ./MySolution.slnx --host MyBlazorApp --provider openai --diff
dotnet build ./MySolution.slnx --no-restore -nologoUI renders but nothing responds
- Confirm
AddMudServices(). - Confirm
AddAgentBlazor(...)beforebuilder.Build(). - Confirm
app.MapAgentBlazorEndpoints(). - Confirm MudBlazor and AgentBlazor assets are loaded.
- Confirm the layout includes Mud providers.
Actions do not appear
- Check
[AgentCapability(...)]. - Check
[AgentAction(...)]. - Check
AddWorkflow<T>(). - Check
WithRoutePrefixes(...)matches the route.
Hosted WebAssembly remote chat issues
- Confirm
app.MapAgentBlazorRemoteChat()on the server. - Confirm the client uses
AgentBlazor.Client. - Confirm the client registers
HttpClientwith the host base address. - Confirm the endpoint is usually
/agentblazor/chat/run.