Connect page behavior to chat and agent lifecycle

Overview

The page may need to react to a business result without showing its control payload as a chat bubble. OnMessageReceived receives the whole AgentMessage. Returning false suppresses that item only in the link panel; it does not erase shared workspace history.

A business response may need two presentations

An agent can return text for the conversation and metadata that tells the page to refresh a request record. OnMessageReceived receives the whole envelope so application code can recognize its own contract. Returning false suppresses that item in this link panel; it does not delete it from shared history or cancel the underlying business operation.

Bind lifetime to your intended scope

A page-scoped agent can be useful for temporary work, while an enduring assistant should outlive a component render. Dispose subscriptions when the component leaves and avoid provisioning a new instance on every UI update. A callback that performs a write must still check authorization and idempotency; receiving an agent message is not blanket approval to mutate a record.

Handle a page-specific response

Download the Operations Desk source. The README lists project setup, package prerequisites and local ports.

1. Handle data-changed or ui-update messages in C#, validate the target/context, refresh the page data and return false when the panel should suppress the handled payload. Return true for normal chat.
2. Use CreateAgent with SurfaceChatLinkCreateAgentContext to supply a page-specific recipe. Creation happens after the user clicks Create, not automatically on page load.
3. Use AllowExternalAgent for an already healthy pre-provisioned target; disable it for strict manual creation. Enable AllowReset only when reset is appropriate and label readiness/lifecycle messages clearly.

<SurfaceChatLink AgentHandle="crm-agent"
                 Title="CRM Assistant"
                 OnMessageReceived="HandleAgentMessageAsync" />

@code {
    private async Task<bool> HandleAgentMessageAsync(AgentMessage message)
    {
        if (string.Equals(message.MessageType, "ui-update", StringComparison.OrdinalIgnoreCase))
        {
            await RefreshSectionAsync(message.Message);
            return false;
        }

        if (string.Equals(message.MessageType, "data-changed", StringComparison.OrdinalIgnoreCase))
        {
            await ReloadDataAsync();
            return false;
        }

        return true;
    }
}

<SurfaceChatLink AgentHandle="customer-assistant"
                 Title="Customer Assistant"
                 CreateAgent="CreateCustomerAssistantAsync"
                 AllowReset="true" />

@code {
    private Task<AgentHealthStatus> CreateCustomerAssistantAsync(
        SurfaceChatLinkCreateAgentContext context)
    {
        return context.PrincipalContext.CreateAgent(new AgentConfiguration
        {
            Handle = context.AgentAlias,
            AgentType = "customer-agent",
            Models = "default",
            Description = "Customer page assistant",
            ForceReconfigure = false
        });
    }
}

Go deeper

Explore the related documentation.

• FabrCore Websocket
• FabrCore Client
• FabrCore Blazor
• SurfaceChatLink: complete parameters, callbacks and lifecycle