---
title: "Jam | Console logs, network requests, and more"
image: "https://cdn-jam-screenshots.jam.dev/3ba8abea7a145ede6d4a179f54706daf/screenshot/b0d07fa3-1380-4dc9-a956-4ecf23bf9e10.png"
url: "https://jam.dev/c/b1b44ce9-1252-422f-a7c5-dd1d8b877464"
capturedOn: "https://www.maco-design.nl/maatwerk-interieur/"
type: "video"
browser: "Brave 128.0.0.0"
os: "Windows (x86) 11"
screen: "2543x1311"
country: "NL"
timezone: "Europe/Amsterdam"
incognito: "true"
author: "marketing"
date: "2024-09-05T11:19:33.492Z"
---

This happens in incognito mode - so might be cache related. But this wasn't happening before.

## Signals

9 failed requests · 3 interactions

## Comments

**marketing** · 2024-09-05T11:19:33.492Z

This happens in incognito mode - so might be cache related. But this wasn't happening before.

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