cloud

A setup skill for assistant-ui Cloud persistence and authorization, using the `assistant-cloud` package and the `AssistantCloud` client. It applies when adding cross-session thread and message persistence, multi-device chat history, file uploads, or authentication to an assistant-ui application. The cloud instance is passed as the `cloud` option to `useChatRuntime` alongside `AssistantChatTransport` from `@assistant-ui/react-ai-sdk`, and wrapped with `AssistantRuntimeProvider`. For the thread-list sidebar UI itself, a separate thread-list skill is used. The doc directs consulting assistant-ui.com/llms.txt for the latest API.

`AssistantCloud` supports three authentication modes. The recommended JWT approach supplies an async `authToken` callback that returns the session access token. A server-side API-key approach uses `apiKey` together with `userId` and `workspaceId`. An anonymous mode (`anonymous: true`) suits public apps. All modes take a `baseUrl`, typically from the `NEXT_PUBLIC_ASSISTANT_BASE_URL` environment variable, with `ASSISTANT_API_KEY` reserved for server-side use. The skill references additional guides for persistence, authorization patterns, self-hosted custom persistence, and auth integrations including better-auth and Clerk.

The Cloud API exposes thread operations—`cloud.threads.list()`, `create()`, `update(threadId, ...)`, and `delete(threadId)`—plus message access via `cloud.threads.messages(threadId).list()`. File uploads use `cloud.files.generatePresignedUploadUrl({ filename })`, which returns a signed URL the client PUTs the file to, along with a public URL. The doc also notes common gotchas: threads that do not persist usually mean the `cloud` option was not passed to the runtime or authentication is misconfigured, and auth errors typically mean `authToken` is not returning a valid token or `baseUrl` is incorrect. Installation is via `npm install assistant-cloud`.