ServiceNow Build Agent Now Works Inside Cursor, Claude Code, Windsurf, and Copilot
ServiceNow made Build Agent generally available at Knowledge 2026, extending it into the four major AI coding tools so developers can build ServiceNow apps without leaving their preferred IDE.
ServiceNow announced at Knowledge 2026 on May 6 that Build Agent is now generally available in ServiceNow Studio and accessible from Cursor, Windsurf, Claude Code, and GitHub Copilot. Developers who already live in those tools can now build ServiceNow applications without switching to Studio.
The integration works through the ServiceNow SDK, which exposes Build Agent’s core capabilities as skills available inside each IDE. That means the agent brings its understanding of your live ServiceNow instance — existing data models, configurations, and active policies — into whatever environment you’re coding from.
What Build Agent Does
Build Agent generates full applications from natural language prompts: workflows, catalog items, UI components, and configurations in a single session. It includes a self-healing test loop for quality validation and supports custom instructions so teams can encode their organization’s development standards and conventions directly into the agent’s behavior.
In ServiceNow Studio, Build Agent shows a planning step before it executes — a preview of what it intends to create. Jithin Bhasker, VP and GM at ServiceNow, explained the reasoning: “Speed without governance and an enterprise runtime produce apps that too often look ready but aren’t.”
Elmer de Valk, CEO of ServiceNow partner Plat4mation, offered a concrete data point from a recent project: “Build Agent generated nearly 80% of the application automatically.”
The Anthropic Connection
ServiceNow Studio’s version of Build Agent now runs on Anthropic models. ServiceNow says the switch enables longer context sessions, which matters when you’re working through an entire application build without wanting to lose continuity mid-session. The general-purpose Claude model was replaced with a model better suited to sustained development work.
Build Agent also supports MCP Client connections to external tools like Figma, Miro, and GitHub, so it can pull in design context or reference external repositories without manual copy-paste.
Governance Built In
Free access to App Engine Management Center (AEMC) is now included with Build Agent. AEMC handles governance checks before an application goes to production, verifying that what the agent built meets platform standards. ServiceNow’s framing is that governance has to be default-on, not something teams remember to add at deployment time.
In-app AI agents are also embedded by default in custom applications built with Build Agent, so the apps themselves arrive with AI capabilities rather than requiring a second build pass to add them.
A sandbox environment is available for testing before any changes touch a live instance.
Context
Build Agent’s expansion into external IDEs is a direct response to how enterprise development has shifted. Most teams building on ServiceNow no longer stay inside Studio for the entire workflow — they’re in Cursor or Copilot for the heavy coding and context switching back to Studio only when they need platform-specific tools. ServiceNow is meeting developers where they already are rather than asking them to relocate.
The free AEMC access changes the economics somewhat. Governance tooling for ServiceNow deployments has historically required separate licensing. Making it part of the Build Agent package removes a step that often got skipped.
Pricing for Build Agent beyond the beta period hasn’t been detailed publicly. AEMC free access is expected to extend through the end of Q3 2026.
Sources: ServiceNow Newsroom — Build Agent announcement (May 6, 2026), BusinessWire press release, CIO.com — ServiceNow embeds Anthropic Claude as default Build Agent model