You can add the host to /tools/sidekick/config.json, which will be fetched every time the sidekick is loaded.

@rofe we did the same thing couple of weeks back, but the side kick isn't fetching the new host configuration and not showing edit/preview when we're on the production host https://www.theiotintegrator.com/ but the same is working fine when we're on https://main--channelco-iot--hlxsites.hlx.live/

May I ask when this functionality was added to sidekick?

cc: @amol-anand

@ravkiran you're right, i got confused: before the sidekick can read the config.json, the extension needs to know when to inject the sidekick in the first place - classic chicken/egg :)

So as you already pointed out, the only workaround for early users is currently is to remove and re-add the project. This is a 5 seconds operation via the extension's context menu. Alternatively (or additionally) we could add a "refresh" button to the project config on the options page, but that would probably even take the user longer than removing and adding the project again. And once they found the options page, they can also quickly add the host name for their project manually.

The 3rd option that comes to mind is for the extension to periodically auto-refresh all project configs, say on startup, or when the browser is idling. But I'm a bit worried about that generating a lot of (mostly useless) traffic.

Thank you @rofe for the alternate proposals.

Alternatively (or additionally) we could add a "refresh" button to the project config on the options page,

This sounds good to me, we can document this with screenshot easily and ask the customer just to click on the refresh button agains main--.... Asking the customer to remove and re-add seems counter intuitive IMHO.
I like the third option too, but rather than periodic refresh, I think its better to add a Refresh button in the right click of the sidekick and that will refresh all the projects. As you've pointed out this could lead to more traffic, but this option is doing only when the user Refreshes manually, rather than periodically.
WDYT?

Actually, I like the context menu option, but I'd probably limit it to the current project to minimize the impact. I don't think refresh all is a common use case, and most people probably only have 1 or 2 projects configured.

Fixed with #723