I have been exploring SitecoreAI Agentic Studio recently. If you have not tried it yet, it is the AI workspace inside SitecoreAI where you can chat with pre-built agents, build your own, and chain them into multi-step workflows called Flows.
What Is Agentic Studio
When you open it, you see five sections: Actions (chat history), Agents (pre-built and custom agents), Flows (multi-step workflows), Signals (AI-driven trends and research), and Spaces (organized view of conversations and artifacts).
What I Tried
I started by opening a Chat and asking it to write a short blog post. That created a text artifact inside Studio. Then I created a Space from that conversation, which grouped everything together but did not change the artifact type.
Next I ran the Quote Extractor workflow against the blog content. That produced an extract artifact. Then I ran the Blog Writing Agent, which generated a content_item artifact with its originItemId pointing back to the Quote Extractor output.
The chain: Chat (text) > Space > Quote Extractor (extract) > Blog Writing Agent (content_item). None of these are real Sitecore CMS items.
The Apply Changes Issue
The Blog Writing Agent's output showed an "Apply Changes" button. That button implies you can push the content into a Sitecore page. But there is no Sitecore page behind this artifact. The originItemId points to the Quote Extractor output, which is an internal Studio artifact. The componentMap is null. When I clicked the button, it did not work.
The UI should check whether the origin is a real Sitecore item before showing the button. If the origin is another Studio artifact, "Apply Changes" should be hidden or disabled.
Wrapping Up
Agentic Studio has a lot of potential. The chat, space, and workflow pipeline feels natural. I am planning to dig deeper into custom agents and Flows, and will share more as I go.
