> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tekma.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Tekma documentation

> Capture browser bugs, share recordings with debugging context, and connect Tekma to your team and AI tools.

Tekma turns a browser problem into a recording your team can investigate. Capture what happened, review the accompanying technical context, and share the result in one link.

<CardGroup cols={2}>
  <Card title="Record your first bug" icon="video" href="/getting-started/quickstart">Connect the browser extension and publish a capture.</Card>
  <Card title="Record with an AI agent" icon="terminal" href="/developers/cli">Install the CLI and create a shareable browser walkthrough.</Card>
  <Card title="Review a recording" icon="play" href="/recording/playback">Navigate chapters, search the transcript, and inspect failures.</Card>
  <Card title="Request a recording" icon="link" href="/sharing/recording-links">Let someone send a reproduction to your workspace.</Card>
</CardGroup>

## What is included in a capture?

| Context                 | What it helps you understand                             |
| ----------------------- | -------------------------------------------------------- |
| Video or screenshot     | What the person actually saw                             |
| Console messages        | Errors and warnings produced during the capture          |
| Network activity        | Requests, responses, failures, and timing where captured |
| Browser actions         | The sequence of interactions that led to a problem       |
| Chapters and transcript | Where to jump in a recording and what was said           |

The available context depends on the recording method, browser permissions, and workspace privacy rules. A recording is a bounded snapshot; it does not monitor your browser continuously.

## A simple reporting workflow

1. Reproduce the problem while recording.
2. Review the capture and give it a descriptive title.
3. Choose whether the share includes debugging context.
4. Send the link to a teammate or your connected issue tracker.

For example, **“Checkout: discount code clears the delivery address”** gives the next person more context than **“Bug”**. Add the expected result in a comment and point to the moment the behavior changes.

## Choose your next step

Use the [browser extension](/getting-started/extension) for everyday reporting, [recording links](/sharing/recording-links) for collecting reproductions, or the [CLI and MCP tools](/developers/overview) for agent workflows.