Enterprise developers face a persistent challenge: they want to use the latest AI coding tools, but their organizations require governance, compliance, and platform-specific context. ServiceNow just addressed this tension head-on. At Knowledge 2026, the company announced that Build Agent is now generally available and works inside Cursor, Windsurf, Claude Code, and GitHub Copilot, alongside ServiceNow Studio.
What Changed
Previously, developers building ServiceNow applications had to work primarily within ServiceNow Studio. Now, the Build Agent's core skills extend into the AI coding tools that developers already use daily. The ServiceNow SDK and agent skills work across Claude Code, OpenAI Codex, Cursor, Windsurf, and Antigravity.
This is not just about convenience. Developers can now access ServiceNow governance guardrails, application scopes (including out-of-the-box apps), and Anthropic-powered longer context sessions without leaving their preferred environment. When they export to ServiceNow Studio, governance, security roles, and data models apply automatically.
The announcement confirms that Anthropic's Claude is now the default model powering ServiceNow Build Agent. According to ServiceNow, they are targeting a 50% reduction in implementation time when using Claude internally.
Why Enterprise Governance Matters
I have seen many organizations struggle with AI adoption in regulated environments. They want the productivity gains from tools like Cursor and Claude Code, but compliance requirements and security concerns create friction. ServiceNow's approach is pragmatic: rather than forcing developers into a single environment, they brought governance to where developers already work.
The AI Control Tower provides centralized oversight, including compliance tracking and security controls. This matters for industries like healthcare and financial services where audit trails are non-negotiable. Scott Bickley from Info-Tech Research Group noted that Claude Code excels at "complex scenarios such as planning, executing, and verifying multi-step tasks automatically." Combined with ServiceNow's governance layer, this creates a path to agentic development workflows that enterprises can actually approve.
The Multi-Model Strategy
ServiceNow is deliberately pursuing a multi-vendor AI strategy. This announcement follows their recent OpenAI collaboration on automation and speech-to-speech technology. As Amit Zavery, ServiceNow's president and COO, explained: "Each of these partners have unique use cases and experiences." Customers retain choice in which AI model to deploy.
This flexibility is increasingly important. Different models have different strengths. Claude excels at reasoning through complex multi-step tasks. GPT-4 variants might be preferred for certain conversational interfaces. Allowing enterprises to choose, rather than forcing a single vendor, reduces lock-in risk and lets organizations optimize for their specific use cases.
What This Means for Developers in the Region
For developers in the UAE and broader Middle East working on enterprise applications, this announcement has practical implications. Many organizations here are deploying ServiceNow for IT service management, HR workflows, and customer service operations. The ability to build ServiceNow apps using Claude Code or Cursor, while maintaining compliance with local governance requirements, lowers the barrier to AI-assisted development.
The free access to App Engine Management Center is worth noting. It helps keep applications governed before deployment, which addresses a common concern I hear from IT leaders: how do we adopt AI coding tools without losing control over what gets deployed to production?
Outstanding Questions
Pricing clarity remains pending. When multiple AI models are in use across different tools, cost management becomes complex. ServiceNow has not yet provided detailed guidance on how customers should navigate these costs.
There is also the question of context limits. While Anthropic-powered longer context sessions are mentioned, the specific limits and how they compare across different IDE integrations are not specified. For developers working on large ServiceNow implementations, understanding these boundaries will be important.
Looking Ahead
ServiceNow's move reflects a broader trend: enterprise platforms are opening up to meet developers where they are, rather than expecting developers to adapt to proprietary environments. The combination of flexible AI model choice, governance by default, and integration with popular coding tools addresses the main objections enterprises have to AI-assisted development.
For organizations already invested in ServiceNow, this lowers the friction to adopting AI coding tools. For those evaluating ServiceNow, the ability to build using Claude Code, Cursor, or Copilot while maintaining enterprise controls is a meaningful differentiator. The real test will be in implementation: whether the governance layer adds friction that negates productivity gains, or whether ServiceNow has found the right balance between control and developer velocity.