Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions .changeset/gorgeous-dingos-join.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
---
'ai': patch
---

feat(ai): add convertDataPart option to convertToModelMessages

Add optional convertDataPart callback for converting custom data parts (URLs, code files, etc.) to text or file parts that models can process. Fully type-safe using existing UIMessage generics.
Original file line number Diff line number Diff line change
Expand Up @@ -41,9 +41,9 @@ export async function POST(req: Request) {
},
{
name: 'options',
type: '{ tools?: ToolSet }',
type: '{ tools?: ToolSet, convertDataPart?: (part: DataUIPart) => TextPart | FilePart | null }',
description:
'Optional configuration object. Provide tools to enable multi-modal tool responses.',
'Optional configuration object. Provide tools to enable multi-modal tool responses, and convertDataPart to transform custom data parts into model-compatible content.',
},
]}
/>
Expand Down Expand Up @@ -87,3 +87,144 @@ const result = streamText({
```

Tools can implement the optional `toModelOutput` method to transform their results into multi-modal content. The content is an array of content parts, where each part has a `type` (e.g., 'text', 'image') and corresponding data.

## Custom Data Part Conversion

The `convertToModelMessages` function supports converting custom data parts attached to user messages. This is useful when users need to include additional context (URLs, code files, JSON configs) with their messages.

### Basic Usage

By default, data parts in user messages are filtered out during conversion. To include them, provide a `convertDataPart` callback that transforms data parts into text or file parts that the model can understand:

```ts filename="app/api/chat/route.ts"
import { openai } from '@ai-sdk/openai';
import { convertToModelMessages, streamText } from 'ai';

type CustomUIMessage = UIMessage<
never,
{
url: { url: string; title: string; content: string };
'code-file': { filename: string; code: string; language: string };
}
>;

export async function POST(req: Request) {
const { messages } = await req.json();

const result = streamText({
model: openai('gpt-4o'),
messages: convertToModelMessages<CustomUIMessage>(messages, {
convertDataPart: part => {
// Convert URL attachments to text
if (part.type === 'data-url') {
return {
type: 'text',
text: `[Reference: ${part.data.title}](${part.data.url})\n\n${part.data.content}`,
};
}

// Convert code file attachments
if (part.type === 'data-code-file') {
return {
type: 'text',
text: `\`\`\`${part.data.language}\n// ${part.data.filename}\n${part.data.code}\n\`\`\``,
};
}

// Other data parts are ignored
},
}),
});

return result.toUIMessageStreamResponse();
}
```

### Use Cases

**Attaching URL Content**
Allow users to attach URLs to their messages, with the content fetched and formatted for the model:

```ts
// Client side
sendMessage({
parts: [
{ type: 'text', text: 'Analyze this article' },
{
type: 'data-url',
data: {
url: 'https://example.com/article',
title: 'Important Article',
content: '...',
},
},
],
});
```

**Including Code Files as Context**
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Love this, thanks for putting this together @Drew-Garratt 👏

Would it be worth to include an example here for toggling on custom tools that a user might turn on when sending the user message? In this way, it can be stored alongside the other user message parts inside the DB and one can easily restore this context when the user wants to edit the message later on.

Let users reference code files in their conversations:

```ts
convertDataPart: part => {
if (part.type === 'data-code-file') {
return {
type: 'text',
text: `\`\`\`${part.data.language}\n${part.data.code}\n\`\`\``,
};
}
};
```

**Selective Inclusion**
Only data parts for which you return a text or file model message part are included,
all other data parts are ignored.

```ts
const result = convertToModelMessages<
UIMessage<
unknown,
{
url: { url: string; title: string };
code: { code: string; language: string };
note: { text: string };
}
>
>(messages, {
convertDataPart: part => {
if (part.type === 'data-url') {
return {
type: 'text',
text: `[${part.data.title}](${part.data.url})`,
};
}

// data-code and data-node are ignored
},
});
```

### Type Safety

The generic parameter ensures full type safety for your custom data parts:

```ts
type MyUIMessage = UIMessage<
unknown,
{
url: { url: string; content: string };
config: { key: string; value: string };
}
>;

// TypeScript knows the exact shape of part.data
convertToModelMessages<MyUIMessage>(messages, {
convertDataPart: part => {
if (part.type === 'data-url') {
// part.data is typed as { url: string; content: string }
return { type: 'text', text: part.data.url };
}
return null;
},
});
```
Loading
Loading