Providers
Connect the embedded chat to a Manta deployment and datastore.
What it is
EmbeddedChatProviders is the shell around embedded chat. It supplies the API client and
the query cache the chat uses. Requests go to mantaBaseUrl and carry the browser session for that host.
Import
import { EmbeddedChat } from "@manta-eu/react/components/embedded-chat";
import { EmbeddedChatProviders } from "@manta-eu/react/providers";
Example
export function Copilot() {
return (
<EmbeddedChatProviders datastoreId="your-datastore">
<EmbeddedChat
user={{ id: "…", email: "you@example.com", name: "You" }}
isOperator={false}
datastore={{ id: "your-datastore", name: "Your datastore" }}
assistantName="Copilot"
/>
</EmbeddedChatProviders>
);
}
Request
Wrap the chat and pass:
datastoreId— the datastore GraphQL and SPARQL from this tree belong to. The chat socket uses thedatastoreprop on embedded chat, not this id.mantaBaseUrl— the deployment origin. Omit it to usehttps://app.hiremanta.com.
Response
The chat renders inside the providers. GraphQL and SPARQL from this tree use datastoreId and include the session
cookie for mantaBaseUrl. The chat socket uses the datastore prop on EmbeddedChat.
Requests carry the session from mantaBaseUrl, which defaults to https://app.hiremanta.com. The chat does not sign
the user in. With no session, requests fail with a 401 and the chat does not redirect to a login page. Browsers do not
send the session cookie to an app served from a different domain.