fix: use application/json Content-Type for agent generate requests#34
Merged
fix: use application/json Content-Type for agent generate requests#34
Conversation
The response method was incorrectly setting Content-Type to text/plain while sending a JSON body. This caused the mastra server to not parse the body correctly, resulting in 'Argument messages is required' errors. This bug was present since the first commit but only became visible when the mastra server started strictly validating Content-Type headers.
oriolgual
approved these changes
Feb 6, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Problem
The
responsemethod inlib/ai/clients/mastra.rbwas settingContent-Type: text/plain;charset=UTF-8while sending a JSON body. This caused the mastra server to not parse the request body correctly, resulting inArgument 'messages' is requirederrors.Root Cause
The bug was present since the first commit (
9639eff- June 10, 2025) but only became visible when the mastra server started strictly validating Content-Type headers for body parsing.Fix
Changed line 290 from:
to:
Testing
Tested locally with meetings chat - the
Argument 'messages' is requirederror no longer occurs.