Goal
Find and review what happened in a session, and understand how long recordings are kept.Prerequisites
- terminal.view_history for history; terminal.view_recording / terminal.download_recording for recordings
Workflow
Recordings
Recorded sessions are stored as asciicast streams and can be played back in the dashboard or downloaded. Production sessions are always recorded; non-production recording can be required by policy.Retention and purging (no manual delete)
Recordings are retained for a configurable number of days — separately for production and non-production — and then purged automatically by the platform on an hourly retention sweep. There is intentionally no manual delete button: recordings age out and are removed on their own once past retention. Adjust retention days in the terminal policy if you need a shorter or longer window.History and active sessions
- History lists sessions with target, environment, mode, reason, timestamps, and close reason.
- Export combines session records with terminal/database audit events (CSV or JSON).
- Policy managers can revoke a live session; users can reconnect to their own dropped session within the grace window.
Expected result
You can audit terminal activity and replay recorded sessions within their retention window.
Related guides
Production safeguards and approvals
How a target’s environment is classified, why production access is gated, and the reason/approval flow members must follow.
Terminal policy and file transfer
The policy controls owners/admins use to govern terminal behavior, plus browsing and transferring files within a session.
Terminal workspace overview
The per-project operations workspace where you open application and database shells, run runbooks and commands, and review session history and recordings.