---
title: "Jam | Console logs, network requests, and more"
image: "https://cdn-jam-screenshots.jam.dev/503e048374349dad40c5d9cf6f6f8ce6/screenshot/1586e14a-966e-42cf-9dfa-4cd8a5ac9504.png"
url: "https://jam.dev/c/5dabaea6-04c0-4fa0-8b9f-240da8801f9f"
capturedOn: "https://chat.deepseek.com/a/chat/s/85989008-3059-4e36-ab18-24e0131da014"
type: "video"
browser: "Chrome 132.0.6834.110"
os: "Mac OS (arm) 10.15.7"
screen: "928x1058"
country: "IN"
timezone: "Asia/Calcutta"
author: "Saswat Marpureddy"
date: "2025-01-28T18:02:30.483Z"
---

## Signals

1 failed request (1 5xx)

## Comments

**Lindus** · 2025-04-24T20:09:30.273Z · at 0:46

eat beef than it will be fixed

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