Repository navigation
fix: always use system messages for StepFun chat models - #252
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Step reasoning models could send the application prompt with the
developerrole because the generic Chat Completions compatibility defaults assume it is supported. SetsupportsDeveloperRole: falsethroughout Step model discovery and normalization so Step chat requests consistently usesystem, including custom models and stalemodels.jsonentries. Preserve other compatibility flags and caller-owned model data.Validation:
step-provider.test.tsandmodel-runtime-modify-models-compat.test.ts, including request-body assertions for domestic, overseas, and custom Step endpoints.pnpm run checkpassed, including formatting, lint, type checking, architecture checks, and the browser smoke gate.