When I'm working with the local web server (jss start:connected) and at the same time I log into the actual instance of Sitecore (dev.test.com) and go to the experience editor. The local version get's stuck in experience editor mode.

The reason seems to be that chrome reads the cookies for the (dev.test.com) URL as well as the cookies for (localhost).

Deleting the sc_mode cookie that says edit or logging out from Sitecore seems to be the only way to fix this problem.

Is this a bug in Sitecore or what am I missing?

  • 2
    The session is shared. You need to run one in normal and one in incognito. Or use different browsers like Chrome and Firefox or whatever.
    – Mark Cassidy
    Aug 15, 2019 at 9:09
  • This still feels like a bug in sitecore though.
    – devzero
    Aug 15, 2019 at 9:47

1 Answer 1


Unfortunately it's how domain based cookies work. If you've got cookies saying you're in edit mode on domain.sitecore.local, it's going to render in edit mode whether you're connected or not, because both the connected mode data and the integrated data come from the same domain. You can quickly get out of edit mode by visiting your.sitecore.domain/?sc_mode=normal which is mildly quicker than deleting a cookie, or use incognito mode like @MarkCassidy suggested.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.