> ## 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.

# Read DevTools evidence beside a capture

> Use console, network, actions, environment and backend context to investigate a browser reproduction.

Open a workspace capture and choose **Show DevTools**. The panel can contain these tabs:

| Tab         | What to use it for                                                                                                           |
| ----------- | ---------------------------------------------------------------------------------------------------------------------------- |
| **Info**    | Browser, operating system, viewport, timezone, connection estimate, extension version and detected libraries when available. |
| **Console** | Filtered console messages, severity, timestamps and call stacks.                                                             |
| **Network** | Requests, failures, status, method, duration, resource type and safe bounded previews.                                       |
| **Actions** | Recorded clicks, inputs without values, navigation and other user events.                                                    |
| **Backend** | Custom metadata or server-side context explicitly supplied by the capture workflow.                                          |

Optional Sentry context appears only when the workspace owner connected a readable Sentry project. It is fetched from Sentry around the capture time and is not public-share or AI evidence.

## Filter and follow an event

Use console severity and stream filters to reduce noise. In Network, choose **Network errors only** or a resource type. Select an entry with a timestamp to seek the player to that moment. Connection speed is a browser estimate, not a speed test; missing environment fields are omitted.

Request and response bodies can be absent, bounded, redacted or unavailable. Tekma does not expose cookies or claim to mirror every live DevTools panel. WebSocket information is content-free metadata. Treat temporal proximity as a clue, not proof of root cause.

## Shared diagnostics

Only **With DevTools** links carry the permitted diagnostic bundle. **Without DevTools** links carry visual content and playback navigation only. Shares still apply expiry, revocation, audience and workspace privacy. A content-only share cannot be upgraded by opening it through MCP.

For missing diagnostics, check the share mode, capture kind, privacy policy and processing state before recording again. See [privacy](/recording/privacy) and [MCP access](/developers/mcp).