chore(agentation): drop cross-realm Response workaround - #62
Merged
smsunarto merged 1 commit intoAug 19, 2026
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.
bb 0.39 accepts a cross-realm Response from plugin HTTP routes, and this repo's engines now require bb >=0.39.0. The GET /events SSE route returns
new Response(stream, { headers })directly, and the realm-workaround comment is gone. SSE headers are unchanged. The /health route keepsc.jsonas ordinary Hono ergonomics.Verified: tsc clean, 71/71 agentation tests pass, and a live curl against the pinned dev bb instance returned 200 with
text/event-streamand streamed the hello frame.