feat(ai): experimental_transcribe({maxDownloadSizeInBytes})

[gr2m]

Background

Summary

Manual Verification

Checklist

• Tests have been added / updated (for bug fixes / features)
• Documentation has been added / updated (for bug fixes / features)
• A patch changeset for relevant packages has been added (for bug fixes / features - run pnpm changeset in the project root)
• Formatting issues have been fixed (run pnpm prettier-fix in the project root)
• I have reviewed this pull request (self-review)

Future Work

Related Issues

[lgrammel]

Could affect generate/stream text/object url downloads

[gr2m]

Could affect generate/stream text/object url downloads

I confirmed that it e.g. applies to this example, without a way to set a max download size.

await generateText({
    model: openai('gpt-4o'),
    messages: [
      {
        role: 'user',
        content: [
          { type: 'text', text: 'Describe the image in detail.' },
          {
            type: 'image',
            image:
              'https://github.com/vercel/ai/blob/main/examples/ai-core/data/comic-cat.png?raw=true',

            // OpenAI specific option - image detail:
            providerOptions: {
              openai: { imageDetail: 'low' },
            },
          },
        ],
      },
    ],
  });

should we add maxDownloadSizeInBytes to all the methods exported by ai that might do downloads?

[lgrammel]

Could affect generate/stream text/object url downloads

I confirmed that it e.g. applies to this example, without a way to set a max download size.

await generateText({
    model: openai('gpt-4o'),
    messages: [
      {
        role: 'user',
        content: [
          { type: 'text', text: 'Describe the image in detail.' },
          {
            type: 'image',
            image:
              'https://github.com/vercel/ai/blob/main/examples/ai-core/data/comic-cat.png?raw=true',

            // OpenAI specific option - image detail:
            providerOptions: {
              openai: { imageDetail: 'low' },
            },
          },
        ],
      },
    ],
  });

should we add maxDownloadSizeInBytes to all the methods exported by ai that might do downloads?

Adding maxDownloadSizeInBytes to all methods breaks encapsulation regarding download configuration and leads to unspecified behavior with custom download functions.

instead I'd prefer if we could expose our download function somehow, with the max download size as an option (but there will be a naming conflict with the upcoming download for the files api that we need to solve).
users can then choose custom download functions (our download function configured with a different limit) and the concepts stay clearly separated.

[gr2m]

closing in favor of #12445