Solution skill
Chat message persistence: store, load, and resume conversations
Complete solution
Guide Chat message persistence: store, load, and resume conversations: Validate the format before using them in file paths or queries; the docs use a strict alphanumeric-plus-dash regex and a startsWith containment check for file stores. Use this when you hit exactly this in Chat message persistence. Not for different errors or different tools.
TL;DR: Validate the format before using them in file paths or queries; the docs use a strict alphanumeric-plus-dash regex and a startsWith containment check for file stores. Most chatbots need history to survive reloads. The pattern: a chat store (your database), chat ids from generateId, and useChat seeded with loaded messages.
Most chatbots need history to survive reloads. The pattern: a chat store (your database), chat ids from generateId, and useChat seeded with loaded messages.
Shape:
// app/chat/page.tsx: create a chat and redirect to /chat/[id] import { redirect } from 'next/navigation'; import { createChat } from '@/util/chat-store';
export default async function Page() { const id = await createChat(); redirect(/chat/${id}); }
// chat store interface (back it with your database) import { generateId } from 'ai'; export async function createChat(): Promise[string] { const id = generateId(); await db.chats.insert({ id, messages: [] }); return id; } export async function loadChat(id: string) { / validate id, return messages / } export async function saveChat({ id, messages }) { / upsert / }
Client:
const { messages, sendMessage } = useChat({ id: chatId, messages: initialMessages, // loaded server-side transport: new DefaultChatTransport({ api: '/api/chat' }), });
Rules:
- Treat chat ids as opaque tokens. Validate the format before using them in file paths or queries; the docs use a strict alphanumeric-plus-dash regex and a startsWith containment check for file stores.
- Save on completion: hook the stream's onEnd (server) to persist the finished messages. Saving only on send loses the assistant's half of the turn.
- On load, repair incomplete tool rounds. A persisted history with a dangling tool call throws MissingToolResultsError on the next send. Filter or complete the round at load time.
- In v7, system-role messages in persisted history are rejected unless allowSystemInMessages is true. Prefer instructions at the top level; migrate old histories.
- Pass the chat id to useChat so the resume machinery and your store agree on identity.
- This guide intentionally skips auth. In production, scope every store operation to the authenticated user or chats leak across accounts.
When to use
You hit exactly this: Chat message persistence: store, load, and resume conversations in Chat message persistence.
When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.
Compatibility
Chat message persistence (versions mentioned here: v7).
Evidence
Verified against the live AI SDK docs 2026-09-26. The message-persistence guide documents the createChat plus redirect pattern, generateId from ai, the file-store implementation with chat-id validation, and seeding useChat with loaded messages. The errors reference documents MissingToolResultsError for dangling tool rounds.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_fNZUI5g2eg3FJbt2fHTuLg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Chat message persistence: store, load, and resume conversations <span>— Vectle</span></a>