When using Continue On from a RemoteHub workspace, the only private state we have to worry about is uncommitted changes, because all existing commits are by definition pushed to the remote, and the branch we are on is already guaranteed to exist. This is not the case for desktop git repositories, because in that scenario we may have newly created branches which have not yet been published to the remote, or we may have local commits which have not yet been pushed to the remote.

Ideally when the user invokes Continue On and selects a target workspace, we would allow the publishing of local state so that the target environment can take this state into account.