Home / Docs / Blazor UI Integration

Blazor UI Integration

Blazor UI Integration

The old FabrCore.Client Blazor component package is obsolete and has been removed. Blazor apps should call the Host REST API, connect to WebSocket ingress for streaming updates, and keep UI state in the application layer.

Principal-scoped identity:

Pass the authenticated principal handle to the Host API. Current wire names include x-user-handle and x-fabrcore-userhandle, but the value is the principal partition used by PrincipalGrain.

Server-Side Blazor Pattern

Inject an application service that wraps IFabrCoreHostApiClient. Keep authentication, authorization, and UI-specific state in your Blazor app.

REST API

Use the Host REST API for agent creation, chat, health, storage, discovery, embeddings, files, and diagnostics.

WebSocket Streaming

Use /ws when a UI needs bidirectional messages, progress events, or long-running agent updates.

Migration from Chat UI Components

  • Remove FabrCore.Client, ChatDock, ChatDockManager, ClientContext, and DirectMessageSender usage.
  • Move agent chat and lifecycle calls into application services backed by FabrCore.Sdk or raw HTTP calls.
Documentation