Workspace Close Session vs Close All
How closing one workspace session differs from closing all active sessions, where each action appears, and what users should expect from single-session cleanup compared with global cleanup.
Workspace Close Session vs Close All
Where you see this in the app
This page documents the difference between closing one active workspace session and using the broader Close all active workspaces cleanup action.
Users can encounter these controls in slightly different places:
- a post workspace can expose a direct
Close workspaceaction for the current session, - account-side usage panels can show one-by-one close controls for active sessions,
- concurrency recovery flows can surface
Close all active workspaces.
Close one vs close all
These actions solve different problems.
| Action | What it is for |
|---|---|
Close workspace | Stop the current session you are actively using |
| Close one session from active-workspace lists | Stop one specific session without touching your other sessions |
Close all active workspaces | Global cleanup when session pressure or concurrency limits make broad cleanup easier |
From an end-user perspective, single-session close is the precise tool. Close-all is the recovery tool.
What single-session close does
A single-session close tells the app to stop one identified workspace session only.
After a successful close, users should expect:
- the current workspace session to stop,
- current embed or live preview state for that session to clear,
- related session-specific history or tool panes to reset,
- a confirmation such as
Workspace closed.
It does not imply that every other active workspace session owned by the same user also stops.
When global cleanup fits better
Global cleanup is more appropriate when the problem is not one bad session but overall session pressure.
Typical examples:
- the app says controllers are busy,
- the user hit a concurrent-session limit,
- a retry flow explicitly recommends cleanup before relaunching.
In those cases, closing one session may help, but close-all is the more reliable reset because it clears every active interactive session instead of asking the user to guess which one is blocking the next launch.
What users should expect after each action
Users should interpret the outcomes like this:
| Outcome | Practical meaning |
|---|---|
Workspace closed | The chosen session stopped successfully |
Close failed | That specific session could not be closed right now |
Active workspaces closed | Global cleanup succeeded |
Workspace cleanup partially complete | Global cleanup closed some sessions but not all |
So the main difference is scope: one session versus every active session that matters to the current cleanup flow.
Related docs
Related docs
See it in action
Previous
Workspace Resumed Sessions and Resume Commands
How the app resumes an existing interactive workspace session instead of always starting a new one, and what resumed session messages and resume commands mean for end users.
Next
Workspace Close-All Cleanup and Partial Failures
How the Close all active workspaces action behaves, what full vs partial cleanup results mean, and how retry-after-cleanup works when a launch was blocked by concurrency limits.