Building applications

MCP connections enable Build Agent to access external tools and resources through standardized communication. Use these connections to integrate third-party applications like Figma for accelerated design-to-development workflows.

Autonomous Engineer is available in ServiceNow Studio. You access it through the Build Agent chat panel by switching the active mode to Autonomous Engineer.

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.

Open your PDI and start building in the instance.

By default, when application administration is enabled for a scoped application, ACL rules for the scoped application are applied. If no ACL rules for the scoped application are found, global ACL rules can apply.

Tool gates, approval patterns, and auto approval determine whether each action in Arc runs, requires approval, or is blocked.

With Action recorder, you can capture steps to automate repetitive tasks in AI Desktop Actions. You can save the steps that you perform on application elements as a reusable desktop action.

You can activate the Scoped Application Restricted Caller Access plugin (com.glide.scope.access.restricted_caller) if you have the admin role.

You can activate the ServiceNow Arc plugin (sn_app_cowork) for ServiceNow Arc if you have the admin role. If the application does NOT include demo data or it does NOT install related applications and plugins, delete or revise the following sentence:The application includes demo data and installs related ServiceNow Store applications and plugins if they aren't already installed.

Activate the ServiceNow Extensions for VS Code to be able to edit applications within your ServiceNow instance.

Activate your PDI plugin from the Developer Site to start working on an instance.

One option to get started using an instance is to activate a plugin directly for your PDI.

Adaptive path desktop actions automatically adjust their behavior based on user context and system conditions. Configure these settings to optimize desktop action performance and user experience across different scenarios.

Adaptive desktop actions adjust their execution based on user context and system conditions. Configure these settings to optimize desktop action performance and user experience across different scenarios for desktop and web-based tasks.

Configure AI Desktop Actions to execute predefined automation sequences on your desktop. Defined path actions provide consistent, repeatable workflows for common desktop tasks.

Reference known issues, limitations, and resolution steps for AI Desktop Actions on macOS.

Use this guide to determine which type of desktop action best fits your automation scenario before you begin configuration.

Add desktop action details, such as name, description, and associated applications, and review inputs and outputs.

Make a remote MCP server available to Arc users, so they can connect to it in one step without entering its details themselves.

Add pages to the navigation to make them accessible from other pages, such as a home page.

Add permissions to collaboration descriptors to manage your user's capabilities, such as the ability to delete the application or manage collaborators.

To develop a component for Virtual Agent, add specific properties and actions to interact with the Virtual Agent client interface. The properties required depend on the type of component you are creating.

Use Build Agent for a wide range of development scenarios beyond application creation, including app analysis, modernization, documentation, governance, and learning assistance.

Autonomous Engineer and Build Agent are separate products that work together. Autonomous Engineer uses Build Agent as its execution layer.

When Autonomous Engineer completes a turn, it updates the change log.

The Autonomous Engineer chat panel within Build Agent is where you interact with the AI agent during planning and development. Use it to submit requests, review responses, run tests, and apply generated code.

When all work items are complete, Autonomous Engineer generates an update set that you export and move through the standard ServiceNow deployment process.

Autonomous Engineer supports domain separation, allowing you to set the domain (sys_domain) and use sys_override on APIs and records that support it.

Governance controls for Autonomous Engineer are managed through Build Agent.

Limitations that apply to Build Agent also apply to Autonomous Engineer.

MCP connections enable Autonomous Engineer to access external tools and resources through standardized communication, extending the planning and implementation workflow with data and context from third-party systems.

The Autonomous Engineer dashboard displays the status of every work item in your plan and provides navigation to individual work items, milestones, and pre-flight verification items.

Access all Autonomous Engineer plans from the Plans view in the Build Agent panel. The Plans view shows the plans you created and all plans available on the instance.

Use Autonomous Engineer to author and manage Playbook Designer artifacts through a conversation. You can generate playbook structures, configure activities, set runtime permissions, and define launcher configurations without manually navigating the Playbook Designer UI.

Autonomous Engineer monitors background agents during execution and automatically detects and retries work items that get stuck or unresponsive.

Autonomous Engineer and Build Agent share the same configuration settings. Settings you configure for Build Agent also apply when Autonomous Engineer runs.

Autonomous Engineer accepts images, documents, code files, and file types specific to ServiceNow as uploads. Supported formats, size limits, and general guidelines apply when generating apps and metadata.

Metadata and app file types that Autonomous Engineer can create and manage.

Learn which AI models and versions Autonomous Engineer supports and how to change them. Use this information to verify compatibility and select the right model for your task.

Autonomous Engineer tools support application development tasks such as semantic search, schema inspection, code search, planning, UI validation, database querying, app navigation, and script execution. Each tool extends what Autonomous Engineer can do during a build session.

Test Agent generates test coverage for each work item that Autonomous Engineer builds, executes the tests, and performs root cause analysis (RCA) on failures.

When you work with Autonomous Engineer, your changes are automatically tracked in update sets so you can review, revert, and deploy them without leaving ServiceNow Studio.

Use Autonomous Engineer to provide requirements, review an implementation plan, and build all work items in parallel using background agents in Build Agent.

The Agent Chat Harness is the conversational AI interface built into Lux Lab. It uses the Agent Communication Protocol (ACP) to connect external AI agents to your project context.

Learn about the agentic app development approach, which tools you should use, and the AI-led software development life cycle on the ServiceNow AI Platform.

Execution workspace enables you to test, run, and monitor your desktop actions. It enables you to observe how your automations interact with desktop applications, including handling situations where human input is needed.

Learn about the terms and concepts that are unique to AI Desktop Actions.

ServiceNow AI Desktop Actions enables you to design, configure, and manage desktop actions that automate repetitive tasks in your desktop and web environment. AI agents can autonomously and semi-autonomously process instructions, generate execution plans, and run desktop actions across legacy systems, thick client applications, and web applications without APIs.

The Design workspace is an interactive environment within AI Desktop Actions that enables you to create desktop actions by recording and configuring user interactions with desktop applications. The workspace provides a visual canvas where you can design multi-screen automation workflows that capture business processes across different applications.

Reference topics provide additional information about the roles and tables that are installed with the AI Desktop Actions application.

The Agents and Skills panel is an explorer that surfaces all agents and skills available in your current project and on your system. It gives you a single place to check what is configured and ready to use.

Let an AI agent perform automated actions directly on your desktop across browsers, desktop applications, and files using AI Desktop Actions. You maintain control and can pause the automation at any time to review or adjust steps.

The AI Desktop Actions application includes a task input field, an execution workspace, and status indicators that show the current state of AI agent task execution.

AI Workflow Factory Prime enables you to discover, build, run, and extend on the ServiceNow AI Platform. From process and task mining, to agentic and sandbox development, use the AI Workflow Factory Prime capabilities to help your team move from idea to production faster.

Access the Credit Dashboard to learn about your AI Workflow Factory Prime credit usage.

The AI Workflow Factory Prime Credit Dashboard doesn't populate capability data on initial install. Use the following troubleshooting guide to resolve the issue.

Export the data from the Credit Dashboard to a .CSV report.

Configure a custom application [sys_app] in the now.config.json file for an application in source code.

Arc builds ServiceNow apps for you with the Now SDK, from planning the app to installing it on your instance, through a conversation in a chat.

App Engine is a ServiceNow AI Platform suite of products to help boost productivity by automating workflows.

Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.

The App Settings panel contains configuration for your profile, appearance, editor behavior, instance connection, integrations, and updates.

Protect sensitive application data by using application administration to restrict how users acquire application-specific roles.

People with admin privileges can manage the permissions of developers collaborating on an application.

Reference topics provide additional information about forms and options available through Application Runtime Policy.

Application Runtime Policy (ARP) is an opt-in, Zero Trust security framework for app creation and runtime that enforces fine-grained controls over accessing network, scripting, record, and platform resources. ARP provides automatic policy creation for applications in development, which helps simplify policy creation and the ServiceNow Store certification process.

Cross-scope privilege records define rules for access to application resources outside your application's scope. Application Runtime Policy generates cross scope privilege records automatically when your application attempts to access resources beyond its own scope.

When enabled, Application Runtime Policy operates in two possible modes: Tracking and Enforcing. Tracking mode automatically allows out-of-scope access attempts, while Enforcing mode automatically blocks out-of-scope access attempts until you review them.

Network policies allow list the external hosts and endpoints that an application is permitted to access. Application Runtime Policy (ARP) generates network policies automatically when your application attempts to connect to external networks during development.

Enable Application Runtime Policy for an application that's in development by setting the policy mode on the custom application form.

Quota configurations define limits on the resources that an application can use at runtime. Application Runtime Policy uses these limits to prevent a single application from consuming excessive platform resources.

Segment policies enable broad access patterns across one or more Application Runtime Policy segment without requiring granular policy records for each access. If your application requires segment policies, you must create them manually.

Assign collaboration descriptors to user groups for a specific application so that you can define specific permissions for these user groups.

Assign collaboration descriptors to your users for a specific application so that you can define specific permissions for these users.

Use ServiceNow Arc to complete multi-step work, such as investigating incidents, creating reports, or coordinating updates across platforms. Combine skills, sub-agents, and connectors in a single request so Arc can complete the whole piece of work from start to finish.

Create desktop actions by auto-capturing steps to automate repetitive tasks in AI Desktop Actions. You can save the steps that you perform on the application elements as a reusable desktop action of type on-screen task.

Reference information for Autonomous Engineer, including work item states, agent packs, and supported capabilities in Build Agent.

The ServiceNow Autonomous Engineer application is an agentic AI worker that builds applications from your requirements. It generates a plan with structured work items, and background agents build the work items in parallel.

Build Agent can generate agentic workflows, agents, and skills scoped to your custom app.

Agent packs bundle the domain knowledge, tools, and skills that Autonomous Engineer uses to implement ServiceNow products.

Autonomous Engineer is an agentic worker that augments product development capacity across the SDLC. It intakes requirements, applies platform best practices through agent packs, and generates an implementation plan before building work items in parallel through Build Agent.

The Build Agent chat panel is where you interact with the AI agent during development. Use it to submit requests, review responses, and apply generated code.

Configure test settings to enable automatic test prompting and execution of UI tests in Build Agent and Autonomous Engineer.

Create and manage custom skills and rules, or instructions to control how Build Agent behaves during a session. Rules are preloaded into every session automatically. Skills are available on demand when you or the agent invokes them by name.

Enable the web search tool so that Build Agent can search the public web and retrieve relevant information when responding to queries.

Connect a supported MCP server to Build Agent to access external tools and resources in the chat panel when building and editing apps.

The conversation change log tracks every change Build Agent makes to your application. It appears automatically in an integrated tab in ServiceNow Studio and lets you view updates, roll back to a previous checkpoint, and deploy changes to an update set.

Generate documentation for the structure, tables, and UI components of an application. Build Agent reads the codebase and creates a README file describing the application architecture.

If any conkeyrefs are broken, re-add them from the doc/source/reuse/domain-separation/domain-separation-overview.dita file.In the short description, edit the first sentence to state whether domain separation is supported or not and add the application name. Keep the conkeyref at the end that describes domain separation.Domain separation is supported for Build Agent. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.

Learn which AI models and versions Build Agent supports and how to change them. Use this information to verify compatibility and select the right model for your task.

Use Build Agent and Autonomous Engineer to author and manage Playbook Designer artifacts through a conversation. You can generate playbook structures, configure activities, set runtime permissions, and define launcher configurations without manually navigating the Playbook Designer UI.

System properties installed with Build Agent control operational settings and resource limits. Tables store conversation, message, checkpoint, and telemetry data. Roles define access control for properties and features.

Plan and work item states appear during planning and execution. Use this reference to identify where a plan or work item is in the execution process and what action is required.

Build Agent accepts images, documents, code files, and file types specific to ServiceNow as uploads. Supported formats, size limits, and general guidelines apply when generating apps and metadata.

When you work with Build Agent, your changes are automatically tracked in update sets so you can review, revert, and deploy them without leaving ServiceNow Studio.

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.

Explore example prompts for building apps, as well as adding governance, UI and other ServiceNow metadata to help you get started with prompting Build Agent.

Use these guidelines to get the most out of Build Agent in your development workflow.

Governance controls in Build Agent help with code quality, security, and compliance when generating applications. The Build Agent automated safeguards prevent common development issues and enforce organizational standards.

Plan deployments and troubleshoot issues by learning about Build Agent constraints that affect deployment capabilities and performance.

Plugins are required for Build Agent, and vary by version.

Reference topics provide additional information about using Build Agent to create and edit apps, as well as ServiceNow metadata.

Metadata and app file types that Build Agent can create and manage.

Test Agent generates test coverage for code created by Build Agent, executes tests, and performs root cause analysis (RCA) on failures. Prompt Test Agent to complete build-to-test workflows in a single development session without manual test authoring or failure investigation.

Build Agent tools support application development tasks such as semantic search, schema inspection, code search, planning, UI validation, database querying, app navigation, and script execution. Each tool extends what Build Agent can do during a build session.

Identify and resolve common issues in Build Agent.

Learn to develop reusable server-side logic and build a ServiceNow application in Build Agent, from data modeling through testing, using agentic development.

The Build Agent workflow automates building applications, testing, and deploying update sets on the ServiceNow AI Platform. Build Agent streamlines development by handling code compilation, quality checks, and deployment steps without manual intervention.

The ServiceNow Build Agent application is an autonomous AI agent that creates and updates ServiceNow applications from natural language prompts. You can also use Build Agent to get answers to general ServiceNow development questions.

Build and edit applications with agentic AI development tools available with AI Workflow Factory Prime.

Describe the app you need, approve the plan, and let Arc build the app, save its source to your computer, and install it on your instance.

Develop applications on the ServiceNow AI Platform using agentic and classic development approaches and tools. Build new applications or extend existing applications to fit the needs of your organization's unique workflows and processes.

Create tables and fields on the tables to support the application’s data model.

The next step in designing an application is to build logic. Logic includes form logic (what people can and cannot see/use on a form) and business logic (rules that govern what happens to data when it is entered).

You build a Lux app in code, starting from its pages. A page is a Lit web component that Lux registers as a route based on where you put its file.

Build and define the data, design elements, and logic that make up your application.

The ServiceNow AI Platform provides a robust set of builder tools that enable you to quickly develop applications for your organization.

Create and develop custom applications in source code using familiar development tools and processes.

Create and manage custom applications from scratch using classic pro-code tools.

Business rules are server-side actions that can be run during CRUD (Create, Read, Update, Delete) operations on instance records.

Application access settings determine whether one application can access resources from another application.

When application developers create new records, the system automatically assigns the records to the currently selected application in the application picker.

Application developers create tables and their associated lists and forms for users to add and update records.

Every custom application record includes a related list identifying its dependencies on other applications.

Administrators use application design access records to specify which other applications are available to developers during application creation.

Application files are configuration records that allow developers to extend application functionality.

The applications list allows application developers to view and select applications.

The application picker enables application developers to view and select the application scope where their changes apply.

Application scoping protects applications by identifying and restricting access to application files and data.

Each installed application has a version as defined by its application developer in the custom application record.

The UI displays the following visual indicators when configuring the layout of a custom application's list or form.

The platform is a contextual development environment that displays the currently selected application, identifies the scope of every application artifact, and prevents any changes that violate the access settings for an application.

The current application context determines what customization and form design options are available when working with lists and forms in scoped applications.

Runtime access tracking uses cross-scope privilege records to determine which script operations and targets the system allows to run.

The custom application record defines and identifies an application and all its associated artifacts.

By default, new application tables prevent other application scopes from creating configuration records on application data tables. This prevents any other applications from changing the functionality of a table.

The default runtime access permissions apply to new application data tables.

As the application developer, you can grant or deny other applications the permission to create configuration records, also known as application files, that extend the functionality of an application.

You can prevent other application scopes from creating configuration records on application data tables.

You can prevent script API and web service calls from other application scopes.

You can permit other application scopes to create configuration records on application data tables.

You can permit some or all runtime script API and web service calls from other application scopes.

A fix script is server-side JavaScript code that you run after an application is installed or upgraded.

The UI displays the following visual indicators when designing forms in custom applications.

The global scope is a special application scope that identifies applications developed prior to application scoping, or applications intended to be accessible to all other global applications.

The system adds a namespace identifier to the front of application artifacts such as tables, scripts, and configuration records.

Applications consist of several types of files and records that collectively deliver a service.

A read-only protection policy prevents anyone from modifying an application file or its related record.

The Application File Types table defines parent-child relationships between configuration records.

Runtime access determines if an API or web service call can run against an application table.

Runtime access tracking allows administrators to manage script access to application resources by creating a list of script operations and targets that the system authorizes to run.

Application developers can set a protection policy for script includes published as part of a custom application. The policy determines whether someone can view or edit the script include after the application is installed on their instance.

Administrators can share applications that are complete and are ready for use on other instances.

All production instances monitor and generate reports on usage patterns for ServiceNow Store apps. When subscription enforcement is enabled, users who are not subscribed to the app are blocked from performing fulfiller actions in the app.

The platform displays a message if you attempt to edit a Store Application record when you're in a different application scope.

Change your PDI user role to either App Engine Studio Creator or Admin for different views and levels of access.

Classic app development on the ServiceNow AI Platform enables you to plan, design, and build applications using classic app builders, IDEs, and other ServiceNow tooling. Start with what you know and use powerful builders for different development experiences, a library of reusable components, and published applications to modernize your legacy processes.

Clear the stored credentials of the current project from the system. User credentials (instance URL, user name, password) of a project are stored in the operating system credentials vault so that the user does not need to log in each time.

The Code Editor is the central workspace in Lux Lab. It provides syntax highlighting, context-aware code completion, multi-file navigation, and integration with the Lux platform.

Assign permissions to define what collaborators can do.

Properties in the now-ui.json file that define a component's scope, dependencies, actions, properties, and UI Builder and analytics settings.

Several types of components are installed with activation of the sn_desktop_agents plugin, including user roles and tables.

Configure Chrome so that the files can automatically complete downloads without manual intervention, and each download's status and path can be tracked automatically.

A property becomes configurable and visible in the props pane when you add a decorator to it. The decorator's options set the field type that the props pane renders, and also set the storage key that the resolved value is read back from.

Lux makes a component's behavior configurable at three levels: code, admin policy, and individual preference without three separate systems to learn. You add one decorator, @config, to a class field to opt a property into all of it.

You can enable the AI Desktop Actions application if you have the admin role.If the application does NOT include demo data or it does NOT install related applications and plugins, delete or revise the following sentence:

Configure app-level CSS for styles that belong to the app and must stay the same regardless of the tenant or user-resolved theme. Lux supports two optional files for this, tailwind.app.css and head.app.css.

Configure Autonomous Engineer by installing it from the ServiceNow Store and enabling the features required for planning and parallel execution on your instance.

Build Agent connects your instance to AI-powered design workflows. Set up the required application and MCP server connections to start using it.

Add a uiBuilder block to a component's now-ui.json file so that the component appears in the UI Builder toolbox on a workspace landing page.

Add tool gates, approval patterns, network rules, sandbox rules, capability overrides, connector scopes, and file type rules to a policy to control what Arc can do for the users the policy applies to.

Set the instance origin, proxy, and development server options for a component project.

Configure experiences by setting the properties that drive each instance and using the inline and admin editing surfaces to manage those values. You can arrange widgets into layout regions and apply themes to control appearance without touching code.

Enable AI agents to securely access stored values, such as credentials and other input data, through Desktop Action Parameter records. Parameters protect sensitive values and provide dynamic inputs to desktop actions during agent execution.

Configure brand colors, shape, theme-owned fonts, logos, favicons, and mobile color mappings in a theme.js module. Theme-level values can vary by tenant or user without a change to component code or an app rebuild.

Configure type checking for a component and JavaScript-only project.

Configure Application Runtime Policy to automatically approve generated policies, or to require review and manual approval.

Configuring Lux Lab means installing it and connecting it to your ServiceNow instance. You also set your preferences in the App Settings panel, including your profile, appearance, editor behavior, and integrations.

Install the ServiceNow Lux Lab for VS Code extension and connect it to your instance.

Set up the UI component CLI extension.

Connect ServiceNow Arc to GitHub or GitHub Enterprise to enable pull request review, CI checks, read code, and manage issues.

Connect your Microsoft account so ServiceNow Arc can work with your mail, calendar, Microsoft OneDrive files, and Teams chats and channels. After you connect, you can ask Arc to draft and send email, schedule meetings, find files, and post to Microsoft Teams.

Connect MCP servers so Arc can use tools and data from other services, such as GitHub, Sentry, SerpApi, and Postman. Each server you connect adds capabilities to the agent, and you control which servers each sub-agent can use.

Connect the ServiceNow Lux Lab for VS Code extension to your ServiceNow instance to access instance files, deploy changes, and preview your work.

Connect Lux Lab to your ServiceNow instance so that you can access instance files, deploy changes, and preview your work. Instance sign-in is required before you can reach the app.

Connectors link ServiceNow Arc to the platforms you work in, so Arc can read and update your real data, not only answer questions.

Take control and pause the execution that AI agent is running. Make manual changes to your desktop, and then resume execution by providing handoff notes to the AI agent.

Lux apps use six core building blocks to create consistent, maintainable applications: a manifest, pages, loaders, widgets, a layout, and a context API for sharing data.

ServiceNow Arc separates the client, the agent host, and an isolated sandbox so that planning happens on the host and agent commands run inside a container with its own network policy. Arc runs on the desktop and connects to your ServiceNow instance, which governs what Arc can do.

Check the quality and safety scores of Arc sessions in AI Control Tower, then open a session or trace to see which metric scores and details.

AI Control Tower scores the traces that Arc sends for quality and safety. Review the scores to understand usage patterns and identify where responses fall short.

Add a file to a folder in your project directly from the Project Explorer tree. The file appears in the folder you choose, ready to open in the Code Editor.

Add a subfolder inside any folder of your project, directly from the Project Explorer tree. Use subfolders to group related files in your project.

Create a custom application by describing your requirements in plain language to Build Agent. The AI agent generates and builds the application code based on your input.

Develop ServiceNow Lux Lab for VS Code experiences from scratch.

Build a Lux experience from scratch in Lux Lab. The new project comes with sample pages, widgets, and the standard project structure, ready for you to add your own pages and widgets.

Create a page in a new experience so that you can add elements to it, preview it, and deploy it to an instance. You can create the page from a context menu, by hand, or with an AI agent.

Add a page to a Lux app. A page is a Lit web component that Lux registers as a route based on where you put its file.

You can create a widget two ways — describe it in chat or clone an existing widget. Each way produces a new widget ready to edit in the Editor.

Have an agent plan a task in plan mode, and then save that plan as a work item in your project. You agree on an explicit plan before the agent makes any code changes.

Create an AI agent and add desktop action tool in AI Agent Studio to mimic human-like intelligence while executing desktop actions for repetitive tasks in web and desktop environment.

Lux Lab's VS Code extension scaffolds, builds, and deploys an extension application through a guided UI. An extension application adds pages to an existing ServiceNow experience; it doesn't create a standalone experience.

Create descriptors in the collaboration application so that you can assign permissions to users or groups.

Create a policy to define what ServiceNow Arc can do, which actions need human approval, and which actions are blocked.

Build custom agentic workflows, AI agents, and skills for your applications using automated generation tools with Build Agent. You can streamline development by creating the necessary instructions, tools, and access controls based on your requirements.

Create a skill for Arc to do a specific task, customizing it to fit your needs. After running the same type of task a few times, turn it into a skill so future runs require only one prompt instead of detailed instructions.

Configure rules to enforce security boundaries for AI agents in your organization. Resource access rules define which files, folders, websites, and applications AI Desktop Actions can access.

Desktop action policies control which users are subject to resource access rules. Configure a policy to define the user criteria and link the rules that govern automated resource access.

Create a definition for your store app to define the licensing metrics you want collected.

After the application’s data model is created, secured, and populated with data, create the design elements to access that data.

Create a new page for an existing experience.

Create a page using the ServiceNow Lux Lab for VS Code extension to create tailored experiences.

Add a page variant to a route using the ServiceNow Lux Lab for VS Code extension.

ServiceNow applications are contained within a project in the VS Code IDE. Import an application from your ServiceNow instance with the help of ServiceNow Extensions for VS Code.

Ask Arc in a chat to run a task or remind you at a set time, without opening the scheduling window.

Schedule Arc to run an instruction once or on a repeating schedule, and run, edit, copy, pause, or delete any schedule from one list.

Create a segment policy to enable broad access to one or more policy categories without requiring individual policy records for each access attempt.

Create a custom sub-agent to hand off a specialized task, such as code review or security analysis, to a reusable agent with focused instructions and limited access. A narrow scope helps produce consistent results, limiting the sub-agent to only the skills and MCP servers it requires.

Install the ServiceNow SDK toolchain, scaffold a new Lux application, and deploy your first app to your ServiceNow instance. This foundational workflow guides you through environment setup, local development, and deployment.

Use Build Agent to add new files or modify existing files in ServiceNow applications to support ongoing app development and maintenance.

Logs in automatically when a goal references stored credentials configured for a website, without exposing sensitive values in chat or asking you to provide the input.

The AI Workflow Factory Prime Credit Dashboard enables you to see your credit entitlements and usage, including trends over time and breakdowns by capabilities used.

Develop custom components using the Next Experience UI Framework and the ui-component extension.

Monitor the usage of ISV applications with Subscription Management. Create a definition for your store application with the metadata you want collected. After publishing the application with the definition to the store, Usage Analytics runs and aggregates your defined metrics.