---
title: "Jam | Console logs, network requests, and more"
image: "https://cdn-jam-screenshots.jam.dev/8d58afb0be8cdcedc95e6cd0e2ea4b06/screenshot/0193d423-a077-475a-874f-2e9851f39b65.png"
url: "https://jam.dev/c/8e6a07d8-e85a-4d46-be67-b20175026355"
capturedOn: "http://localhost:2025/"
type: "video"
browser: "Brave 141.0.0.0"
os: "Linux (x86) 6.14.0"
screen: "1920x951"
country: "BR"
timezone: "America/Sao_Paulo"
author: "Fernando Kawano"
date: "2025-10-07T12:06:35.211Z"
---

## Signals

1 console error · 14 interactions

## Links

- GitHub: https://github.com/kawanofer/met-museum-backend/issues/1

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