What changed
Shopify announced on August 27, 2026 that Theme commands on Shopify CLI versions 3.83.x and earlier will no longer support password-protected storefronts from October 1. Those CLI releases rely on a legacy storefront preview/session-authentication path that Shopify is retiring. Developers who continue using the old versions can lose theme-development access to password-protected shops, including common workflows such as `shopify theme dev`, `shopify theme console`, and `shopify app dev` when an app includes theme app extensions. Shopify says the supported path is CLI 3.84.0 or later and currently recommends the latest release, 4.7.0. Removing storefront password protection is an alternative, but changes the store's access boundary rather than fixing the development toolchain.
Why it matters
Local theme development often sits far outside normal production monitoring, so this failure can look like an authentication or shop-configuration incident rather than an intentional CLI retirement. Agencies and app/theme teams can also have old CLI versions pinned in developer laptops, CI images or project tooling long after newer versions exist. The October cutoff therefore creates a concrete developer-workflow compatibility boundary: password-protected development stores can remain online while older local tooling suddenly loses preview/session access. Teams should upgrade and test rather than weakening storefront protection simply to preserve an obsolete authentication path.
The break is scoped to password-protected storefront development
Shopify says the cutoff affects Theme CLI commands using versions 3.83.x and earlier when the target storefront is password protected. Public storefronts do not depend on the same legacy preview/session-authentication path, so the issue is not a universal Shopify CLI shutdown.
Several ordinary theme workflows can fail together
The most likely affected commands are `shopify theme dev` and `shopify theme console`. Shopify also calls out `shopify app dev` when an application contains theme app extensions, because that development flow can need the same protected-store preview access. Teams should therefore audit app-development tooling as well as standalone theme repositories.
Version 3.84.0 is the compatibility floor
Shopify documents 3.84.0 or later as the supported line after October 1 and recommends upgrading to the latest CLI. That means simply reinstalling an arbitrary older 3.x build is not enough; CI images and developer setup docs should pin or enforce an accepted minimum version.
Removing the password is a workaround, not an equivalent migration
Shopify notes that developers can remove storefront password protection and continue using an older CLI. That changes who can access the storefront, however, and may be inappropriate for development, staging or pre-launch stores. Upgrading the CLI preserves the intended access control while moving off the retired authentication implementation.
This is separate from Shopify's other October migration
BTN already tracks Shopify's October 1 cutoff for creating or updating storefront ScriptTags. The dates coincide, but the underlying changes are independent: one retires legacy Theme CLI authentication for protected stores; the other removes a legacy storefront script-injection API. Theme teams should keep both migration checks on their October readiness list.