support developer role in chat completions API#867
Merged
adilhafeez merged 1 commit intomainfrom Apr 3, 2026
Merged
Conversation
alex-paperspace
approved these changes
Apr 2, 2026
salmanap
approved these changes
Apr 3, 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
3 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.
Adds support for the
developermessage role in the OpenAI Chat Completions API.Problem
Clients sending
"role": "developer"(introduced by OpenAI for reasoning models like o1/o3) get a 400 error because Plano'sRoleenum only acceptedsystem,user,assistant, andtool.Changes
Developervariant to theRoleenum inopenai.rsdeveloperpasses through nativelydevelopermaps to system prompt (those providers don't have a developer role)developermessages filtered out same assystem(not used for routing decisions)