-
Notifications
You must be signed in to change notification settings - Fork 3.5k
chore (ai): rename CoreMessage to ModelMessage #6105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nicoalbanese
approved these changes
May 2, 2025
samdenty
added a commit
that referenced
this pull request
May 2, 2025
* origin/v5: fix(providers/openai): logprobs for stream alongside completion model (#6091) chore (ai): move maxSteps into UseChatOptions (#6113) docs (ai): add notes on schema .optional() (#6111) chore: update references to use ai-sdk.dev (#6076) (#6107) Version Packages (canary) (#6069) chore (provider-utils): rename TestServerCall.requestBody to requestBodyJson (#6106) chore (ai): rename CoreMessage to ModelMessage (#6105) feat (ai): add filename to file ui parts (#6104) feat (docs): add Dify community provider (#4084) (#6067) (#6103) feat (docs): add Sarvam community provider (#6079) (#6096) fix(providers/openai): zod parse error with function (#6074) (#6095) feat(docs): add Weave observability provider (#6029) (#6094) core (ai/mcp): update experimental MCP client documentation for Streamable HTTP transport usage (#5972) (#6093) fix (docs): update formatting in useChat reference docs (#6100) chore (ai): replace useChat attachments with file ui parts (#6071) feat (ui/react): support resuming an ongoing stream (#6053) test (openai): update snapshot (#6086)
samdenty
added a commit
that referenced
this pull request
May 2, 2025
…call * origin/v5: (43 commits) chore (provider-utils): return IdGenerator interface (#6118) chore (provider): improve jsdoc comments (#6117) chore (ai): remove outdated typecasts (#6116) chore (ai): remove useChat keepLastMessageOnError (#6114) fix(providers/openai): logprobs for stream alongside completion model (#6091) chore (ai): move maxSteps into UseChatOptions (#6113) docs (ai): add notes on schema .optional() (#6111) chore: update references to use ai-sdk.dev (#6076) (#6107) Version Packages (canary) (#6069) chore (provider-utils): rename TestServerCall.requestBody to requestBodyJson (#6106) chore (ai): rename CoreMessage to ModelMessage (#6105) feat (ai): add filename to file ui parts (#6104) feat (docs): add Dify community provider (#4084) (#6067) (#6103) feat (docs): add Sarvam community provider (#6079) (#6096) fix(providers/openai): zod parse error with function (#6074) (#6095) feat(docs): add Weave observability provider (#6029) (#6094) core (ai/mcp): update experimental MCP client documentation for Streamable HTTP transport usage (#5972) (#6093) fix (docs): update formatting in useChat reference docs (#6100) chore (ai): replace useChat attachments with file ui parts (#6071) feat (ui/react): support resuming an ongoing stream (#6053) ...
iteratetograceness
pushed a commit
to iteratetograceness/ai
that referenced
this pull request
May 9, 2025
## Background The name `CoreMessage` was an artifact of needed to introduce a separate message type. Over time it became clear that we have threee distinct message types: - messages used on the client that are displayed to the user (`UIMessage`) - messages that are sent to our user-facing APIs (currently `CoreMessage`) - messages that are sent to the providers (`LanguageModelV2Message`) They all have distinct DX considerations and are different by design. The name `CoreMessage` is not clear here. ## Summary Rename `CoreMessage` to `ModelMessage` to make the distinction `UIMessage <> ModelMessage` clear (most users are not exposed to internal provider messages). ## Future Work `CoreMessages` and related types and functions are deprecated and will be removed in AI SDK 6
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
The name
CoreMessagewas an artifact of needed to introduce a separate message type. Over time it became clear that we have threee distinct message types:UIMessage)CoreMessage)LanguageModelV2Message)They all have distinct DX considerations and are different by design.
The name
CoreMessageis not clear here.Summary
Rename
CoreMessagetoModelMessageto make the distinctionUIMessage <> ModelMessageclear (most users are not exposed to internal provider messages).Future Work
CoreMessagesand related types and functions are deprecated and will be removed in AI SDK 6