On this episode of Developer Passport, I sat down with Andrew Vitollo and Matt Ripley, the product managers behind ServiceNow Studio and Build Agent, to dig into what's new. And the headline is pretty simple: Build Agent now lives in ServiceNow Studio, it's running Claude Opus 4.6, and it can operate at the global scope level.
Let me break down why each of those things is a bigger deal than it sounds.
Build Agent Comes Home
If you've been using Build Agent in the IDE, you've probably already had this thought: "This is great, but what about Studio?" You weren't alone. Andrew told us that was one of the most common questions they got. And it makes sense. ServiceNow Studio is where the majority of the developer community actually works. It's the low-code home base that's been around for a while. The IDE was a natural starting point for Build Agent, but Studio is where the bulk of the ServiceNow developer community already lives.
With the Australia early access release, that changes. Build Agent is in ServiceNow Studio with full feature parity to the IDE, plus the new capabilities shipping in the March release. Going forward, both environments are on the same branch. You're not choosing between two different experiences anymore.
And this opens the door to more personas. The IDE was more of a pro-dev play. Studio is where citizen developers, low-code builders, and traditional ServiceNow admins live. Now they all get an agentic assistant that can plan, generate metadata, build applications, and package them for deployment.
What Can It Actually Do?
Andrew walked us through a demo app he'd built called "Campus Bytes," a food truck ordering app for office events. He whipped it up in about 30 minutes, which, if you've ever built a scoped app from scratch, you know is absurd.
Build Agent handled the tables, columns, business rules, script includes, and flows. Andrew also called out that it handles packaging and installation, so you're going from idea to working app without jumping between tools to get it deployed.
The full list of what Build Agent supports is growing fast. Andrew estimated 30-40% of the current supported components were added just in the March release. And if you're not sure what it can do, the advice from the PMs themselves was refreshingly direct: just ask Build Agent. It knows its own capabilities, and those capabilities are changing month to month.
One thing that came up in the live Q&A that I think is worth calling out: Build Agent isn't just a builder. It's running Claude Opus 4.6 under the hood. You can use it to brainstorm, refine requirements, analyze existing apps, add comments to code, generate README files, or suggest refactoring approaches. Think of it as a peer that happens to also know how to write business rules.
Global Scope Support Changes the Game
This is the one that made Andrew laugh when he started talking about it, because he knew how big it is. Build Agent can now operate at the global scope level.
For those outside the ServiceNow world, that might not mean much. But for ServiceNow developers, global scope is where most of the actual work happens. Custom apps are great, but the reality is that a huge amount of development on the platform involves extending and modifying out-of-the-box functionality that lives in global.
Andrew mentioned customers are already exploring use cases like converting global apps into scoped apps using Build Agent. That's the kind of tedious, error-prone migration work that used to take days of careful manual effort.
The Honest Take on Where It's At
I appreciated how candid both Andrew and Matt were about the current state. Andrew put it plainly: even with the previous model, you'd get an app that was maybe 70-80% of the way there. The remaining 20-30% still needs human attention to harden, debug, and polish.
But the gap is closing fast. Andrew had emoji rendering issues in his demo app. Two prompts later, fixed. That feedback loop of prompt, review, adjust is getting tighter with each release, and the new Claude Opus 4.6 model is a noticeable step up in reasoning and context handling.
Matt was equally honest about the roadmap. He said to expect half the items on it to ship sooner than planned and the other half to not ship at all. That kind of transparency is rare and welcome. The highlights they're targeting include live UI previews with real-time editing, a teachable skills framework so Build Agent can learn your company's coding standards, story-to-deployment SDLC condensing, and eventually, release-level execution where you're managing a team of agents rather than pair-programming with one.
Where to Go From Here
Build Agent in ServiceNow Studio requires the Australia early access family release. It hasn't hit PDIs yet, but the team is actively working on it along with a more lenient trial version for customers who don't have the AI for Creators entitlement.
In the meantime, upgrade your PDI to Australia at developer.servicenow.com and start getting familiar with the Studio experience. When Build Agent lands there, you'll be ready.
And if you missed any of the other Developer Passport episodes this week, you can catch the full series at devlink.sn/australia.
