Skip to main content
Tekma has separate paths for reading an existing capture, recording a new one, and receiving a ready event:

Access choices

Use OAuth for a person’s authorized workspace. Use a personal access token for bounded workspace reads and supported writes. Use a recording-link token only for a link-scoped guest upload. Use local mode when media must stay on the machine. Each path has separate workspace roles, scopes and privacy behavior; a read credential does not authorize recording or capture edits.

A useful agent loop

  1. Read capture details and diagnostics.
  2. Locate the failure and timestamp.
  3. Fix and test the project.
  4. Record the corrected behavior with the CLI or extension remote control.
  5. Verify the returned capture, share audience and playback before reporting success.
Continue with authentication or the command reference.