---
title: "Jam | Console logs, network requests, and more"
image: "https://cdn-jam-screenshots.jam.dev/4d6d1a8876b7a7406b445153ca7a3020/screenshot/20c962e7-68c0-40c5-9fe5-69c7abc50911.png"
url: "https://jam.dev/c/3affe11c-bf5c-4140-8e35-6aaa5862a94a"
capturedOn: "https://uat.pixally.com/contract/event/7f8b729a-1454-4fc8-97fb-7d1e12622e78/edit?projectId=e0ed5104-0f5a-444f-a871-569a93a5ffd8&returnTo=%2Fproject%2Fe0ed5104-0f5a-444f-a871-569a93a5ffd8%2Fdetails"
type: "video"
browser: "Chrome 130.0.6723.69"
os: "Linux (x86) 5.15.0"
screen: "1868x966"
country: "IN"
timezone: "Asia/Calcutta"
author: "jasleen.k+++"
date: "2026-08-25T06:46:01.063Z"
---

## Signals

35 failed requests · 84 interactions

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