--- sourceDocument: Brazil Build or modify applications sourceDocumentLink: https://www.servicenow.com/docs/r/application-development Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil 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: Brazil Updated September 10, 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 accessible via the ServiceNow IDE for code-first, autonomous full-stack development. It enables developers, admins, and business analysts to interact with ServiceNow through conversational prompts to create or modify platform metadata, applications, and interfaces efficiently. Show full answer Show less Access to Build Agent currently requires admin permissions and appropriate plugin installation. Users can start new conversations directly from ServiceNow Studio's chat interface or from related metadata records through the ServiceNow AI Platform. ## Key Features * **Dual Environment Access:** Build Agent is available both in ServiceNow Studio and the ServiceNow IDE, each tailored to different development styles: * **ServiceNow Studio:** Focuses on metadata-driven, low-code creation with guided workflows, previews, and diffs---ideal for admins and citizen developers. * **ServiceNow IDE:** Supports pro-code, conversational full-stack app generation and editing using TypeScript and React, with integrated source control and local development options. * **Conversation Handoff:** Seamlessly continue conversations from ServiceNow Otto to Build Agent within ServiceNow Studio without re-entering context, improving workflow continuity. * **Sandbox and PDI Support:** Build Agent can be used within Developer Sandboxes for isolated parallel development and on Personal Developer Instances (PDIs) with controlled prompt usage, ensuring consistent experiences across environments. ## Practical Considerations * Only admins currently have permission to use Build Agent, and required plugins must be installed to enable access. * Build Agent generates metadata compatible with ServiceNow Fluent; users should verify artifact compatibility before applying changes. * Feature availability and UI may vary between monthly ServiceNow releases; confirm behaviors aligned with your instance version. ## What to Expect ServiceNow customers can leverage Build Agent to accelerate app development and configuration through conversational interaction, whether adopting a low-code or pro-code approach. The tool provides controlled automation with previews and approval steps in ServiceNow Studio, or autonomous generation and deployment capabilities in the ServiceNow IDE, enhancing productivity and reducing manual effort. Integration with sandboxes and PDIs supports safe, isolated development and testing. 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 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 panel 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/iwIHTTPpxC5fhcjfPGFnJA "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/hm9Cf3hp~UMqo3Jgj_bB3Q "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/1P73Ydtc5TtZCGW2oQWCGw "Developer Sandboxes provide admins and delegated developers the ability to request, access, and manage individual sandboxes on top of the same underlying development instance. Delegated developers can write and merge code and configuration changes without the risk of their changes getting overwritten on the instance mid-development."). ## 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/0YM7GTG0RM~pHbutmT2qsQ "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/FGuvKutyI~bWEal6HdgZPA "Plan deployments and troubleshoot issues by learning about Build Agent constraints that affect deployment capabilities and performance.").