--- sourceDocument: Australia Build or modify applications sourceDocumentLink: https://www.servicenow.com/docs/r/australia/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 --- # Accessing Build Agent # Accessing Build Agent in ServiceNow Studio {#ariaid-title1} Release version: Australia Updated September 2, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 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 Accessing Build Agent in ServiceNow Studio Build Agent is integrated into ServiceNow Studio to support UI-first, declarative workflows and is also available within the ServiceNow IDE for code-first, autonomous full-stack development. It enables users to interact via chat to create or modify applications using metadata or code, depending on the environment chosen. Access to Build Agent currently requires admin permissions and appropriate plugins. Conversations with Build Agent can be initiated directly from ServiceNow Studio or by right-clicking artifacts in the ServiceNow AI Platform. Show full answer Show less ## Access and Usage * **Opening Build Agent:** Available on the ServiceNow Studio home page chat area or via the Conversations icon in the Navigator panel. * **Permissions:** Limited to admins with required plugins installed. * **Starting Sessions:** You can begin sessions with an active working set loaded by configuring metadata artifacts from the ServiceNow AI Platform. * **Sandboxes and PDIs:** Supports use within Developer Sandboxes for isolated development and is available on Personal Development Instances (PDIs) with a prompt limit of 25 per 30-day cycle. ## Build Agent Environments and Development Styles | Environment | Best For | Development Style | Deployment | UI Creation | Source Control | Local Development | |-|-|-|-|-|-|-| | ServiceNow Studio | AI Platform developers, app owners, admins, citizen developers, business analysts | Metadata-driven, UI-first, declarative workflows | System Update Sets | Forms, lists, workspaces, catalog items | System Update Sets; linked repositories | No | | ServiceNow IDE | Developers preferring IDE, TypeScript, ServiceNow Fluent workflows | Code-first, conversational, full-stack (TypeScript, React) | ServiceNow SDK build, deploy, install | React UI pages and custom interfaces | Git with branching | Yes, via VS Code with @servicenow/now-sdk | ## Key Differences Between ServiceNow Studio and ServiceNow IDE * **ServiceNow Studio:** Focuses on guided, metadata-centric, low-code development with guardrails and preview capabilities, suitable for iterative configuration and edits. * **ServiceNow IDE:** Supports autonomous, chat-driven, code-centric development ideal for greenfield app creation, debugging, and complex refactoring. * **Change Control:** Studio offers strong preview and diffs; IDE includes approval gates and build/deploy workflows. * **Automation Scope:** Studio automates metadata updates; IDE can generate and modify full scoped or global apps. * **Dependency Management:** Studio uses agentic experience layer and metadata explorers; IDE relies on workspace, file explorers, and build pipelines. ## Conversation Handoff from ServiceNow Otto Build Agent supports seamless continuation of conversations initiated in ServiceNow Otto. When transitioning, a handoff record containing a versioned summary and full transcript reference is created. ServiceNow Studio uses this record to open Build Agent with the context pre-loaded as an editable prompt. Users must review and submit this prompt to proceed. This feature requires access to both ServiceNow Otto and Build Agent and must be used within ServiceNow Studio. ## Notes and Limitations * Build Agent generates metadata compatible with ServiceNow Fluent; verify artifact compatibility before approval. * Feature availability and UI may vary between monthly releases; users should confirm behavior against their instance version. * For detailed limitations, consult the Build Agent limitations documentation. Build Agent is available in ServiceNow Studio for UI-first, declarative workflows. You can also use Build Agent the ServiceNow IDE within ServiceNow Studio for code-first, autonomous full-stack development. ## Opening Build Agent {#access-build-agent__section_vfx_b41_53c} When you open ServiceNow Studio, the central chat area on the home page is where you chat with Build Agent to start a new conversation. Figure 1. Build Agent panel in ServiceNow Studio To open an existing conversation, select the Conversations icon ![]() in the Navigator panel. The Build Agent panel then opens on the left.Figure 2. Build Agent in ServiceNow Studio 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](https://www.servicenow.com/docs/EROeC9~Du7I~voFiDV8Z~w "For the Premium version of Build Agent, install the ServiceNow Otto for Creator application from the ServiceNow Store."). {#access-build-agent__ul_ccn_prg_53c} You can start a Build Agent session with an active working set already loaded by right-clicking an artifact in the ServiceNow AI Platform, which displays a list of related metadata that you can edit. Then select the Configure option, which opens the record in ServiceNow Studio. From there, you can start a new Build Agent conversation about what you want to do with the metadata. ## Build Agent environments {#access-build-agent__section_env_comparison} You can use Build Agent in both ServiceNow Studio, which contains the ServiceNow IDE if you want to create apps in source code. For more information, see [Building apps in source code in ServiceNow Studio](https://www.servicenow.com/docs/azwUD18~uE3jVxICjCF0rw "Developing and maintaining applications in source code enables you to create and modify complex applications, manage code in source control more easily, and catch errors at build time."). Your choice on where to access Build Agent depends on your role and workflow. {#access-build-agent__table_build-agent-environments__entry__3} | Usage | ServiceNow Studio | ServiceNow IDE | |-|-|-| | Generally best for | ServiceNow AI Platform developers, app owners, admins, citizen developers, and business analysts | Developers who prefer using an IDE on platform, TypeScript, and ServiceNow Fluent workflows | | Code approach | Metadata-driven (tables, fields, business rules, scripts); embedded Build Agent | ServiceNow Fluent DSL (.now.ts files), TypeScript, React | | Deployment | System Update Sets; ServiceNow Studio package and install | ServiceNow SDK build, deploy, and install | | UI creation | Forms, lists, workspaces (Next Experience), and catalog items | React UI pages and custom interfaces | | Source control | System Update Sets; source control via linked repositories | Git built-in with branching | | Local dev option | No; runs on the instance | Yes, VS Code with `@servicenow/now-sdk` | [Table 1. Build Agent environments] {#access-build-agent__table_build-agent-environments} ## Key differences between ServiceNow Studio and the ServiceNow IDE {#access-build-agent__id_h3n_m41_53c} {#access-build-agent__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 | [ ] {#access-build-agent__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. 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. {#access-build-agent__ul_mys_tn1_53c} ## Handing off ServiceNow Otto conversations to Build Agent {#access-build-agent__section_t5p_11y_zjc} You can continue a ServiceNow Otto conversation from another product in Build Agent without repeating your intent. When ServiceNow Otto detects that you want to build or modify an application, it creates a handoff record. ServiceNow Studio then uses that handoff record to open Build Agent with your conversation context already loaded. The handoff record stores a versioned summary of the conversation and a reference to the full transcript. ServiceNow Studio reads the handoff record and opens Build Agent with the summary pre-filled as an editable prompt in the chat panel. When that happens, Build Agent doesn't run automatically. You must review and edit the pre-filled prompt before submitting it. The full ServiceNow Otto transcript is attached to the session so you can reference details from the original conversation that the summary doesn't include. Note: To use conversation handoff: * You must have access to both ServiceNow Otto® and Build Agent. * You must be working in ServiceNow Studio. {#access-build-agent__ul_nsv_bby_zjc} ## Build Agent and sandboxes {#access-build-agent__section_w2v_hrx_zjc} Use Build Agent in an isolated development environment with Developer Sandboxes. Sandboxes provide parallel development for distributed developers, with isolated metadata and Git integration. For more information, see [Developer Sandboxes](https://www.servicenow.com/docs/8n5o1hEPYqgl19r~ioAcOw "Developer Sandboxes are isolated development environments on a shared instance. Delegated developers use them to build and merge changes in parallel, and admins request and manage them."). ## Build Agent and PDIs {#access-build-agent__section_kpl_4lx_x3c} 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](https://www.servicenow.com/docs/zYU4E4RsssMJufmUKWiAaQ "ServiceNow offers free personal developer instances (PDIs) to Developer Program members to learn, explore, and experiment with the ServiceNow AI Platform."). ## Notes and limitations {#access-build-agent__id_izr_m41_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. {#access-build-agent__ul_zly_yn1_53c} For more information on limitations, see [Build Agent limitations](https://www.servicenow.com/docs/tJefqUrK5yuP8~N~Rk816g "Plan deployments and troubleshoot issues by learning about Build Agent constraints that affect deployment capabilities and performance.").