---
title: "Jam | Console logs, network requests, and more"
image: "https://cdn-jam-screenshots.jam.dev/6ca02ebef155043556d65bb9004888f6/screenshot/92980779-cf83-406b-885d-fb9fe5931a57.png"
url: "https://jam.dev/c/d06529a5-7e33-4af4-8f3b-95c0c7c1638f"
capturedOn: "https://appp.gclick.com.br/dashboard"
type: "video"
browser: "Chrome 142.0.7444.176"
os: "Windows (x86) 10 2004/20H2/21H1/21H2"
screen: "1707x801"
country: "BR"
timezone: "America/Sao_Paulo"
author: "Daniel Rodrigues"
date: "2025-12-02T17:01:36.774Z"
---

## Signals

2 console errors · 3 failed requests (1 5xx) · 24 interactions

## Comments

**Anonymous** · 2026-06-09T11:52:45.178Z

HIMFTYHKRBVYTP5ZVTPIMIFNNXH7RJYXO4F3IJL4P5LPWEGWV5OA

## Not in this document

This is the summary tier. The captured events — console logs, network requests, user actions, and video frames — are not here: reading them needs filters, paging, and auth, so they live behind the Jam MCP server and CLI. Start at `getDetails`.

MCP: `https://mcp.jam.dev/mcp` (setup: https://jam.dev/docs/jam-mcp). CLI: `curl -fsSL https://native.jam.dev/install | bash` (https://jam.dev/docs/cli).