Cypress Studio AI
Record, assert, and verify - with AI doing the heavy lifting.
Cypress Studio generates and extends E2E tests by recording real interactions in your app. Studio AI adds a layer on top: as you record, it watches what changes in the UI and recommends assertions automatically. You review them, keep what fits, and save.
The result is faster test authoring and fewer gaps in coverage without guessing what to assert after every click.
Cypress Studio alone does not require a Cloud account or AI to be useful. You can record interactions and add assertions manually at any time. AI-powered recommendations are an opt-in layer that requires a Cypress Cloud connection.
Studio vs. Studio AI​
| Feature | Studio (no Cloud) | Studio AI (Cloud required) |
|---|---|---|
| Record interactions | ✅ | ✅ |
| Manually add assertions | ✅ | ✅ |
| Edit test code inline | ✅ | ✅ |
| Undo / redo / reset | ✅ | ✅ |
| AI assertion recommendations | - | ✅ |
| Review DOM snapshots for AI recommendations | - | ✅ |
If you don't have a Cloud account, Studio still works for recording interactions and manually adding assertions.
Try Studio AI without an account. If you choose, you can generate and accept up to 6 AI recommendations before you're asked to log in and link a project to continue. You can decline the trial or turn off AI recommendations at any time from the AI status indicator in the Studio panel - see Disable AI.
Get started​
Studio requires internet access and sourcemaps. See enable sourcemaps for sourcemap setup. AI features additionally require a Cypress Cloud account and linked project.
Connect to Cypress Cloud​
Studio AI requires a Cypress Cloud account and a linked project. If you haven't set this up, the Studio panel walks you through it.
Create a free account âžœA free account is enough: Studio AI works on every Cypress Cloud plan, including the free Starter plan. New accounts also include a 30-day trial of all paid features, which raises your AI usage limits while it lasts.
To link your project to Cypress Cloud, see Set up your project to record.
Enable sourcemaps​
Studio needs sourcemaps to load your test code accurately. Sourcemaps are enabled by default in most Cypress configurations. If Studio opens your test correctly when you click Edit in Studio, you're already set.
If sourcemaps are missing, Studio displays an error. See how to enable sourcemaps to resolve it.
Open Studio​
You can start Studio three ways:
- New test: Click New Test on any spec or suite in the Cypress App.
- Existing test: Hover over a test in the Command Log and click Edit in Studio.
- Studio panel: Click Studio Beta in the header panel directly.
Edit in Studio button on a Cypress test​
Clicking 'New Test' on a suite​
Create a new test​
- Click New Test on the spec file or suite you want to work in.
- Give the test a descriptive name. Studio AI uses the test name to help generate more meaningful assertions.
- When prompted, enter the URL you want Studio to visit. Studio writes a
cy.visit()command to your test file and uses it to load the app before recording can begin.
Studio creates the test definition and opens the Studio panel and is ready to record interactions.
Extend an existing test​
Studio runs your test up to the last command, then puts you in recording mode from that point forward. New recorded actions and assertions are always appended to the end of your test.
To extend a test:
- Run the spec in the Cypress App.
- Hover over the test in the Command Log.
- Click Edit in Studio.
You can then edit any portion of the test code directly in the Studio code panel. There's no need to switch to your IDE.
Record interactions​
Once Studio is open, interact with your app normally. Studio translates each action into a Cypress command in real time and adds it to your spec file. You can see the commands as Studio writes them in the Studio code panel.
Supported actions:
Need to inspect something while recording mode is active? You can pause recording by clicking the Record button and open DevTools to inspect elements or debug behavior, then click the Record button again to resume.
How selectors are chosen for commands​
Studio automatically picks a unique selector for each element you interact with, add an assertion to, or for AI smart recommendations. We use a priority strategy designed to optimize for uniqueness, readability, and performance.
Default Selector Priority​
data-cydata-testdata-testiddata-qanameidclasstagattributesnth-child
To prioritize selectors that make more sense for your project for Studio and cy.prompt(), use the Cypress.ElementSelector API.
Add assertions manually​
Right-click any element in your app to see available assertions based on that element's current state - visible, hidden, a specific value, a CSS class, and more. Assertions are always appended to the end of your test.
AI smart recommendations ✨​
As you record, Studio AI observes changes in the DOM between interactions and suggests meaningful assertions for each step based on what changed.
How recommendations work​
For each recorded interaction:
- A thinking indicator appears in the Studio panel while Studio AI generates a recommendation.
- If a recommendation is available, Studio AI displays an AI-generated comment explaining what the assertion validates. Studio AI generates the actual test code and collapses it by default - expand it to review.
- If Studio AI detects no meaningful DOM changes or another issue prevents it from generating a recommendation, Studio AI displays an icon indicating this and the reason (for example, no state difference was found).
Studio AI adds recommendations to your test code as soon as it generates them, so you can save or run the test with AI recommendations included before deciding to keep them. Adding them immediately is intentional: running the test shows whether a recommended assertion actually passes against your app before you commit it.
Accept, reject, or edit​
Each recommendation includes Accept and Reject (x) buttons that remain visible even after saving. You can:
- Accept recommendations one at a time or use Accept all to approve the full set.
- Reject recommendations individually or use Reject all to dismiss them.
- Undo, redo, or reset any changes in the Studio code panel (including acceptances and rejections).
Understand what was detected​
Hover over any recommendation to see:
- The exact state of the DOM at the time Studio AI generated the assertion. Studio shows a before and after snapshot of the DOM for each recommendation that represents the state of the DOM before and after the interaction that triggered the recommendation.
- Studio highlights the specific element the assertion targets in the DOM.
- You can save the code to verify the assertion passes before accepting or rejecting it.
The hover details give you enough context to decide whether the assertion reflects something meaningful to your team and not just something that changed.
Failing tests​
If a test is failing, AI recommendations and recording are both disabled. Disabling them is intentional - you don't want to take actions or add assertions when the test is already in a bad state.
To recover from a failing test:
- Edit the failing code directly in the Studio panel or in your IDE.
- Click Save to write the changes to your spec file.
When a line causes a test failure, Studio highlights that line in the code panel so you can locate it immediately for easier debugging.
Types of assertions Studio AI recommends​
Studio AI suggests assertions based on visible UI changes after each interaction, including:
- Visibility (element visible or hidden)
- Element existence
- Text content
- Length (number of elements)
- Form input values, selections, and states
- Element attributes including CSS classes and aria attributes
- Current URL and page title
Studio AI does not have access to your application code, business logic, or backend rules. Studio AI's recommendations reflect what actually changed in the visible UI.
Sensitive data handling​
When Studio AI reads your app's DOM to generate recommendations, it automatically excludes values from certain field types before sending anything to the AI model:
- Password fields (
input[type=password]) - Credit card fields using standard autocomplete attributes (card name, card number, expiry date, security code, card type)
- Hidden inputs (
input[type=hidden])
Studio AI still uses the structure and context of these fields to generate assertions and excludes only the values.
For full details on how Cypress handles data and AI model security, see the Security & Compliance page.
Disable AI​
For an individual session​
You can disable Studio AI for any individual session by clicking the AI status indicator in the status bar at the bottom of the Studio panel. Disabling Studio AI this way turns off AI recommendations for your current session only and does not affect other users, other projects, or your organization's AI settings.
For an anonymous trial session​
If you're trying Studio AI without logging in, you can decline the trial prompt when it appears, or turn off AI recommendations afterward from the same AI status indicator.
For an entire organization​
Organization admins and owners can disable AI capabilities for their entire organization from Cypress Cloud organization settings. Disabling AI at the organization level affects all users in the organization.
For more information, see Disabling AI features.
Usage limits​
Recommendation limits are per user, per hour. All plans share a limit of 10 parallel recommendation requests.
| Plan | Recommendations per hour |
|---|---|
| Free Cloud account | 60 |
| Paid Cloud account (or free trial) | 300 |
If you're not logged in, Studio AI works as a trial: you can accept up to 6 recommendations per browser session before you're asked to log in and link a project to continue.
During the beta, Studio AI is included at no additional charge. Limits and pricing are subject to change. We'll communicate any adjustments before they take effect.
If you need to increase your limits, contact support at support@cypress.io.
Known limitations​
Studio​
- E2E tests only — Component Testing is not yet supported.
- Cucumber-style tests are not yet supported.
- Studio cannot record interactions across multiple origins.
- iFrames and Shadow DOM are not supported.
Studio AI​
- Studio AI requires Cypress version 15.11.0 or later.
- Animations and transitional UI states may produce intermediate DOM diffs, which can affect AI recommendation quality.
- Large pages may exceed AI context window limits, so Studio AI generates no recommendations.
- No automatic application crawling. Studio AI only observes what you interact with.
See open issues labeled topic: studio for the full list.
Send feedback​
There's a feedback button at the bottom of the Studio panel, so use it. Studio is in beta and your input directly shapes what we prioritize next.