A year ago, cy.prompt was an experiment. The goal was simple: make authoring tests something more of the team can do, and cut the maintenance that piles up from an ever-evolving application.
A year later, that goal is real. cy.prompt lets teams write tests in plain language, generates the actual Cypress code underneath, and self-heals those tests when the UI shifts, so your team spends less time fixing tests after a UI update. Over 2,000 teams have built tests with cy.prompt, and the teams who adopt it keep building on it, week after week.
On August 1st, cy.prompt becomes a core feature included as part of every Cypress Cloud plan. Here's what's changing, what counts toward your usage, and how to plan for it.
What's changing
Starting August 1st, cy.prompt usage is measured in executions, and every Cypress Cloud plan includes an allocation that renews with your billing cycle. You can find the amount included with each plan on the pricing page.
Paid plans are built so a busy month never breaks your pipeline or leads to a surprise bill. Going over your allocation doesn't trigger automatic charges or stop your tests from running. If your usage regularly runs beyond your plan, we'll reach out to help you find the plan that fits.
On Free plans, once you reach the included allocation, AI self-healing and new cy.prompt authoring pause until your next cycle, and your existing tests keep running.
What counts toward your usage
An execution is counted each time a cy.prompt command runs, whether your team is authoring tests locally (open mode) or running them in CI (run mode). Each cy.prompt command counts as one execution each time it runs, no matter how many steps it includes. For example, a command that logs in, opens a dashboard, and checks the page title is one execution, not three.
Usage is not impacted when a command execution is attempted but cannot be completed due to lack of authentication, network issues, or malformed prompts.
How to plan ahead
cy.prompt is free to use through July 31. Starting August 1st, usage counts toward the number of executions your plan includes, beginning at zero. Anything run before August 1st doesn't count.
To see where you stand, check the Billing & Usage page in Cypress Cloud. It shows how many executions you've used, and you can set email alerts as you get close to your limit.
Getting started
You can find more details about cy.prompt, including commonly asked questions, in our docs.
Thanks for building with us.