Accessing Build Agent in ServiceNow Studio and the ServiceNow IDE
Summarize
Summary of Accessing Build Agent in ServiceNow Studio and the ServiceNow IDE
Build Agent is a development assistant available in both ServiceNow Studio and the ServiceNow IDE, enabling developers to create and update applications either through UI-first declarative workflows or code-first full-stack development. It requires an instance running Zurich Patch 8 or higher and is accessible on Personal Development Instances (PDIs), providing 25 prompts per 30-day cycle to support consistent development across personal and production environments.
Show less
Build Agent Environments
ServiceNow offers two environments for Build Agent usage, each tailored to different user roles and development styles:
- ServiceNow Studio: Best suited for AI platform developers, app owners, admins, citizen developers, and business analysts. It supports metadata-driven, declarative workflows focusing on tables, fields, business rules, and scripts, with deployment via System Update Sets and package installs. UI creation involves forms, lists, workspaces, and catalog items. Source control uses System Update Sets and linked repositories. No local development option.
- ServiceNow IDE: Designed for developers preferring a code-first approach using TypeScript, ServiceNow Fluent DSL, and React. Deployment uses the ServiceNow SDK with build, deploy, and install workflows. UI creation includes React UI pages and custom interfaces. Git-based source control with branching and local development via VS Code and the @servicenow/now-sdk are supported.
Accessing and Using Build Agent
When launching ServiceNow Studio or the ServiceNow IDE, Build Agent appears by default. If not visible, users can open it via the status bar or the application banner's Sparkle icon. Currently, only admin users with the necessary plugins installed have access.
The Build Agent chat panel facilitates creating or updating apps by entering prompts or selecting predefined options. The panel allows starting new chats, viewing previous chats, and managing checkpoints, which are progress points in the app development that enable reverting to earlier states.
Key Differences Between ServiceNow Studio and ServiceNow IDE
| Aspect | ServiceNow Studio | ServiceNow IDE |
|---|---|---|
| Primary Style | UI-first, declarative, metadata-centric | Code-first, conversational, full-stack |
| Typical Users | Low-code builders, admins | Pro-code developers |
| Interaction Model | Guided steps with suggestions, diffs, selectable modes (guided, batch, one-shot) | Chat-driven autonomous generation; user approves edits, then builds and deploys |
| Scope of Automation | Create/update platform metadata (tables, flows, experiences) with dependency awareness | Generate/edit entire scoped or global apps (UI and backend), explain or repair code, run queries, create documentation |
| Change Control | Strong guardrails; preview via Studio diff surfaces | Approval gates before writing; build and deploy workflow |
| Best Fit | Iterative configuration, edits, low-code delivery | Greenfield app creation, deep refactors, debugging, multi-artifact edits |
| Dependencies | Uses Studio agentic experience layer and metadata explorers | Relies on IDE workspace, file and metadata explorers, and build pipeline |
Notes and Limitations
- Build Agent generates metadata compatible with ServiceNow Fluent; verify artifact compatibility prior to approval.
- Feature availability and UI may vary between monthly releases; verify behavior against your instance version.
- Conversational checkpoints and rollback capabilities are available in both Studio and IDE.
Build Agent is available in ServiceNow Studio (UI-first, declarative workflows) and the ServiceNow IDE (code-first, autonomous full-stack development).
You can watch a short video on how to access Build Agent in ServiceNow Studio.
Build Agent and PDIs
You can access Build Agent on a Personal Development Instance (PDI). Developers using PDIs get 25 prompts per instance per 30-day cycle.
PDIs are updated to match the latest Build Agent for a consistent experience across both personal and production-track instances. Developers testing and building on PDIs have access to the same capabilities available in production environments. For more information on PDIs, see Personal developer instance guide.
Opening Build Agent
- Currently, only admins have permissions to use Build Agent.
- You must have the correct plugins installed to access Build Agent. For more information, see Install Build Agent.
- Build Agent is available in ServiceNow Studio for Zurich Patch 8 and forward.
Build Agent chat panel
Continue your conversation in the chat panel until you're happy with the results.
| Function | Description |
|---|---|
New chat icon  | Open a new chat in the Build Agent chat panel. Begin a new chat when you want to start working on a new application or need a fresh start for updates. |
Chats icon  | See a list of all your chats with Build Agent. |
Checkpoints icon  | See a list of all the checkpoints within your current chat with Build Agent. Checkpoints show all the progress points in your application. You can revert to any of these checkpoints during the course of developing your app. |
Key differences between ServiceNow Studio and the ServiceNow IDE
| Area | ServiceNow Studio | ServiceNow IDE |
|---|---|---|
| Primary style | UI-first, declarative, metadata-centric | Code-first, conversational, full-stack |
| Typical users | Low-code builders, admins | Pro-code developers |
| Interaction model | Guided steps with suggestions, diffs, and summaries; selectable modes (guided, batch, one-shot) | Chat-driven autonomous generation; user approves edits, then build and deploy |
| Scope of automation | Create or update platform metadata (tables, flows, experiences) with dependency awareness | Generate and edit entire scoped or global apps (UI and backend), explain or repair code, run queries, create documentation |
| Change control | Strong guardrails; preview via ServiceNow Studio diff surfaces | Approval gates before writing; build and deploy workflow in the ServiceNow IDE |
| Best fit | Iterative configuration, edits, low-code delivery | Greenfield app creation, deep refactors, debugging, multi-artifact edits |
| Dependencies | Uses the ServiceNow Studio agentic experience layer and metadata explorers | Relies on the ServiceNow IDE workspace, file and metadata explorers, and build pipeline |
Build Agent is available in both ServiceNow Studio and the ServiceNow IDE, but each environment emphasizes a different development style. ServiceNow Studio provides a guided, UI-first experience that focuses on metadata creation and controlled, iterative changes. The ServiceNow IDE provides a code-first experience with an autonomous agent capable of generating and modifying full-stack applications through conversational prompts.
- ServiceNow Studio: Low-code builders and admins who prefer declarative, metadata-driven workflows with previews, diffs, and guardrails.
- ServiceNow IDE: Pro-code developers who need conversational, code-centric generation, advanced customization, and end-to-end build and deploy steps.
Notes and limitations
Keep the following in mind when using Build Agent:
- Build Agent generates metadata supported by ServiceNow Fluent. Verify artifact compatibility before approval.
- Feature availability and UI details might differ between monthly releases. Confirm behavior against your instance version.
For more information on limitations, see Build Agent limitations.