feat: add 'manual' SSE mode for runtime stream/non-stream decisions#42
Open
CatchMe2 wants to merge 2 commits into
Open
feat: add 'manual' SSE mode for runtime stream/non-stream decisions#42CatchMe2 wants to merge 2 commits into
CatchMe2 wants to merge 2 commits into
Conversation
This comment was marked as spam.
This comment was marked as spam.
Tony133
approved these changes
Jun 20, 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
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.
What
Adds a new
sse: 'manual'route mode (shorthandsse: 'manual'and object form{ kind: 'manual' }) that lets a handler decide at runtime whether to stream, without anyAccept-header negotiation.Why
OpenAI-compatible and other LLM APIs decide whether to stream based on the request body (
{ "stream": true }) rather than theAcceptheader — the client sends noAccept: text/event-streameither way.Behavior
'manual'skips Accept negotiation:reply.sseis always attached.reply.sse.send(...)) or returns a plain value. SSE headers commit lazily on the firstsend()/stream(), so a non-streaming return falls through to Fastify's normal JSON serialization uncorrupted.Resolves #16
Checklist
npm run test && npm run benchmark --if-presentand the Code of conduct