Conversation
One record, topic, cursor, error family and provider protocol set that every provider and every context shares.
A provider is registered once as a plugin and the contexts that ask for a stream find it in their config.
Wire round trips, supersession, topic keys, cursors, body encoding and refs, with no provider involved.
This was referenced Oct 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
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.
This PR adds
temporalio.streams, the stream interface every provider and every context shares, with no provider yet.What changed?
temporalio.streams:StreamRecordover thetemporal.api.stream.v1envelope the previous PR brought in, typed topics, cursors withBEGINNINGandEND, theStreamErrorfamily, the provider protocols,StreamRef, and the body helpers that run a record's body through the data converter.ProviderPlugin, plusstream_provideron client, worker and replayer config. A provider is registered once and every context finds it there.Part of AI-198 (epic AI-37).
Why?
Workflow code, activities and clients should read and write a stream the same way, whatever store sits behind it. The interface is that contract. Landing it alone lets reviewers judge the shape before any provider or runtime code depends on it. The memory provider and the conformance suite follow in the next PR.
How did you test it?
Link to a test plan if any -
poe lintis clean. The type tests cover wire round trips, supersession, topic keys, cursors, body encoding and refs, and they pass. The client, worker, replayer and plugin suites still pass with the new config key.