Skip to main content
The Tekma browser extension records tabs and screenshots with browser debugging context. Install it in the browser profile you use to reproduce problems.
Tekma currently distributes the production extension as an installation package supplied by your workspace administrator. The app’s Settings → Browser extension page contains the environment-specific installation guide.

​
Install the package

  1. Obtain the production ZIP from your workspace administrator and extract it.
  2. Open chrome://extensions in Chrome.
  3. Enable Developer mode, then select Load unpacked.
  4. Select the extracted folder containing manifest.json.
  5. Open Chrome’s extensions menu and pin Tekma to the toolbar.
Keep the extracted folder in a permanent location: an unpacked extension loads its files from that folder. Use the production build when connecting to tekma.dev; development builds connect separately.

​
Connect a workspace

  1. Sign in to Tekma in the same browser profile.
  2. Open the Tekma extension and select Connect securely.
  3. Choose the workspace on the approval page and approve the connection.
  4. Keep the popup open while the connection finishes.
  5. Return to Settings → Browser extension and confirm that the browser appears as Connected.
You must be a workspace owner or member to connect a browser. Connections expire after 90 days without use and at most one year after pairing. Reconnect when prompted.

​
Update or disconnect

For a new package, replace the installed build as instructed by your administrator, select Reload on its extension card, and refresh the page you want to capture. Reconnect if requested. To remove upload access, open Settings → Browser extension, find the connected browser, and select Disconnect. Existing captures remain available. You can connect the browser again later.

​
If pairing does not complete

Check that you are signed in to the correct account, selected the intended workspace, and installed the production build. Refresh the settings page to check the connection. If necessary, restart the pairing flow from the extension instead of reusing an old approval page. See recording troubleshooting for permission and recording failures.