How to reset Google Cloud Shell user persistent disk?
<p>Ok, folks.  Pushing the limits (of my understanding), I've broken my Google Cloud Shell on Google Cloud Platform.  I can no longer open a shell session.</p>

<p>When I click the shell icon <code>&gt;_</code> on the tool bar, the shell opens on the lower half of the screen for a moment, stating it is provisioning the instance (if it has been over an hour), established a connection, and then poof, it closes.</p>

<p>I was able to time a screen capture just right to see the following:</p>

<p><a href="https://i.stack.imgur.com/Npo5a.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/Npo5a.png" alt="Cloud Shell, No such file or directory"></a></p>

<pre><code>Welcome to Cloud Shell! For help, visit https://cloud.google.com/cloud-shell/help.
-bash: /usr/bin/zsh: No such file or directory
</code></pre>

<p>I am pretty sure this relates to a naive attempt to install zsh ON A DIFFERENT PROJECT.  My theory is that the 5Gb of persistent disk storage provided by Cloud Shell is per user, not per user per project.  Therefore, my home directory is borked and will no longer load because the OS modifications are not persisted, only user home directories, and my <code>.bashrc</code> now references non-existent files.</p>

<p>So my question is this:  How do I start over, or wipe out the existing persistent disk and settings to obtain a working Shell again?</p>