I’ve looked into this, and it seems like you’ve identified a regression issue in Shopify CLI version 3.88.1. Since you’ve already confirmed that you are on the latest version and provided a clear reproduction case, here are a few things you can try or keep in mind while this is being addressed:
Check for CLI Updates: Sometimes hotfixes are released shortly after a minor version causes a regression. Run shopify upgrade to see if a newer patch (like 3.88.2+) is available.
Clear Local Cache: Occasionally, the local dev server cache causes sync issues. You can try stopping the CLI and running shopify theme dev --reset (if applicable) or clearing your browser’s cache for the admin/customizer URL.
Downgrade as a Temporary Fix: Since this started specifically with v3.88.1, you might want to downgrade to v3.88.0 or the previous stable version where it was working. You can do this via npm: npm install -g @shopify/cli@3.88.0
Check Node.js Version: You are on Node v25.3.0 (Experimental/Current). Sometimes the CLI behaves more predictably on LTS (Long Term Support) versions like Node 20 or 22. If the downgrade doesn’t work, testing on an LTS version might help.
I’ve checked the logs you provided on Pastebin, and it does look like the file watcher is picking up changes but failing to trigger the browser hook. I’d recommend opening a formal issue on the Shopify/cli GitHub repository with this exact data, as it looks like a bug in the sync logic of the new version.
Hey @nbsimmons - thanks for flagging. This is odd especially since the changes are showing as synced. @Ankit_Saxena is on point about opening an issue on the CLI repo if you haven’t already:
This would get you in touch with the CLI devs directly and they should be able to help out.
Oh, no worries @nbsimmons - I didn’t realize it redirected back here to the forums, in the past it let you set up an issue right in the repo itself. Yeah, this is the right place for this in that case. We can definitely take a look.
Just to narrow down some things, could you let me know which version of Chrome you’re using for the theme preview?
Thanks @nbsimmons - and no worries! I didn’t realize we changed how bug reports work for the CLI Looking into this for you now, I’ll loop back once I have more to share/if I need more info from you on our end.
Hey @nbsimmons - feel free to share that here! We’re still looking into the other issue you reported earlier, but I still have eyes on that too. I’ll keep you in the loop.
In addition, to the above, the customizer no longer hot reloads when a change is detected locally.
Prior to the last two CLI versions, if –theme-editor-sync was active and you had the Customizer open, it would automatically reload the customizer but this no longer happens.
Looking into this for you now, I’ll loop back once I have more to share/if I need more info from you on our end.