Cypress AI
Cypress offers AI capabilities across the platform to help teams write tests faster, understand failures more clearly, and keep tests running as apps change. These capabilities are built into the tools you already use - the Cypress App and Cypress Cloud - and are designed to reduce the manual effort that can slow down testing.
This page explains what's available, how each capability fits into your workflow, and how Cypress handles your data.
The Problem Developers Face
Writing tests, maintaining them, and debugging failures is time-consuming and repetitive:
- Writing tests requires boilerplate and memorizing commands.
- Understanding large test suites is hard for new team members.
- Debugging failures often means staring at logs and replaying tests.
- Identifying missing coverage is manual and error-prone.
Cypress AI is designed to solve these problems without changing how you already work.
How Cypress AI Fits Into the Workflow
Cypress AI are easy-to-use tools across your testing lifecycle. They are woven into the core workflow.
| Stage | AI Capability | Outcome |
|---|---|---|
| Author Tests | cy.prompt(), Studio AI | Generate commands, assertions, and full tests from natural language or UI exploration |
| Understand Tests | Test Intent Summaries | Quickly see what tests verify, reducing cognitive load and onboarding friction |
| Debug Failures | Error Summaries | AI-powered explanations for what happened when a test failed |
| Analyze & Triage | Cloud MCP | Gives AI coding assistants and AI agents a direct window into your application's health and stability |
| Test maintenance | cy.prompt() | Automatically adapt to UI changes that would otherwise break selectors |
| Fill Coverage Gaps | UI Coverage Test Generation | Identify untested flows and automatically generate new tests |
Get Started
Log into your Cloud account to start using Cloud AI. By default, all AI capabilities are enabled for your organization.
Capabilities in detail
cy.prompt()
Best for: teams who want to generate Cypress test code from plain English, or reduce selector maintenance as their UI evolves.
cy.prompt() is a Cypress command that converts natural language test steps into executable Cypress commands. It uses AI to interpret each step, evaluate the DOM, generate selectors, and produce Cypress code. cy.prompt() supports two workflows.
cy.prompt(
[
'visit https://cloud.cypress.io/login',
'type "[email protected]" in the email field',
'type {{password}} in the password field',
'click the login button',
'verify we are redirected to the dashboard',
],
{
placeholders: { password: 'secret123' },
}
)
Workflow 1: Generate once, commit to source control
Use cy.prompt() to generate a test quickly, then export and commit the generated code.
This workflow is a good fit when:
- Your app has stable, predictable elements.
- You want predictable, reviewable test code in version control.
- You want to use AI to accelerate authoring but prefer to own the output.
Workflow 2: Continuous self-healing
Keep cy.prompt() running in your tests. When a selector fails between runs, Cypress regenerates code for that step automatically. This is "self-healing" — the test adapts without manual intervention.
This workflow is a good fit when:
- Your app is in active development and UI changes frequently.
- You are willing to accept AI calls at runtime in exchange for less maintenance.
- You understand that self-healing works best when it catches occasional, unexpected changes — not when selectors change on every run.
Read the full cy.prompt() documentation →
Studio AI
Best for: teams who want to write assertions faster without guessing what to assert after every interaction.
Cypress Studio lets you build and extend E2E tests by recording real interactions in your app. Studio AI adds assertion recommendations on top: as you record, it watches what changes in the UI and suggests assertions automatically. You review them, keep what fits, and save.
Studio AI observes DOM changes between interactions and generates assertions based on what actually changed — visibility, text content, form values, element attributes, URL changes, and more. It does not have access to your application's source code or business logic.
Read the full Studio AI documentation →
Test Intent Summaries
Best for: teams who need to understand what a test is checking without reading every command or watching a full Test Replay.
Test Intent Summaries are AI-generated descriptions of a test's purpose, available in the Cypress Cloud test details sidebar. They help you orient quickly — whether you are reviewing a new test or debugging a failure — without needing to trace through the command log manually.
Test Intent Summaries are available on all Cypress Cloud plans at no additional cost.
Error Summaries
Best for: teams who want to understand why a test failed without parsing raw stack traces.
"At a glance" Error Summaries are plain-language explanations of what went wrong in a failed test attempt, available alongside stack traces and error messages in the Cypress Cloud test details sidebar. They describe what led to the failure so you can jump directly to investigating the root cause.
Error Summaries are available on all Cypress Cloud plans at no additional cost.
Cloud MCP Beta
Best for: teams moving toward agentic workflows who want to eliminate the context gap between their CI environment and their development tools.
Cloud MCP is a remote server that gives AI assistants a direct window into your application’s health and stability. By connecting your AI coding assistant or AI agent directly to your CI results, it transforms Cypress from a testing tool into a real-time engineering data source—removing the manual overhead that makes testing a bottleneck.
Instead of spending time investigating runs, your assistant uses the Model Context Protocol (MCP) to independently monitor and analyze recorded run data, including errors, stack traces and test replay links. This makes it easier to reach for Cypress as your tool of choice.
Read the Cloud MCP documentation →
UI Coverage Test Generation
Best for: teams using UI Coverage who want to close coverage gaps without writing tests from scratch.
UI Coverage Test Generation lets you generate targeted Cypress tests directly from coverage gaps identified during code reviews. Instead of manually identifying what to test, you can generate a test scaffold from the gap and refine from there.
This capability is included with UI Coverage and is not available on standard Cloud plans.
Read the UI Coverage Test Generation documentation →
FAQs
Why do I need a Cloud Account?
Cypress AI features use large language models (LLMs) to interpret prompts, analyze DOM state, and generate test code. Cypress Cloud manages those LLM requests securely on your behalf.
Without a Cloud account, there is no secure channel through which to route those requests, no organizational controls to apply, and no way to enforce the data handling commitments Cypress makes to its customers.
A free Cypress Cloud account is enough to get started.
Create a free account ➜Free accounts include a two-week trial of all paid features, including higher AI usage limits.
Usage limits
Usage limits vary by feature and plan. During beta periods, limits are subject to change.
| Capability | Free plan | Paid plan |
|---|---|---|
| cy.prompt() prompts | 100 per hour, per user | 600 per hour, per user |
| cy.prompt() steps | 500 per hour, per user | 3,000 per hour, per user |
| Studio AI recommendations | 60 per hour, per user | 300 per hour, per user |
| Test Intent Summaries | Included | Included |
| Error Summaries | Included | Included |
| Cloud MCP requests | 100 per hour, per user | 100 per hour, per user |
| UI Coverage Test Generation | Not available | Included with UI Coverage |
If you need to increase your limits, contact support at [email protected].
Pricing
During experimental and beta periods, AI features are provided at no additional charge. Pricing is subject to change. We will communicate any changes before they take effect.
See Cypress Cloud plans for full plan details.
Security and data handling
Read the Cypress AI Security page →
Disabling AI features
AI features are opt-out, not opt-in by default. AI capabilities are enabled for all users of an organization on the applicable plan. Organization admins and owners can disable AI capabilities for their entire organization from Cypress Cloud organization settings.
