Communitygithub.com

assistant-ui/thread-list

Implementa la gestión de múltiples hilos (historial de conversaciones) en aplicaciones assistant-ui: renderiza el `ThreadList` preconstruido junto a `Thread`, o construye una barra lateral personalizada con `ThreadListPrimitive` y `ThreadListItemPrimitive` (Root, New, Items, Trigger, Title, Archive, Unarchive, Delete). Cubre CRUD de hilos a través de la API `useAui()`/`useAuiState()`: `switchToThread`, `switchToNewThread`, y por elemento `rename`, `archive`, `unarchive`, `delete`, `generateTitle`, `initialize`, además de leer `s.threads.threadIds`/`archivedThreadIds`/`mainThreadId`. Incluye persistencia respaldada en la nube mediante `useChatRuntime` + `AssistantCloud` y una ruta local `useRemoteThreadListRuntime` + `InMemoryThreadListAdapter`. Úsalo cuando un usuario quiera una lista/barra lateral de hilos, cambiar entre ellos, buscar, ordenar, arrastrar y soltar, o renombrar/archivar/eliminar conversaciones. Para estado de un solo hilo, mensajes o compositor, usa el runtime; para configuración de autenticación/persistencia en la nube, usa cloud.

¿Qué es thread-list?

El skill `assistant-ui/thread-list` proporciona una solución completa para gestionar múltiples hilos de conversación (historial) en aplicaciones assistant-ui. Su principal utilidad es permitir a los desarrolladores implementar una lista de hilos o barra lateral donde los usuarios pueden cambiar entre conversaciones, buscar, ordenar por varios criterios, arrastrar y soltar elementos, y realizar acciones CRUD como renombrar, archivar, desarchivar y eliminar hilos. Está diseñado para plataformas basadas en React, como Cursor o aplicaciones web personalizadas, y se integra perfectamente con el ecosistema assistant-ui. El skill expone componentes preconstruidos (`ThreadList`) y primitivos personalizables (`ThreadListPrimitive`, `ThreadListItemPrimitive`) para flexibilidad en la UI. Para la capa de datos, ofrece dos rutas de persistencia: una respaldada en la nube mediante `useChatRuntime` + `AssistantCloud`, ideal para aplicaciones multi-usuario con autenticación; y una ruta local con `useRemoteThreadListRuntime` + `InMemoryThreadListAdapter`, perfecta para prototipado o uso sin backend. La lógica de estado se maneja a través de las APIs `useAui()`/`useAuiState()`, que exponen funciones como `switchToThread` y `switchToNewThread`, y permiten leer fácilmente los IDs de hilos activos, archivados y el hilo principal.

Compatible con~Claude Code~Codex CLI~Cursor
Part ofDesign & UI
npx skills add https://github.com/assistant-ui/skills/tree/main/skills/thread-list
Ver original→Ver todas las habilidades

Preguntar en tu IA favorita

Abre un nuevo chat con esta habilidad de agente ya precargada.

OpenAIChatGPTClaudeClaudeGeminiGeminiGrokGrokPerplexityPerplexityDeepSeekDeepSeek

Documentación

¿Qué hace thread-list?

Implementa la gestión de múltiples hilos (historial de conversaciones) en aplicaciones assistant-ui: renderiza el ThreadList preconstruido junto a Thread, o construye una barra lateral personalizada con ThreadListPrimitive y ThreadListItemPrimitive (Root, New, Items, Trigger, Title, Archive, Unarchive, Delete). Cubre CRUD de hilos a través de la API useAui()/useAuiState(): switchToThread, switchToNewThread, y por elemento rename, archive, unarchive, delete, generateTitle, initialize, además de leer s.threads.threadIds/archivedThreadIds/mainThreadId. Incluye persistencia respaldada en la nube mediante useChatRuntime + AssistantCloud y una ruta local useRemoteThreadListRuntime + InMemoryThreadListAdapter. Úsalo cuando un usuario quiera una lista/barra lateral de hilos, cambiar entre ellos, buscar, ordenar, arrastrar y soltar, o renombrar/archivar/eliminar conversaciones. Para estado de un solo hilo, mensajes o compositor, usa el runtime; para configuración de autenticación/persistencia en la nube, usa cloud.

Individual skills in this repo

This repo contains 7 individual skills — each has its own dedicated page.

assistant-ui/assistant-ui

Overview and router for assistant-ui, the React library for building AI chat interfaces from composable primitives. Use for high-level, cross-cutting, or architecture-overview questions: choosing packages, picking a runtime, or understanding the layered model (RuntimeCore, Runtime, context hooks, primitives) and message model. Covers the `@assistant-ui/react` core plus `@assistant-ui/react-ai-sdk`, `@assistant-ui/react-langgraph`, `assistant-stream`, and `assistant-cloud`; `AssistantRuntimeProvider`; the primitives `ThreadPrimitive`, `MessagePrimitive`, `ComposerPrimitive`; the hooks `useAui`, `useAuiState`, `useAuiEvent`; and runtime selection across `useChatRuntime`, `useExternalStoreRuntime`, `useLangGraphRuntime`, `useLocalRuntime`. For a specific area route to a focused sibling instead: setup, runtime, primitives, tools, streaming, cloud, thread-list, or update. Not for hands-on tasks already owned by those siblings.

assistant-ui/primitives

Builds and customizes assistant-ui chat UI from composable, unstyled @assistant-ui/react primitives that follow Radix-style part composition. Use when assembling or styling a custom Thread, Composer, message rendering, action bar, or branch picker from building blocks: ThreadPrimitive (.Root, .Viewport, .Messages, .Empty, .ScrollToBottom), ComposerPrimitive (.Input, .Send, .Cancel, .Attachments), MessagePrimitive (.Parts/.Content, .Error), ActionBarPrimitive (.Copy, .Edit, .Reload, .Speak, feedback, .ExportMarkdown), BranchPickerPrimitive, AttachmentPrimitive, ThreadListPrimitive, ThreadListItemPrimitive. Covers MessagePrimitive.Parts children render functions for text, image, reasoning, and tool-call parts; conditional rendering with AuiIf (deprecated .If); and gotchas like wrapping in AssistantRuntimeProvider and adding className since primitives ship unstyled. For prebuilt drop-in UI and scaffolding use setup; for multi-thread sidebar behavior use thread-list.

assistant-ui/runtime

Guide for assistant-ui runtime system and state management. Use when working with runtimes, accessing state, or managing thread/message data.

assistant-ui/setup

Installs and configures assistant-ui in a project via the CLI, and picks the right runtime for a backend. Use for first-time install, scaffold, or config: `npx assistant-ui@latest create my-app` (templates default, minimal, cloud, cloud-clerk, langgraph, mcp), `npx assistant-ui@latest init [--yes] [--overwrite]` in an existing Next.js app, or `npx assistant-ui@latest add` registry components (markdown-text, thread-list). Also use to choose a runtime hook for a backend: useChatRuntime (AI SDK), useLangGraphRuntime, useAgUiRuntime, useA2ARuntime, useLocalRuntime (custom streaming API), or useExternalStoreRuntime (Redux/Zustand). Covers Vite/TanStack Start setup, shadcn styling, the playground --preset flag, and avoiding the deprecated @assistant-ui/styles and @assistant-ui/react-ui packages. For upgrading an existing install or post-upgrade breakage use update; for building UI from raw parts use primitives.

assistant-ui/streaming

Streaming backends and wire protocols for assistant-ui via the assistant-stream package. Use when building a custom (non-AI-SDK) streaming endpoint with createAssistantStreamResponse or createAssistantStreamController, emitting parts through appendText/appendReasoning/appendSource/appendFile/addToolCallPart and setResponse; choosing between the AI SDK Data Stream format (toUIMessageStreamResponse) and the native Assistant Transport format; encoding or decoding streams with DataStreamEncoder/DataStreamDecoder, AssistantTransportEncoder/AssistantTransportDecoder, PlainTextEncoder, or UIMessageStreamDecoder; or wiring streamed chunks into useLocalRuntime or useChatRuntime. Use specifically for debugging stream wire issues: text-delta, part-start, result events, text/event-stream content-type, SSE format, tool calls not rendering, or partial text not showing. For general non-stream debugging route to the relevant focused skill, not the parent overview.

assistant-ui/tools

Registers LLM tools and renders custom tool-call UI in assistant-ui (@assistant-ui/react). Use when adding frontend-only tools with makeAssistantTool / useAssistantTool (browser actions like clipboard, navigation, localStorage, async-generator streaming, AbortSignal), rendering backend AI SDK tool() calls with makeAssistantToolUI / useAssistantToolUI (status.type running/complete/incomplete/requires-action, args, result, artifact via ToolCallMessagePartProps), building generative UI from tool results, or implementing human-in-the-loop and approval flows (addResult, resume with context.human(), respondToApproval for server-side needsApproval gates). Covers registering tool components inside AssistantRuntimeProvider and the case-sensitive toolName matching that connects a tool to its UI. Reach for this when tool UI is not rendering, a tool is not being called, or a result is not showing.

assistant-ui/update

Upgrades an existing assistant-ui project to current releases and executes the resulting migrations. Use when the user wants to update, upgrade, bump, or migrate @assistant-ui/react, @assistant-ui/react-ai-sdk, ai, or @ai-sdk/react, hits peer-dependency conflicts or post-upgrade type errors, or must apply renamed APIs after a version jump. Detects installed versus latest versions via npm ls / npm view, then routes through breaking-change references for each jump (AI SDK v4/v5 to v6; assistant-ui 0.8.x to 0.14.x): useAssistantApi to useAui, runtime.threadList to runtime.threads, ThreadPrimitive.ViewportSlack removal, the primitives components prop to children render functions, toDataStreamResponse to toUIMessageStreamResponse, maxSteps to stopWhen: stepCountIs(n). Runs npx assistant-ui@latest upgrade, pnpm/npm add @latest, and npx tsc --noEmit to verify. For a first-time install or fresh scaffold (not an upgrade) use setup instead.

Skills relacionados

steipete/sag

ElevenLabs text-to-speech with mac-style say UX.

community

steipete/oracle

Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.

community

steipete/peekaboo

Capture and automate macOS UI with the Peekaboo CLI.

community

mattpocock/design-an-interface

Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".

community

mattpocock/prototype

Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.

community

mattpocock/grill-me

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

community