I primarily interact with my workspace via VS Code Remote SSH by clicking my workspace in the sidebar. However, it's often off.

I'm proposing the following behavior:

1. When I SSH into a stopped workspace (e.g.ssh coder.ben-stable), the workspace starts and streams the build log until it is finished. Then, the SSH connection starts. No need for the user to confirm. They clearly want to access their workspace.

   • Perhaps a configurablecoder config-ssh --disable-auto-start flag could disable this behavior. Doesn't seem necessary though

2. When I visit a URL for an app on an agent (e.g.https://dev.coder.com/@bpmct/ben-stable.dev/apps/code-server/?folder=/home/coder/coder), the workspace starts and I can follow along with the build log. Once complete, and the app health check passes, I am redirected to the app. Related:Support starting the workspace when launching acoder_app when it's off #2909

   • If the user does not own the workspace, but only has access to the app, perhaps it displays some generic "Starting workspace..." text?

To validate:

• Will this work OK with VS Code Remote SSH (the primary way I connect to my workspace) or do we needVS Code Extension #3597?