Sessions inspector

The sessions inspector is a read-only window into terminal sessions running on your machines. It shows live transcripts, exit codes, and metadata. It does not run new commands.

Web terminal in the cabinet is now view only. The interactive shell still loads for backwards compatibility, but new commands launched from the cabinet are flagged in audit and may be blocked by workspace policy.

What a session is

A CMDOP session is a first-class object — a server-stored record of a PTY (or a persistent multi-command shell) that survives client disconnects. See Concepts: remote sessions for the full model. The inspector shows whichever sessions are visible to you per workspace and per-machine access.

Sessions list

The list separates active and ended sessions. Filters:

Machine — narrow to one host.
User — sessions started by a specific member.
Workspace — usually fixed to the active workspace.
Time range — last hour, day, week, or custom.

Inspecting a session

Clicking into a session reveals:

Live transcript — read-only stream of stdout / stderr.
Exit code and duration.
Attached clients — desktop, CLI, bot, or this browser tab.
Associated chat thread — if the session was driven by a chat conversation.

The transcript is bounded by a per-session ring buffer. Older output may be truncated; the inspector flags gaps.

Re-attaching from desktop or CLI

Need to actually drive the session? Each session row exposes:

Open in desktop — deep link (cmdop://session/<id>) that hands off to the desktop Machines tab.
CLI snippet — cmdop terminal attach <session-id> ready to copy.

The cabinet does not provide an interactive shell anymore.

Need to actually run something? Use cmdop connect <machine> (CLI) or open the Machines tab in desktop.

Mint a read-only share link for a teammate or external reviewer:

TTL — hours granularity (90 m rounds up to 2 h); 0 = never expires.
Scope — exactly one session on exactly one machine.
Guest access — read-only by definition; the guest can scroll the transcript but cannot send keystrokes.

For full mechanics, see ../../guides/terminal/share-links.

Compliance

Transcripts are retained per the workspace plan (typically 30–365 days). Exports as plain text or JSON; webhooks can ship transcripts to a SIEM. Retention windows configured in Workspace settings.

Where this data lives

Backed by the Django terminal app (sessions, commands, shared); rendered by apps/my/.../dashboard/command/.