How sessions work
Active, archived, cloned, resumed, and imported session behaviour.
A session is the persisted container for one assessment run under
server orchestration.
What a session contains
- current phase pointer (server-owned)
- per-phase JSON artifacts (and DOT where applicable)
- message / step history for the guided flow
- preview and protocol state
- final report revisions and session-scoped uploads
Active session model
Normally you have one active session. Creating a new active session archives other active ones for your user. Returning to the product resumes the latest active session. When access is credit-based, becoming active reserves a credit.Resume, clone, import
- Resume — reopen an archived session when the product allows it
- Clone — branch from prior work (supported after issue/archive); clone can reset AI budgets under report rules
- Import — create an active session from an export payload