https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FTBGdylwDeL8%3Ffeature%3Doembed&display_name=YouTube&url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DTBGdylwDeL8&image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FTBGdylwDeL8%2Fhqdefault.jpg&type=text%2Fhtml&schema=youtube

 

Ladies and gentlemen: we have made it to the grand finale of Developer Passport Brazil, and I couldn't think of a better product to bring it all home than the home for all developer tooling: ServiceNow Studio. I had the pleasure of being joined by returning Dev Passport presenter, Principal Inbound Product Manager, Matthew Ripley, to showcase all of the new features and enhancements.  

 

ServiceNow Studio is your on-platform home for building: the experience layer that sits right next to Build Agent and centralizes everything a developer needs into one place. No bouncing between the app navigator, the form view, and your IDE. If you're building on the Now Platform, Studio is where you live. Here are some highlights from what we covered.

 

A Homepage That's Gone All-In on Agentic

The September release homepage puts Build Agent front and center, literally. ServiceNow Studio's team stripped out the old recent-apps/recent-files clutter in favor of a clean, focused "vibe mode." Don't worry, nothing's gone; you can pop into preferences and customize your activity bar to bring back collections, file categories, or your recents whenever you want them.

 

Oh, and it's built on Lux , ServiceNow's new AI-native UI framework (yes, the same one I demoed dark mode for earlier that day  👀). Lux rolls out iteratively across the platform starting big in Q4 and running through early 2027, so keep your eyes open — this homepage is just the beginning.

 

New Entry Points Straight Into Studio

Small button, big drum roll: platform records now have an "Open in Studio" option, and the right-click configure menu (say, on an incident's related business rules) drops you directly into Studio instead of a plain list view. Want the old behavior back? There's a toggle for that. Expect more of these entry points to show up across core platform as auto and other tools start routing dev use cases straight to Build Agent.

 

Pro-Code Capabilities, Now Living in Studio

This is where the IDE and Studio start sharing DNA. Since replatforming on VS Code, Studio has picked up:

• Access to source code via a built-in explorer: see the actual source behind apps you've converted to Fluent
• Source Control V2:  link an app to an external repo, stage and sync changes, and push straight from Studio

Matthew told the story of migrating his (very real) fasting-tracker app built with Build Agent, iterated on through ~20 checkpoints, from an old instance to a new one by converting it to Fluent and syncing it through source control V2. One heads-up if you're running delegated development: converting to Fluent currently limits access to admin users only. Non-admin access to Fluent and BuildAgent is on the roadmap, so hold off converting anything delegated devs rely on until that lands.

 

IDE stays a standalone product — this isn't replacing it. It's Studio borrowing the pro-code muscle so you don't have to leave to get it.

 

The Mission, In Matthew's Words

Agentic development is moving fast, and the whole point of Studio is that you don't have to keep up with every shift to benefit from it. Simple, consumable, most-valuable-features-up-front — with the human always in the loop and the agent working as an extension of the developer, not a replacement for one.

 

Recap

Four big enhancements landed for Studio in Brazil:

1. Simplified, agentic-first homepage (vibe mode)
2. Right-click entry points straight into Studio
3. Integrated pro-code capabilities (source Explorer)
4. Source Control V2

All four will be available on PDIs once Brazil ships there in the next couple weeks — keep an eye on the Dev Program channel and we'll shout when it's live.

 

Huge thanks to Matthew for coming back one more time to close out the Brazil Developer Passport in style.