PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteCypress AI self-healing can keep a test step working when a page change makes its old selector stop matching. In cy.prompt, Cypress first checks selectors that worked before; if none fit, it can use AI to find an element for the original natural-language instruction. That can prevent some selector changes from interrupting a run—but a healed selector is not proof that the test still exercises the right behavior. Teams should inspect the resolved element and keep meaningful assertions.
What AI self-healing means in Cypress
Cypress presents cy.prompt as a way to author tests with natural-language instructions in the Cypress App. It can turn instructions into standard Cypress commands. A team can also leave the prompt active so Cypress adapts its steps as the UI changes. Cypress calls this adaptation AI self-healing; it is a Cypress-specific workflow, not a guarantee that arbitrary test logic or application defects will be repaired. Cypress AI
As an Amazon Associate I earn from qualifying purchases.
For example, a test may ask Cypress to click the sign-in button. If a redesign changes the button’s class or moves it, a selector written against the old markup may no longer find it. Cypress’s examples also include renamed buttons, moved form fields, redesigned login controls and changed product-card layouts. These are examples of locator maintenance, not evidence that AI can infer every intended business rule.
How Cypress tries to heal a changed selector
- Start with a natural-language step. The prompt describes the action or target in the test.
- Check previously successful selectors. Cypress says it first tries its cache of selector mappings that worked in earlier runs.
- Use AI if the cache does not fit. If the changed page no longer matches a cached mapping, Cypress can use AI to locate an element corresponding to the instruction.
- Review the result. Cypress says the Command Log and detailed Console output show the resolved element and whether the step was healed via cache or AI. Jennifer Shehane, writing for Cypress on December 3, 2025, described this visibility as: “Every healed step is visible in the Command Log and in detailed Console output so you always understand how your test resolved the element.” Cypress’s technical explanation
In Cypress’s description, a cache-based heal does not make an AI call; the AI path is used when the selector changed and no matching cached entry exists. The visibility is useful for review, but it does not independently establish that the element Cypress found is the one the test author intended.
What improves reliability—and what does not
The narrow reliability benefit is fewer test interruptions caused specifically by selectors that no longer match after a UI change, when the intended action remains the same. A renamed control or a layout refactor need not automatically leave a test blocked on its old locator.
Self-healing does not prove that the application works, that the selected control is semantically correct, or that assertions cover the user’s actual goal. A test can pass because its written assertions pass; that alone does not validate the test’s business intent. Cypress’s FAQ also notes a distinct caveat in its cypress tap workflow: a spec with all tests skipped can report passed. Cypress App FAQ
- Check the resolved DOM element for each healed step, particularly for high-impact actions such as submitting a payment or changing account access.
- Review the Command Log and Console details to see whether Cypress used a cached selector or AI.
- Keep assertions tied to outcomes that matter, such as a confirmation state, persisted value or expected navigation—not just the fact that a click occurred.
- Review generated code and diffs before committing changes, and test important flows against the redesigned UI.
Choose between runtime adaptation and committed Cypress code
Cypress supports two distinct ways to use prompts. The trade-off is whether the test adapts at runtime or whether a human reviews the generated commands and then commits ordinary Cypress code.
Free tools Windows power users keep installed
One-click scans. No signup required.
| Approach | AI during each run? | Control and auditability | Useful when |
|---|---|---|---|
Keep cy.prompt active |
The prompt can adapt when UI changes make its prior selector mappings unusable; Cypress may use cache or AI. | Review healed steps in the Command Log and Console. The team must still verify the target and assertions. | You want prompt steps to accommodate UI changes without immediately editing selectors by hand. |
| Generate, inspect and freeze the code | No prompt-based adaptation is needed for each run after you commit ordinary Cypress commands. | Open Code view, inspect and edit the generated commands, then commit the static test. This retains human review and selector control. | You require approval before AI use in CI or want deterministic committed test code. |
Cypress describes running a prompt once and editing its generated commands as an option for teams that want full selector control. Generated code still needs review: a static selector can become stale later, and assertions still need to reflect the intended behavior. Cypress’s explanation of the authoring option
Account, usage limits and cost context
The Cypress App FAQ says cy.prompt requires a free or paid Cypress Cloud account. Cypress’s pricing page, accessed October 3, 2026, listed these prompt execution allowances; they are vendor plan figures, not reliability measurements, and may change:
| Plan | Prompt executions listed |
|---|---|
| Starter | 100 per month |
| Team | 9,000 per year |
| Business | 24,000 per year |
| Enterprise | 60,000 per year |
The same pricing page listed Smart Recommendations as free while in beta. Check the live Cypress pricing page for current limits and plan terms rather than treating these figures as permanent. The cited sources do not provide an independent quantified estimate of how much self-healing improves reliability.
Rank #4
Data handling: check the current Cypress terms
Cypress says AI Skills run inside a developer’s own coding agent, while cy.prompt, Studio AI and Cloud MCP use run data already stored in Cypress App and Cypress Cloud. Cypress describes that data as including command history, console logs, network requests and Test Replay recordings. Its security page says Cypress AI models are not trained on customer data, inputs and outputs are session-bound and not shared with model providers, and test content is stored in the USA. Cypress also says customers own and are responsible for test content stored in Cypress Cloud. These are Cypress’s statements; teams should check the current Cypress security information and their own data-handling policies before using sensitive test data.
Where local agent debugging fits
Cypress documents cypress tap as a way to drive an open-mode local session. For recorded CI runs, Cypress points to Cypress Cloud MCP or Cloud CLI. These tools may be part of a broader authoring and debugging workflow, but they are separate from the selector-recovery behavior of cy.prompt; using them does not itself mean a selector has self-healed. Consult the Cypress App FAQ for the current workflow details.
Best Value
Screenshot capture is a separate tool choice
For screenshot capture—not Cypress selector healing—ScreenshotNeo is the alternative to try first when a workflow needs website screenshots or PDFs. It removes cookie and consent banners, newsletter popups and chat widgets before capture; only clean shots are billed, so bot checks, blank pages, timeouts, failed loads and cache hits cost nothing. It also provides an MCP server for AI agents. This does not replace Cypress assertions or repair a test selector.
One GET request can capture a page; see the ScreenshotNeo documentation for options and API details:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpThe Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Sign up for 1,000 free screenshots a month, with no card required.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsQuick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
