Skip to main content
Cypress App

AI in Cypress

AI shows up in Cypress in two distinct ways, and knowing which one you need is the fastest route to the right page.

AI that writes tests for you. You are still the author. Cypress Studio and cy.prompt turn recorded interactions or plain language into real Cypress commands, so less of your time goes to boilerplate and selector archaeology.

Cypress made legible to your agents. Here your AI coding tool is the consumer. Skills, cypress tap, Cloud MCP, and agent-ready reports give an agent accurate Cypress context, so it produces tests that follow your conventions instead of generic ones that break in CI.

Most teams end up using both. The rest of this page is a map of what exists in each half.

Write tests with AI​

Both options below produce ordinary Cypress code that you can read, edit, and commit. Neither is a black box: cy.prompt exposes the generated commands in the Command Log, and Studio writes directly into your spec file.

  • Cypress Studio records real interactions in your app and turns them into end-to-end tests. Connected to Cypress Cloud, Studio AI also recommends assertions as you record. Reach for it when you want to author a test by clicking through your app.
  • Generate tests with cy.prompt turns natural language steps into executable Cypress commands, and can keep them working as your UI changes. Reach for it when describing a flow is faster than recording one.

Give agents Cypress context​

An AI coding agent that knows nothing about Cypress writes tests that look plausible and then fail in CI: brittle selectors, arbitrary waits, and assertions that do not retry. These capabilities give it better information to work from.

  • Cypress skills for AI agents teach your coding agent to write, review, and explain tests the way an experienced Cypress engineer would. Install them once per project.
  • cypress tap attaches your agent to a running open mode session from the terminal, so it can run a spec and then read the Command Log, the error, and the DOM as the Cypress app shows them. That closes the loop: the agent can verify its own fix instead of reporting pass or fail. The cypress-tap skill packages this workflow so your agent drives it correctly.
  • Cloud MCP connects your agent to Cypress Cloud so it can read real run results, failures, and Test Replay data while you work, rather than guessing at why something failed.
  • Cloud CLI is the scriptable counterpart to Cloud MCP: the same Cloud run data as JSON in the terminal, for agents that work through a shell and for your own automation. The cypress-cloud-cli skill instructs your agent on how to work through that recorded run and test data to find a failure's root cause.

Analyze and debug with AI​

What each capability needs​

No AI capability in Cypress requires a paid subscription. Everything below works on the free Starter plan, and some of it never touches Cypress Cloud at all. The exceptions are the agent-ready reports at the bottom of the table, which come with the Cypress Accessibility and UI Coverage solutions rather than with a Cloud plan.

Paying raises limits rather than unlocking capabilities: a paid plan gets you a larger cy.prompt execution allowance and higher hourly limits on cy.prompt and Studio AI. See AI usage limits for the numbers.

CapabilityWhere it runsCypress Cloud accountPaid plan
Cypress Studio recordingCypress AppNot neededNo
Studio AI assertion suggestionsCypress AppFree plan worksNo
cy.promptCypress AppFree plan worksNo
Cypress skills for AI agentsYour editorNot neededNo
cypress tapYour terminalNot neededNo
Cloud MCPYour editorFree plan worksNo
Cloud CLIYour terminalFree plan worksNo
Cypress AI failure and intent summariesCypress CloudFree plan worksNo
Agent-ready accessibility reportsCypress CloudYesIncluded with Cypress Accessibility
Agent-ready coverage reportsCypress CloudYesIncluded with UI Coverage

The capabilities that need a Cloud account need one because Cypress Cloud is what routes their AI requests securely, applies your organization's controls, and tracks usage. See Why do I need a Cloud account?

Organization admins and owners can turn AI capabilities on or off for everyone in the organization. See Disabling AI features.

See also​

Contents