Repository navigation
feat: support developer and fallback message roles - #27
Merged
Merged
Conversation
sheepbox8646
marked this pull request as ready for review
July 21, 2026 16:14
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
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.
Summary
developeras a first-class SDK message role with constructor and JSON validationWhy
Runtime changes and other application instructions may occur after a conversation has started. Previously, some providers hoisted, dropped, or silently ignored these system messages, and the SDK had no semantic
developerrole. This made message ordering provider-dependent and could produce invalid requests when an instruction interrupted a tool-call/result exchange.Developer impact
Callers can now use
sdk.DeveloperMessage(...)and placesdk.SystemMessage(...)at the intended point in history. Providers serialize native roles when supported and otherwise apply deterministic user-role fallbacks without mutating caller messages.Validation
go test -short -count=1 ./...mise run test-racemise run lintmise run buildmise run vetgit diff --check