---
title: "Jam | Console logs, network requests, and more"
image: "https://cdn-jam-screenshots.jam.dev/b27fd8fa6c4c4e85825f239778725df3/screenshot/31713a61-f14c-4dc5-a558-9ee070a2df61.png"
url: "https://jam.dev/c/72d6248d-4a95-48c3-9319-ccf31b05f9e4"
capturedOn: "https://tefalwebzine.co.kr/wp-admin/post.php?post=2693&action=edit"
type: "screenshot"
browser: "Chrome 140.0.7339.128"
os: "Windows (x86) 11"
screen: "2560x1271"
country: "KR"
timezone: "Asia/Seoul"
author: "planlee"
date: "2025-09-26T02:23:21.997Z"
---

## Signals

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