Accessing Build Agent in ServiceNow Studio and the ServiceNow IDE

  • Release version: Australia
  • Updated June 9, 2026
  • 3 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Accessing Build Agent in ServiceNow Studio and the ServiceNow IDE

    Build Agent is an AI-powered development assistant available within both ServiceNow Studio and the ServiceNow IDE, enabling developers to create and update applications through either UI-first or code-first workflows. It supports Personal Development Instances (PDIs) with a consistent experience matching production environments and offers 25 prompts per PDI every 30 days. Access requires admin permissions and appropriate plugins installed.

    Show full answer Show less

    Build Agent Environments and Usage

    Build Agent supports two main development environments:

    • ServiceNow Studio: Best for low-code builders, admins, citizen developers, and business analysts focusing on metadata-driven, declarative workflows (tables, fields, business rules). It offers guided steps, previews, diffs, and strong change control using System Update Sets.
    • ServiceNow IDE: Ideal for pro-code developers preferring a code-first approach with TypeScript, React, and ServiceNow Fluent DSL. It features autonomous conversational generation, full-stack app creation, and integrated Git source control with local development options.

    Accessing and Using Build Agent

    Build Agent opens by default when launching ServiceNow Studio or the ServiceNow IDE. If not visible, it can be accessed via the status bar or the Sparkle icon in the application banner. The Build Agent chat panel facilitates creating or updating apps by entering prompts or selecting predefined options. Users can manage multiple chats and checkpoints, allowing them to track progress and revert to previous states during development.

    Key Differences Between ServiceNow Studio and ServiceNow IDE with Build Agent

    • Development Style: Studio is UI-first and metadata-centric, while IDE is code-first and conversational.
    • Users: Studio targets low-code builders and admins; IDE suits professional developers.
    • Automation Scope: Studio focuses on iterative metadata updates; IDE supports full app generation and deployment.
    • Change Control: Studio provides preview and diff guardrails; IDE requires user approval before build and deployment.
    • Source Control: Studio uses System Update Sets and linked repositories; IDE uses built-in Git with branching.

    Practical Considerations

    When choosing between Studio and IDE, consider your development style and project needs. Studio is optimal for iterative, low-code configuration and controlled edits, whereas IDE is suited for greenfield app creation, complex refactors, and debugging with autonomous code generation.

    Keep in mind:

    • Build Agent generates metadata compatible with ServiceNow Fluent; verify artifact compatibility before approval.
    • Feature availability and UI may vary with monthly releases; confirm behaviors against your instance version.

    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

    When you open ServiceNow Studio or the ServiceNow IDE, the Build Agent should appear by default. If it doesn't appear, If the panel isn't open, select Open Build Agent from the status bar in the corner of your browser.
    Note:
    • 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.
    Figure 1. Open Build Agent
    If Build Agent isn't open, open it from the status bar in the corner of your browser.

    Build Agent chat panel

    Use the Build Agent chat panel to create or update an app or app file. Make a selection to begin the chat, or enter a prompt.
    Figure 2. New chat panel
    Begin a conversation by selecting an option to create or update an app or app file.

    Continue your conversation in the chat panel until you're happy with the results.

    Table 1. Navigating the Build Agent chat panel
    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
    Note:
    You can do conversational checkpoints with Build Agent and roll back to the last conversation checkpoint in both ServiceNow Studio and the ServiceNow IDE.

    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.

    Choose the environment based on your skill set and the type of work:
    • 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.