---
title: "Jam | Console logs, network requests, and more"
image: "https://cdn-jam-screenshots.jam.dev/c55973404c8a41b6a56a315f47a50f69/screenshot/050c0c00-b8ee-438c-9c4c-0966f50b7ba8.png"
url: "https://jam.dev/c/d48ac6aa-9ea9-415d-aa2e-f2bbee76a02a"
capturedOn: "https://tefalwebzine.co.kr/wp-admin/post.php?post=2693&action=edit"
type: "screenshot"
browser: "Chrome 140.0.7339.207"
os: "Windows (x86) 11"
screen: "2560x1271"
country: "KR"
timezone: "Asia/Seoul"
author: "planlee"
date: "2025-10-01T01:15:46.183Z"
---

## Signals

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