AI SDK migration guide

Choose your AI SDK migration path

The ai package is Vercel AI SDK. Start with the release you are moving to. Each guide names the changes Emendant covers, shows code before and after, and states what still needs your review.

• Migrate AI SDK 4.x to 5.0: React and RSC imports move, message types change, and tool() uses inputSchema.
• Migrate AI SDK 5.x to 6.0: old CoreMessage names are removed, and agent and tool names change.
• Migrate AI SDK 6.x to 7.0: experimental names, call options, stream results, and token usage fields change.

Check your repository before you upgrade

1. Check the installed ai version in your manifest and lockfile. Read the guide for the target release above.
2. Run npx emendant scan in your TypeScript or JavaScript repository. It reports supported changes at affected call sites without editing your files.
3. Review the findings, then run npx emendant fix --dry-run to inspect eligible patches. Emendant does not update package versions for you.
4. After you update dependencies, run your own typecheck and tests. Some migration steps need manual work or a model provider you name.

For a worked example, read one measured AI SDK 6 to 7 migration of a public repository. It gives every command from a pinned commit and feed snapshot, the patch Emendant wrote, the edits it left to the reader, and the changes it did not report.

Emendant reports only changes in its curated feed. A clean scan does not prove that every AI SDK migration step is complete. Read the supported projects guide for the current scope and the fix guide for patch grades.