Agent skill · software engineering · assistant-ui
cloud
Adds AssistantCloud backed persistence, authorization, and telemetry to assistant-ui apps. Use when wiring cross-session thread and message history, multi-device chat, message feedback, file uploads, or auth: passing `cloud` to `useChatRuntime` from `@assistant-ui/ai-sdk`, `AISDKThreads({ cloud })` for `AuiConfig` hosts, the standalone `useCloudChat`/`useThreads` hooks from `@assistant-ui/cloud-ai-sdk`, or `cloud` on `useLangGraphRuntime`. Covers constructing `AssistantCloud` with `authToken` (JWT), `apiKey` plus `userId`/`workspaceId` (server-side), or `anonymous`; direct provider integrations (Clerk, Auth0, Supabase, Firebase) and a backend token endpoint; and the client surface verified against source: `cloud.threads.{list,get,create,update,delete}`, `cloud.threads.messages.{list,create,update,feedback}`, `cloud.files.{generatePresignedUploadUrl,pdfToImages}`, `cloud.runs.{stream,report}`, `cloud.projects.threads`, `cloud.auth.tokens.create`, and `cloud.telemetry`. Also covers a custom `ThreadHistoryAdapter` built on `CloudMessagePersistence`/`createFormattedPersistence`, run telemetry (`beforeReport`, sub-agent tracking with `wrapSamplingHandler`), and the `NEXT_PUBLIC_ASSISTANT_BASE_URL`/`ASSISTANT_API_KEY` env vars. Route here for threads that do not persist, 401s against the cloud API, or feedback buttons that do not save. For the `<ThreadList />` sidebar UI itself use thread-list; for the general `RemoteThreadListAdapter`/`ThreadHistoryAdapter` contract use runtime.
Why this skill is useful
Adds executable scripts for cloud persistence and authorization that extend the AI's capabilities in managing chat sessions and file uploads.
What it needs
Requires assistant-cloud installed locally. About 7k tokens when loaded. Last updated 2026-08-02. 20 stars on the source repository.
What this skill does
assistant-ui Cloud Always consult assistant-ui.com/llms.txt for the latest API. Assistant Cloud is a hosted service that adds thread persistence, message history, auto-generated titles, message feedback, and file uploads to any React chat UI, with or without assistant-ui's own components. One AssistantCloud client backs three integration paths: the full assistant-ui runtime, a standalone AI SDK hook, and LangGraph Cloud. Contents References Install Quick start: useChatRuntime AuiConfig hosts: AISDKThreads Standalone AI SDK: useCloudChat LangGraph Message feedback Authentication Client API Environment variables Common Gotchas Related Skills References ./references/persistence.md -- the thread, message, file, and run client API in full, verified against source ./references/authorization.md -- the three auth modes and direct provider integrations (Clerk, Auth0, Supabase, Firebase) ./references/custom-persistence.md -- CloudMessagePersistence and createFormattedPersistence, for a custom ThreadHistoryAdapter backed by cloud message storage ./references/auth-integrations.md -- non-cloud auth gating with Auth.js (next-auth), Clerk, and better-auth, plus pairing AssistantCloud with a backend token endpoint Install assistant-cloud ships as a dependency of @assistant-ui/react, which re-exports AssistantCloud for browser code. Server-side code (API routes, token endpoints) that has no reason to depend on @assistant-ui/react imports AssistantCloud from assistant-cloud directly. Quick start: useChatRuntime useChatRuntime({ cloud }) from @assistant-ui/ai-sdk wraps AI SDK's useChat and adds persistence. It creates a cloud thread on the first message, persists messages as they stream, generates a title after the first response, loads history on thread switch through <ThreadList />, and submits message feedback against the stored message. anonymous: true is for demos; see Authentication for production auth. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills assistant-ui/cloud