Skip to main content

​
Launch a browser yourself

Interact with the opened browser, then stop it:
The result reports upload status, capture identifiers and any share URL permitted by workspace policy. Open the returned capture and verify playback; an upload acknowledgement is not proof that the video shows the intended behavior.

​
Attach to an existing browser

Start Chromium with a loopback DevTools endpoint, then run:
The recorder attaches as a second CDP client and follows the focused page selected at start. It does not follow a tab opened later. Keep the debugging port on loopback and close it after the run. Guest automation can supply a recording-link token and API origin instead of OAuth. For a result that never uploads, use:
The saved video has no element-level redaction. Input values are not captured as action text, but visible page pixels can still contain secrets.

​
Recover and troubleshoot

Use tekma record status before starting another session. Keep the recorder directory after an interruption, check FFmpeg and browser permissions with tekma doctor, and retry only after checking whether the server already created a capture. A browser that cannot stream video can still produce diagnostic events; verify the output fields instead of assuming media succeeded.