Cypress 16 Arrives: HTTP/2 by Default, Cypress.env() Retired, and What It Means for Your Test Suite

Cypress's Biggest Runtime Shake-Up in Years

While much of the automation conversation this year has centered on Playwright and Selenium's BiDi migration, Cypress has been quietly rebuilding its own foundations. The team's latest major version, Cypress 16.0.0, changes how test traffic actually moves across the wire and removes an API that has been part of nearly every Cypress project since the tool's earliest days.

HTTP/2 Becomes the Default

Cypress 16 tests run over HTTP/2 by default in Chrome, Chromium, and Edge - the same protocol your app uses in production, with faster multiplexed requests and no six-connection ceiling. That last detail matters more than it sounds: the old six-connection-per-origin limit under HTTP/1.1 has long forced test runners to queue requests in ways production traffic never does, occasionally masking or introducing timing-related flakiness. Running suites over the same protocol stack the app uses in the wild should make test behavior line up more closely with real user sessions.

A Modernized Foundation and a 'Breaking' Change

This release also modernizes the foundation Cypress runs on, moving to Node.js 24, Electron 41, and Chromium 146, and removes Cypress.env(); the migration guide includes an AI-assisted upgrade prompt. Dropping Cypress.env() is the change most teams will feel first, since it has been a standard way to read configuration and secrets inside spec files for years. Anyone still relying on it will need to work through the official migration guide, and it's notable that Cypress is now baking an AI-assisted prompt into that guide rather than leaving teams to grep their codebase manually.

The Groundwork Was Laid in Cypress 15

This isn't a sudden pivot. Cypress 15, released in August 2025, was explicitly framed as a foundation release. Under the hood it removed support for Node.js 18 and Node.js 23, removed support for Linux distributions with glibc older than 2.31, and removed support for Chrome DevTools Protocol with the Firefox browser. On the feature side, the team used that release to rework Cypress Studio, its record-and-edit test builder. Users can still record interactions and add assertions by right-clicking, and now even edit the test inline without leaving the Cypress App, and Cypress has described this as the beginning of its vision for AI-assisted test creation, with the new Studio experience giving the building blocks to eventually ship smarter test tooling that learns from your app and your tests.

Meanwhile, the Point Releases Kept Shipping

Between the two majors, Cypress's patch cadence didn't slow down. Next.js 16 component testing support arrived after Next.js 16 was announced on October 21, 2025, and by version 15.7 teams could component test their Next.js 16 apps with webpack bundling, though Turbopack isn't supported yet. That release also brought a targeted performance fix: Cypress now limits the number of matched elements it checks for visibility before logging them into the command log, a change aimed squarely at teams running large, DOM-heavy dashboards where visibility checks had quietly dragged on run times.

What QA Teams Should Do Now

• Audit for Cypress.env() usage before touching the v16 upgrade: this is the change most likely to break CI pipelines silently.
• Check your Node and browser baselines: Node.js 24, Electron 41, and Chromium 146 are now the floor, so older CI images will need updating.
• Re-baseline flaky-test metrics after moving to HTTP/2: some tests may behave differently once the connection ceiling disappears.
• If you're running Next.js 16 component tests, stick with webpack for now; Turbopack support isn't there yet.

Cypress remains one of the two dominant JavaScript-first end-to-end frameworks, and this pair of releases signals a deliberate strategy: strip out legacy baggage, align the test runner's networking with real-world production behavior, and use that cleaner foundation to build AI-assisted authoring and migration tools on top. Teams running large Cypress suites should treat the v16 upgrade as a planned project, not a drop-in bump.