Skip to main content
Embedded chat uses the native Tilde chat channel. Your server proxies the chat API and says who the user is; the browser renders the chat components.

With an embed key CLOUD

Name the agents on the embed key (project Embed tab), then list them on the server:
lib/tilde.ts
The handler serves the chat API under /api/tilde/chat. Render the components:
The identity prop only groups the components’ caches. Your server’s resolveIdentity decides who the user is.

With an agent’s chat key

Without an embed key, and in Tilde OSS, use @trytilde/chat-proxy with the agent’s chat key from the agent’s Chat providers tab:
@trytilde/chat-next adapts it to Next.js route handlers, and @trytilde/chat-ui provides the same Chat and ListSessions components.

Who may chat

The agent’s channel access applies to embedded users like any other channel. A private agent accepts only users you allow on its IAM tab; a public agent accepts every user your server vouches for. Each user sees only their own sessions.