---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/application-development

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Build Agent and tools

# Build Agent and ServiceNow AI Platform tools {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 Build Agent and ServiceNow AI Platform tools

Build Agent is a powerful AI-driven development tool available in both ServiceNow Studio and the ServiceNow IDE that helps customers create and modify applications efficiently.
Each environment supports a distinct development style: ServiceNow Studio offers a UI-first, low-code, declarative approach focused on metadata, while the ServiceNow IDE provides a code-first, autonomous, conversational experience for full-stack app development.
This flexibility allows ServiceNow customers to select the environment best suited to their skill set and project needs.
Show full answer Show less  

## Key Features

* **ServiceNow Studio:** Designed for low-code builders and administrators, it emphasizes guided, iterative metadata creation with previews, diffs, and guardrails to ensure controlled changes.
* **ServiceNow IDE:** Tailored for pro-code developers, it supports conversational prompts to autonomously generate and edit complete scoped or global applications including UI and backend components, with advanced customization, debugging, and build/deploy workflows.
* **Interaction Models:** Studio uses guided steps with selectable modes such as guided, batch, or one-shot, while the IDE relies on chat-driven autonomous generation where users approve edits before deployment.
* **Change Control and Automation Scope:** Studio emphasizes strong guardrails and previews focused on platform metadata, whereas the IDE includes approval gates and end-to-end build and deploy pipelines supporting complex app creation and refactors.
* **Conversational Checkpoints:** Both environments support conversational checkpoints allowing users to roll back to previous states during development.

## Typical Workflow

* Configure settings including MCP server connections as needed.
* Open your chosen environment (Studio or IDE) and start a Build Agent conversation via chat.
* Describe requirements in natural language for Build Agent to parse and propose changes or new applications.
* Review and approve edits, diffs, and summaries before applying changes.
* Iterate until the desired metadata or code changes are finalized.
* Prompt Build Agent to create and run Automated Test Framework (ATF) tests, with options for auto troubleshooting and regression suite generation if failures occur.
* Build the application, verify results, and deploy; source control integration such as Git is supported.

## Choosing Between ServiceNow Studio and ServiceNow IDE

* Use **ServiceNow Studio** for metadata-centric, low-code, iterative development with strong previews and guardrails suitable for less technical users.
* Use **ServiceNow IDE** for code-centric, autonomous, full-stack development requiring advanced customization, debugging, and complex application builds, ideal for professional developers.

## Important Notes and Limitations

* Build Agent generates metadata compatible with ServiceNow Fluent; customers should verify artifact compatibility before approving changes.
* Feature availability and user interface details may vary by monthly release; verify behavior against your specific ServiceNow instance version.  
Compare how Build Agent behaves in ServiceNow Studio (UI-first, declarative workflows) versus the ServiceNow IDE (code-first, autonomous full-stack development), so you can choose the right environment for your task and audience.
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.{#vc-build-agent-studio-vs-ide__ba-sns-vs-ide-1-p}

## Audience and intent {#vc-build-agent-studio-vs-ide__id_h4z_wn1_53c}

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.
{#vc-build-agent-studio-vs-ide__ul_mys_tn1_53c}

## Key differences between ServiceNow Studio and the ServiceNow IDE {#vc-build-agent-studio-vs-ide__id_bzd_xn1_53c}

{#vc-build-agent-studio-vs-ide__comparison__entry__3}

| 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 |
[ ]

{#vc-build-agent-studio-vs-ide__comparison}  
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.

## Typical Build Agent workflow {#vc-build-agent-studio-vs-ide__studio-workflow}

A general workflow for using Build Agent in either ServiceNow Studio or the ServiceNow IDE is the following:

1. Make sure that everything you need is properly configured in the settings, such as supported MCP server connections. For more information, see [Build Agent configuration](https://servicenow-prod.fluidtopics.net/eYEDaezMo15Pay7Rpk4_~A "Build Agent connects your instance to AI-powered design workflows. Set up the required application and MCP server connections to start using it.").
2. Open ServiceNow Studio. Use the central chat area on the home page to start a new conversation, or select the Conversations icon ![]() in the Navigator panel to open an existing conversation.
3. Describe what to create or change in natural language.
4. Let Build Agent parse requirements and propose the application and files to create or modify.
5. Build Agent edits code or metadata or scaffolds a new application.
6. Review proposed edits, diffs, and summaries, and approve or adjust before applying changes. Review checkpoints and manual edit update sets. In ServiceNow Studio, view generated app details from the Apps tab, and inspect the source code from the Explorer tab.
7. Iterate until the desired metadata changes are complete. For more information, see [Supported metadata in Build Agent](https://servicenow-prod.fluidtopics.net/L093IWK7z5gescoGCm7vmA "Metadata and app file types that Build Agent can create and manage.").
8. Prompt Build Agent to create and run Automated Test Framework (ATF) tests to verify that the tests execute as expected. Depending on your configuration, Build Agent may ask you if you want to run ATF tests. If there are failures, auto troubleshooting triages the tests and produces a regression test suite that you can use to monitor app health.
9. Instruct Build Agent to build the application; verify results in the File Navigator or Metadata Explorer.
10. Deploy the application. If you're using source control, you can push to Git. For more information, see [Deploying what you built with Build Agent](https://servicenow-prod.fluidtopics.net/UfO9v7wOOeW1T_UazSmw1A "Learn about deployment methods and workflows for moving applications created with Build Agent from development to production environments. Choose the right deployment approach based on your application complexity and organizational requirements.").
{#vc-build-agent-studio-vs-ide__ol_srh_55h_b3c}  
For more information, see the following topics:

* [Get started with agentic development using Build Agent](https://servicenow-prod.fluidtopics.net/xAjO9cfq4Q4Brmgkq0kNeQ "Use Build Agent on the ServiceNow AI Platform to build apps agentically by executing complex configuration and development tasks through conversational prompts. This approach simplifies editing and creating ServiceNow applications and metadata such as tables, relationships, and access controls, without manual navigation.")
* [Agentic development app refinement in ServiceNow Studio](https://servicenow-prod.fluidtopics.net/PNw2muBJvcdHuJsWHSvUvA "ServiceNow Studio connects AI-generated apps to enterprise-grade solutions, where you can review, edit, and enhance your application in a dedicated development environment.")
* [Agentic development app refinement in the ServiceNow IDE](https://servicenow-prod.fluidtopics.net/XRlLa6kThCtmS0vgKBo~Sg "The ServiceNow IDE provides a VS Code, file-based editing experience with syntax highlighting, code completion, and real-time installing to your instance. Use this approach to harden generated, scaffolded apps into production-grade solutions.")
{#vc-build-agent-studio-vs-ide__ol_aqw_b2w_g3c}

## How to choose {#vc-build-agent-studio-vs-ide__id_tqn_141_53c}

Use ServiceNow Studio when you want to do metadata-centric, abstracted low-code development. ServiceNow Studio provides structured, metadata-focused changes with strong previews and guardrails in low-code builders.

Use the ServiceNow IDE when you want file system code-centric development. The ServiceNow IDE provides autonomous, end-to-end generation, complex refactors, and deeper debugging and code explanations.

## Notes and limitations {#vc-build-agent-studio-vs-ide__id_bpv_141_53c}

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.
{#vc-build-agent-studio-vs-ide__ul_zly_yn1_53c}