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.
Workspace Resumed Sessions and Resume Commands
Where you see this in the app
This page documents what happens when the app resumes an existing workspace session instead of starting a completely new one.
Users see this through messages such as Workspace session resumed and through session-resume actions inside the workspace tooling.
Started vs resumed
A resumed session is not the same as a newly created one.
| Message | Meaning |
|---|---|
Workspace session started | A new session was created for this launch |
Workspace session resumed | The app found an existing compatible active session and reused it |
This is a convenience feature. It helps users continue work without unnecessarily opening a fresh parallel session each time.
What resumedFromSessionId means
resumedFromSessionId is the identifier of the existing session the app chose to continue.
From an end-user perspective, it means the current launch is attached to an already-active workspace session rather than a brand-new one.
When the app reuses a session
The app only resumes when the existing session is compatible with the current launch request.
The important user-facing idea is:
- same post,
- same user,
- same session mode,
- still active and not expired.
If those conditions are not met, the app starts a new session instead.
Resume commands and expectations
Users can also encounter resume behavior in the tooling itself, such as codex resume <session-id>.
That command is for continuing a previous Codex-side session. It should be understood as related to the same continuity idea: pick up where a previous run left off instead of starting from zero.
Users should not assume resumed sessions are permanent. They are only reusable while still active and valid.
Related docs
Related docs
See it in action
Previous
Workspace Preview Embed vs New-Tab Fallback
How the app chooses between embedded workspace preview and opening a separate preview tab, and what users should infer when the workspace starts but the inline embed is unavailable.
Next
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.