Skip to main content
Tekma turns a browser problem into a report that someone else can reproduce. Choose the capture path that fits the situation:
  • Record in this browser uses the connected extension for a tab, desktop or window recording, screenshot, or Instant Replay.
  • Ask someone else to record creates a recording link. The recipient can submit without joining your workspace.
  • Record from the CLI or an agent uses the capture/tekma CLI, MCP, or a connected application.

​
What a capture can contain

Depending on the capture kind and privacy rules, a report can include video or an image, the page URL, browser actions, navigation, console messages, network requests, environment details, and optional audio. Video recordings receive automatic chapters; narrated recordings can receive a timed transcript. Screenshots and imported media do not gain browser diagnostics that were not present in the source. The capture page puts the evidence beside the player. DevTools shows console, network, request details, environment and detected libraries when that bundle is available. A content-only share intentionally withholds those diagnostics.

​
Start with a task

Create your first capture

Connect the extension, record a short reproduction, inspect it, and share it.

Request a recording

Send a guest link when another person has the problem.

Inspect a capture

Use chapters, transcript search and diagnostics to find the failure.

Automate with the CLI or MCP

Record, read and update captures from development tools.

​
Access and privacy in one view

Workspace members can see captures according to their role and any folder restrictions. Owners and members can create captures, edit them and make links; viewers can review and comment. An Anyone with the link URL is bearer access to the permitted content, while a Workspace members only URL still requires membership. Review either link like access material and revoke it when the investigation ends. Built-in capture protection and workspace privacy rules reduce sensitive diagnostic data, but they cannot guarantee that every secret is hidden from video pixels or audio. Use test data, configure visual masks where appropriate, and inspect the actual result before sharing. If you are working in desktop Chrome or Chromium, follow the first capture guide. If someone else needs to demonstrate the problem, use recording links. Developers can begin with the CLI and MCP overview.