Skip to main content
Configure the SDK after your app knows the current workspace/channel and, if available, the current user.
If Sagepilot provides a dedicated endpoint for your workspace, pass it as an optional override:

Supported options

For attachment setup, see Native file picker. For push notifications, see Push notifications.

Basic setup

Mount the provider once near the top of your app:

Keep configuration lifecycle stable

SagepilotChat.configure(...) is asynchronous. Await it before calling identify() or opening chat, and avoid reconfiguring the SDK on every render. If your setup depends on auth or workspace state, use stable primitive values in the effect dependencies. Do not depend on entire session or user objects if your auth library recreates those objects frequently.
Mount SagepilotChatProvider once, and only re-run setup when the actual workspace, channel, or user values change.

Chat launcher theme

Use theme.launcher to configure the icon button and unread badge colors for your app-owned launcher. The SDK resolves omitted values to Sagepilot defaults.