Stop the workspace at the end of the day

When you are done, you can stop your workspace. Repositories, uncommitted work and sessions stay, and the next start picks up where you left off.

How it works

What you do	What happens
Commit and push the changes that matter	The changes also exist outside the workspace
Stop it with the power button on the workspace action bar	Running sessions become “stopped”; files and logins stay
Start it with the power button the next day	A click resumes each stopped session

Commit and push the changes that matter. Uncommitted changes exist only inside the workspace (Connect a Git service)
Stop a session at a good break with Stop (resumable later) in its ⋯ menu, and it resumes straight away next time (Stop and resume a session)
A session you want to keep running does not need to be stopped

When it is stopped, these stay.

What stays	At the next start
Cloned repositories and uncommitted changes	Ready to use
The list of sessions	Kept as stopped; click one to resume it
Logins to agents and Git services	Ready to use

While the workspace is stopped, Session history in the left pane still lists the sessions. Acting on them waits until it is started
Previews and opencode web are disconnected

When the Console is updated, an A new version is available notification appears.

Update on the notification only reloads the browser. Running sessions do not stop
When the update includes the workspace side as well, a Restart needed badge appears on the workspace action bar

Press Restart needed and choose Restart now to stop the workspace and start it again.

Running sessions become stopped and can be resumed later. Repositories and files stay as they are
There is no hurry. Stopping at the end of the day and starting the next day applies it too. The badge goes away once the workspace starts on the new version

What changed is in the release history.