Build Agent limitations
Plan deployments and troubleshoot issues by learning about Build Agent constraints that affect deployment capabilities and performance.
Troubleshooting
If you encounter something that Build Agent can't currently do, complete that step directly on the ServiceNow AI Platform® and keep working with Build Agent for the rest of your development. Build Agent is designed to complement your workflow, not to replace it.
For details on troubleshooting, see Common issues and solutions in Build Agent.
General limitations of Build Agent
- AI-generated code requires human review for ACL correctness, security, platform conventions, and governance compliance. Put peer-review gates, static checks, and validation steps in place.
- You still must work with builders in ServiceNow Studio for app files and metadata types not yet supported in Build Agent, such as certain tables, UIs, or advanced features.Note:Build Agent can work on existing applications. You can use Build Agent to enhance base workflows, such as creating business rules on existing tables.
- Security in apps developed with Build Agent is at the application and API level, not at granular record and field level by default. However, you can vibe code security onto the app by making requests. For examples, see Example prompts.
- Limited support for cross-product AI integration.
Build Agent and ServiceNow Fluent
If there isn't a mapping between ServiceNow Fluent and the XML metadata, then Build Agent can't update the data unless you understand the platform well enough to precisely instruct Build Agent to make the changes you need.
Feedback on Build Agent
To give feedback on Build Agent, see the Idea portal on Now Support.