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.promptturns 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 tool to write, review, and explain tests the way an experienced Cypress engineer would. Install them once per project.
cypress tapattaches 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.- 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.
Analyze and debug with AI​
- Cypress AI explains failures and summarizes test intent across recorded runs in Cypress Cloud.
- Work with AI agents in Cypress Accessibility and Work with AI agents in UI Coverage cover tuning those reports so an agent can act on them, then prompting it to triage findings and plan the work.
What each capability needs​
| Capability | Where it runs | Needs Cypress Cloud |
|---|---|---|
| Cypress Studio recording | Cypress App | No |
| Studio AI assertion suggestions | Cypress App | Yes |
cy.prompt | Cypress App | Yes, on any Cloud plan |
| Cypress skills for AI agents | Your editor | No |
cypress tap | Your terminal | No |
| Cloud MCP | Your editor | Yes |
| Cypress AI failure and intent summaries | Cypress Cloud | Yes, on any Cloud plan |
| Agent-ready accessibility reports | Cypress Cloud | Yes, with Cypress Accessibility |
| Agent-ready coverage reports | Cypress Cloud | Yes, with UI Coverage |
Organization admins and owners can turn AI capabilities on or off for everyone in the organization. See Disabling AI features.
See also​
cy.prompt()- the command reference- Cypress Studio
- Cypress skills for AI agents
cypress tap- Cloud MCP