--- title: "cy.blog()" url: "https://www.cypress.io/blog/page/5" description: "Page 5: Releases, AI-assisted testing, and quality guides from the Cypress team. See what changed, whether it affects you, and how teams ship with confidence." --- # cy.blog() Releases, AI-assisted testing, and quality guides from the Cypress team. See what changed, whether it affects you, and how teams ship with confidence. [Meet cypress tap: give your AI agent the context the Cypress app shows you Cypress AIcypress tap is a new set of CLI command to pull Cypress app context into your terminal. It lets AI agent drive a Cypress open session from the terminal, so it can author new tests, extend existing ones, and read failures the way the Cypress app shows them.Read more](/blog/cypress-tap-cli) [All](/blog)[Releases](/blog/category/Releases) [Community](/blog/category/Community) [Education](/blog/category/Education) [Customer Stories]() [Company](/blog/category/Company) [Cloud MCP: Give Your AI Assistant Access to Your Test Runs Update: Cypress Cloud MCP reached general availability on May 20th, 2026. Today, we are releasing the beta of Cloud MCP — a remote Model Context Protocol (MCP) server that connects AI coding assistants and AI Agents directly to Cypress Cloud. If you've ever finished a CI run, watched it go red, and then spent the next ten minutes copy-pasting stack traces into a chat window, you know exactly what problem we're solving. We're bridging the context gap in AI-driven development. The context gap Read more](/blog/cloud-mcp-give-your-ai-assistant-access-to-your-test-runs) [cy.prompt can now wait for network requests cy.prompt now supports waiting for network requests by referencing aliases you've already defined with cy.intercept. You can keep your test instructions in one place, without breaking out of the prompt block to insert manual waits. Read more](/blog/cy-prompt-can-now-wait-for-network-requests) [Introducing Studio AI: Stronger Validation, Less Friction A passing test run does not always equal release confidence. Confidence comes from knowing your tests validate what users actually experience. Not just that a flow executed, but that the UI state changed appropriately, the right text appeared, and element visibility updated as expected. This is where friction shows up. After every meaningful interaction in a test, there's a decision to make. What changed? What should be verified? Those decisions take time. Under pressure, it's easy to write t Read more](/blog/introducing-studio-ai-stronger-validation-less-friction) [How cy.prompt generates cy.contains, cy.press, and handles sensitive data cy.prompt now supports text-based targeting via cy.contains, keyboard interactions through cy.press, and non-existence assertions using visible content. This post covers what changed and how sensitive data in the DOM is handled automatically. Read more](/blog/how-cy-prompt-generates-cy-contains-cy-press-and-handles-sensitive-data) [Fix Cypress CI failures caused by no spec files found Stop Cypress from failing your CI build when no spec files are found. Learn when to use --pass-with-no-tests, when to leave it off, and what else shipped in 15.11.0. Read more](/blog/fix-cypress-ci-failures-caused-by-no-spec-files-found) [Environment Variable Access in Cypress v15.10.0+: Migrating to cy.env() and Cypress.expose() Starting in Cypress 15.10.0, Cypress.env() is deprecated and will be removed in Cypress 16.0.0. This change is driven by the way Cypress.env() hydrates all Cypress environment values into the browser context, including values a test may never read. This makes it easy to unintentionally expose more data than intended. We have not seen reports of this being exploited, but we are implementing this deprecation (and future removal) to move Cypress toward safer defaults and more explicit control o Read more](/blog/environment-variable-access-in-cypress-v15-10-0-migrating-to-cy-env-and-cypress-expose) [What’s new in cy.prompt for AI testing in Cypress We’ve made a series of focused updates to cy.prompt based on how teams are using AI in real Cypress test suites. Learn what’s new, why it matters for reliability and readability, and what improvements are coming next. Read more](/blog/whats-new-in-cy-prompt-for-ai-testing-in-cypress) [What's new in Cypress Accessibility? Over the last year, we've delivered some of the most requested features by current Cypress Accessibility customers, and extended the range of use cases and environments we support. If you're not familiar with Cypress Accessibility, here's the three things you need to know: 1. Automated test runs you record to Cypress Cloud can generate page- or component-level accessibility reports based on everything that happened in your tests, including all steps of all user journeys. 2. It supports compa Read more](/blog/whats-new-in-cypress-accessibility) [AI self-healing in Cypress: reliable tests with full visibility cy.prompt brings transparent self-healing to Cypress tests, adapting to UI changes while showing exactly what healed and why. Get clear logs, reliable tests, and the option to generate code once and commit it for full control in CI. Read more](/blog/ai-self-healing-in-cypress-reliable-tests-with-full-visibility) [Newer posts](/blog/page/4) [Older posts](/blog/page/6)