I'm labelling as bug since this is a negative surprise and threatens the usability of the Auto Off feature in general.

My workspace was about to shut off, I pressed the extend button in the UI, and my workspace was extended to about an hour. First of all, I'm confused what "about an hour" means. That could mean 40m or 1h20m, which is a huge difference. The better experience is showing mewhen it will shut down. That avoids the need for an opinionated duration precision or live countdown timer (visual distraction).

Second of all, when I'm coding it's rarely for an hour sprint. I'm probably coding for a few hours at least, so now Auto Off is this distracting thing I have to remember to extend every hour. It kills my flow. This is the point I disable Auto Off or stop using Coder if I can't disable it.

If we want to keep it constant, it should be 4 hours or more. The best experience for a user is a time entry where I choosewhen my workspace will shutdown. The same timebox that showswhen the workspace is shutdown should be used to mutate thewhen. This is a simpler UI than what we have now as well.

If we go down the time route, we should make sure to display it in the browser's timezone instead of the timezone scheduled in Auto-Start, as this display is ephemeral.

cc@vapurrmaid

and@tjcran and@misskniss since I think this is a big impact to UX