The Shopify CLI 3.85.0 update lets developers with multiple Partner accounts switch between them without logging out, logging back in and passing OTP verification each time. Its second change adds an extra confirmation before any change customers would see on a live theme. Updating takes one package manager command, and shopify version confirms the installed version.
What Changed in Shopify CLI 3.85.0?
Shopify CLI 3.85.0 brought two main changes, aimed at the account switching process for developers who manage multiple Partner accounts and at risky changes made to live themes. Before this release, switching accounts meant logging out and logging back in, with OTP verification every time; 3.85.0 shortens that flow. For developers on the Nodus Works team who work across several client accounts at the same time, this update has a direct effect on the daily workflow.
The second change is more about risk management: the CLI now asks for an extra confirmation step before making changes to a live theme. This prevents a change that customers will see from being published by mistake, especially in projects where several developers work on the same store.
The real value of Shopify CLI 3.85.0 is not a new feature as such, but handing over to the tool two points that used to need manual attention in multi-account, multi-developer setups.
How Do You Switch Between Partner Accounts?
Before 3.85.0, switching accounts took three steps, and each step meant lost time or a risk of error. The new release lets you manage these steps within the CLI itself.
Old flow (before 3.85.0):
New flow (3.85.0 and later): The CLI now supports multiple sessions. You add each Partner account once with shopify auth login; after that, the same command lets you pick from your saved accounts, with no logout and no new OTP verification. For agency developers who work in several client accounts a day, this is the change that saves the most time.
New Safety Warning for Live Theme Updates
When you run shopify theme dev on the live theme, the CLI now shows this warning: "This will make changes visible to customers. Are you sure you want to proceed?" The warning gives the developer a chance to stop and think before the command runs.
The practical value of this feature shows in scenarios where several developers work on the same live store. If a developer wrongly assumed which environment (development theme or live theme) a test command would affect, in earlier versions that mistake could go straight to customers. The new confirmation step catches the mistake before the command runs.
Important: This warning only covers direct theme changes made through the CLI. Live changes made from the admin through the Theme Editor are outside this protection; team discipline (who can change the live theme and when) is still a separate process issue.
How Do You Update to 3.85.0?
Updating an existing Shopify CLI installation takes a single command and does not break your existing project configuration.
A globally installed CLI is brought up to the latest version with your package manager's update command (npm, Homebrew or whichever tool you use). After updating, check the version with the shopify version command; if it shows 3.85.0 or higher, the new account switching and live theme warning features are active. Existing projects need no extra configuration changes.
Tip: In an agency where several developers work on the same client projects, the whole team should move to the current version (at least 3.85.0) at the same time. A mix of versions means the live theme warning appears for some developers and not for others, which creates inconsistency within the team.
Why Does This Update Matter for the Nodus Works Team?
For an agency doing custom development in several client stores at once, friction when switching accounts is a small but cumulative loss of time. For a developer who switches accounts 5-6 times a day, the old flow meant an extra 10-15 minutes of work a day. The live theme warning is even more important: in custom integration projects where several developers work in the same store, accidentally touching the live theme is a real operational risk.
In custom Shopify integration and app development work, tracking tool updates like this and rolling them out to the team on time is part of the daily operation of our Shopify integration solutions and custom app development service. For teams that want to build version and environment discipline in which several developers can work safely, tool choices like these matter as much as the project's technical infrastructure.
FAQ
How do you update to Shopify CLI 3.85.0? An existing installation is brought up to the latest version with the update command of the package manager you use (npm, Homebrew). After updating, you can check the version with the shopify version command.
Do older CLI versions still work? Yes, older versions keep working, but they do not include the new features such as account switching and the live theme warning. Shopify recommends using the current version for projects under active development.
Can the live theme warning be turned off? The warning is triggered automatically when a directly visible change to the live theme is detected. Its purpose is to prevent a mistake that customers would see, which is why it is designed as a safety layer.
Do you need to log in again to switch between Partner accounts? No. From 3.85.0 onward, the CLI keeps the active session and lets you switch between accounts without asking you to re-authenticate.
Conclusion
Shopify CLI 3.85.0 moves two real friction points in multi-account, multi-developer setups (account switching and live theme risk) directly into the tool. For agency teams running several client projects, this adds up to a small but cumulative efficiency gain.
If your team builds custom Shopify integrations or manages several stores at once, setting up the right tooling and version discipline is part of our Shopify integration solutions and custom app development service.
