Session recording
Recording is not a feature you switch on per session. It is how sessions work. The fleet settings decide what happens when a session can't be recorded, and the only logins that go around the recorder are break-glass logins with the host's own credentials (Break-glass access) and any accounts you explicitly exempt.
On the host
A setgid wrapper records the session and writes straight to a spool directory the person cannot read or edit — and what it writes there is already encrypted for the Keyreeve servers (ECDH P-384 and AES-256-GCM), so not even root on the host can read a recording waiting to be sent. Where the host has cgroup v2, each session runs in its own cgroup; a guard ends any login whose processes escape the recorder, so a session cannot quietly outlive its recording. With auditd, the kernel's audit log adds a list of every program run in the session.
Recordings stream to the server as they happen. Each chunk is signed by the agent and chained to the one before it, so a missing piece is visible rather than silent. Administrators can watch a session live. Sessions through the web terminal, the desktop app and the gateway are also recorded by the server itself, so there are two independent copies.
If a session can't be recorded, the failure policy decides: by default everyone is refused except break-glass; it can also refuse everyone, or let people in and mark the session unrecorded.
What is stored, and what is not
Passwords and other patterns are redacted on the host, before the recording leaves it. Matches are replaced with keyed tags, so the same secret can still be correlated across sessions without being readable.
Recordings and program-log arguments are encrypted at rest (AES-256-GCM, a key per recording). Full-text search works through a blind index of keyed hashes, so it doesn't need the recordings decrypted. You can also choose to record output only.
Who may watch
By default administrators and the auditor role may watch recordings; you can restrict that to auditors only, and require a second person's approval before playback. Every playback is written to the audit log, naming who watched what and when. Audit → Recordings → How recordings are protected explains the whole chain.
Retention is set under Admin → Fleet settings → Retention (recordings, program log and logins, in days). Legal hold is put on an individual recording from its own page and keeps it past retention.
Strict mode
For hosts where nothing may happen unrecorded. Strict mode forces containment (a host without cgroup v2 refuses sessions rather than running them uncontained), allows no exempt accounts, keeps nothing past the session, never fails open, and turns off port forwarding, tunnels, X11 and agent forwarding. A host or host group can be put in strict mode on its own.
Keeping tmux and screen
By default a tmux or screen server survives the session that started it: the agent moves it into a cgroup of its own rather than killing it with the session. Reattaching later is a new, recorded session.
A kept multiplexer is ended when the person may no longer use the account, when the time limit passes, or when the setting is turned off. Strict mode never keeps anything.

