Local session recordings

The Driftstack desktop app can record the streamed frames from a live, hands-on session for local replay. The recording stays in the app's local data directory, and you can save it as a video file (MP4, or a QuickTime MOV where the app cannot make an MP4) to your Downloads folder. The video is made on your computer; nothing is uploaded.

Record from the desktop app

1. Open a live session in its session window.
2. Choose Record while the stream is connected.
3. Choose Stop to finalise the local recording.
4. Open Recordings to replay it, or choose Save recording as video.

The app captures one frame per second, so a saved video plays at one frame per second. A recording stops itself after 20 minutes and is saved.

If you close the app while a recording is still in progress, it is saved automatically. Your recordings are listed when the app starts and loaded when you open one.

API captures

On hosted Driftstack, a screenshot is a capture step in an agent session (POST /v1/agent-sessions/<id>/steps); fetch the image by its captureId with GET /v1/agent-sessions/<id>/captures/<captureId> soon after, as captures are kept for at most 30 minutes. See fetch a captured screenshot.

On a self-hosted deployment, API sessions expose explicit screenshot, DOM snapshot, and PDF captures through POST /v1/sessions/:id/capture. Capture bytes are returned inline in the response for your application to store. See the Sessions API reference.

Storage boundary

• Desktop recordings are local to the operator's machine.
• They are not uploaded by the recording workflow, and saving one as a video happens on the same machine.
• API captures are returned directly and are not retained by the capture endpoint.
• A screenshot an agent session takes is kept for at most 30 minutes, and none after the session ends.

Support

For recording or export help, email [email protected].