Over the past few months I installed every public drop of the Sitecore Stream module for XP and XM on one clean XP 10.4 instance, upgrading in place each time. Here is a chronological recap of what changed, with links to the official release blogs for deeper detail.
First public release - Version 1.0.113 (19 February 2025)
The first package required two client credentials in ConnectionStrings.config and two extra settings, OrganizationId and RegionName, in Sitecore.AiClient.config. After those values were present the red-star icon showed up next to Single-Line, Multi-Line and Rich-Text fields, enabling AI-assisted content generation directly inside the Content Editor. Read the 1.0.113 blog
Single Brand Kit and bugfixes release - Version 1.1.34 (20 March 2025)
Authentication was simplified to just the client ID and secret, but anyone who wanted branded content still had to add an Organization ID and a Brand Kit ID to Sitecore.AiClient.config. That manual step felt worthwhile because branded prompts finally produced text in a consistent voice, an improvement many early testers had been waiting for since day one. Although only a single Brand Kit could be wired in at this stage, the ability to steer tone and terminology made Stream far more usable for real marketing scenarios. Read the 1.1.34 blog
Multiple Brand Kits and Content Variants release - Version 1.1.63 (24 April 2025)
Brand Kit IDs vanished from the config because the dialog now queries the API and lists available kits in a dropdown. The same build let me request up to five variants for each prompt through a simple number selector. After upgrading I opened the dialog for the first time and saw an endless spinner, caused by a cached AiClient.js file. I reported the issue so the team could track it. Read the 1.1.63 blog
Site Item Translation release - Version 1.2.45 (5 June 2025)
This release introduced Stream Translate, which can create or update all language versions of an item in one action. The translation dialog saves the item immediately, while the original content-generation dialog still waits for a manual save. I reported this inconsistency so it can be addressed. My earlier AiClient.js cache issue is now documented in the module’s issues.md file together with a hard-refresh workaround. Read the 1.2.45 blog
Closing note
Across four releases, Sitecore Stream has made steady progress. What started with manual setup using hard-coded IDs has become much more streamlined, with features like API-driven Brand Kit selection removing the need for extra configuration. Alongside that, functionality has expanded with multi-variant content generation and full item translation. The module now feels mature enough that we confidently demo the latest version to customers. I will keep upgrading as new builds arrive and plan to dive deeper into the functionality in a future post.