---
title: "cy.blog()"
url: "https://www.cypress.io/blog/author/emily"
description: "Read every Cypress blog post by Emily Wisniewski, newest first, from testing techniques to Cypress product news."
---

# 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.

## Articles written by Emily Wisniewski

[More data, smaller responses: what's new in Cypress Cloud MCP New tools, more data, smaller responses: what's new in Cypress Cloud MCP as of September 2026. Read more](/blog/whats-new-in-cypress-cloud-mcp-sept-2026)

[Meet cypress tap: give your AI agent the context the Cypress app shows you cypress 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)

[75% Less Cypress Bloat in Your Agent's Context Window Learn how Cypress's output is your agent's context passenger and how we reduced our context footprint by 75% using two existing CLI flags. Read more](/blog/75-less-cypress-bloat-in-your-agents-context)

[How to Connect an AI Agent to a Live Cypress Test Session If you've used Cypress Cloud MCP, you know what it looks like when your agent triages a CI failure on its own: no copy-pasting, no context switching. But what about when you're developing locally? When a test fails in cypress open, your agent is still on the outside. It can't see the runner, the DOM, or what the app looked like when it broke. You're still the one relaying that information. Connecting the Chrome DevTools MCP to your Cypress session changes that. Your agent gets direct access to Read more](/blog/connect-an-ai-agent-to-a-live-cypress-test-session)

[Cypress Cloud MCP is Generally Available Today, Cypress Cloud MCP is generally available! When we launched Cloud MCP in beta two months ago, we had a hypothesis: developers shouldn't have to copy-paste stack traces into a chat window to get their AI assistant to help them debug. Cypress Cloud already had all the context their assistant needed. We just needed to close the gap. The response told us the hypothesis was right. In the 9 weeks since beta, over 500 organizations connected, and more than 1,000 developers have used it to query Read more](/blog/cypress-cloud-mcp-is-generally-available)

[Cypress AI Skills: Get More From Your AI Coding Assistant AI coding tools can write Cypress tests. What they tend to struggle with is writing them well. Ask an AI assistant to generate a Cypress test and you'll probably get something that runs. But look closer and you'll find CSS class selectors instead of data-cy attributes, cy.wait(3000) instead of network aliases, and no awareness of the custom commands your team already built. It's a Cypress test — it's just not the kind of Cypress test you'd write yourself. That's the problem Cypress AI Skills i Read more](/blog/cypress-ai-skills-get-more-from-your-ai-coding-assistant)

[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)