Sessions

A session is a workflow run — one execution of a workflow in your workspace. Sessions give you operational traceability: what you planned, what you completed, and what you recorded along the way.

WorkCheats does not execute commands during a session. Step completion records your session state only — it does not prove a command ran successfully in your environment.

Session lifecycle

Screenshot placeholder: Active session view showing current phase, step list, and progress indicators.

Step progress

Each step can be marked complete, skipped, or left pending. Progress is saved so you and your team can see where work stopped.

Do not assume step completion means a command was run successfully in your environment — it only records your session state in WorkCheats.

Notes, outputs, and attachments

During a session you can attach notes, outputs, and file attachments to steps:

• Notes — observations, decisions, or context for later review.
• Outputs — pasted command output or evidence text for traceability.
• Attachments — supporting files uploaded to a step output.

All notes, outputs, and attachments are user-provided content. Treat them as untrusted until you review them. WorkCheats stores them as text or files — it does not validate or execute them.

You can also send output notes or attachments into a linked report using Use in report when a report is linked to the session.

Session variables

Each session can hold independent variable values that apply only to that run. Session variables override workspace values for the session — they do not change workspace variable rows.

You can optionally enable Use workspace variables as defaults to fill gaps from your live workspace variables at resolve time.

See Session variables for full detail.

Protected sessions

You can add an additional passphrase before opening a session. Protected sessions show a Protected badge in the Sessions list.

See Protected sessions for unlock, lock, and cooldown behaviour.

Linked reports

When starting a session, you can link a primary report. The session page shows the linked report and supports Use in report — a manual flow to send selected output notes and attachment metadata into the linked report as evidence.

Linking does not auto-generate report content — you review and approve what is sent. See Reports lifecycle for report status, export, and archived-report evidence limits.

Read-only sessions

Sessions become read-only when:

• The session is completed or stopped
• The original workflow is archived — preserved sessions remain viewable; progress, notes, and outputs are kept, but you cannot change session state or start new sessions from that workflow. See Workflows for archive behaviour; use Favorites for how archived workflow bookmarks behave.

Session variables cannot be edited on read-only sessions.

Archived sessions in the list

The Sessions overview supports a Show archived filter for soft-archived sessions. Whether an archived session can be opened from the list may vary — if Open is unavailable, use session history from the original workflow where offered.

Operational traceability

Sessions support professional workflows where you need an audit-friendly record:

• Which workflow was followed
• Which steps were completed and when
• What was written in notes and outputs

Use sessions for documentation discipline, not as a substitute for your organisation's official evidence handling policies.

Current

• Start, resume, complete, stop, and delete (archive) sessions from workflows
• Multiple concurrent active sessions per workflow
• Step progress, notes, output text, and attachments
• Independent session variables with optional workspace defaults
• Protected sessions with passphrase unlock
• Linked reports and use-in-report evidence from step outputs
• Read-only access when workflow archived or session completed/stopped

Roadmap

The following are not available yet:

• CLI output capture and placeholders — structured capture via wcheats (see wcheats CLI)
• Export session evidence bundles to external systems
• Real-time collaboration on a single active session

See Security & Responsible Use for content safety expectations.