---
title: "Jam | Console logs, network requests, and more"
image: "https://cdn-jam-screenshots.jam.dev/c1379338d3d78cb0da8f7cba4dc10f19/screenshot/ea8fb3b1-5e09-41aa-98e8-e0271333c71e.png"
url: "https://jam.dev/c/f19bd243-4c06-46f2-8a4f-cd52a8d35598"
capturedOn: "https://vercel.com/login?next=%2Fsso-api%3Furl%3Dhttps%253A%252F%252Fwww.arcanys.com%252Finsights%252Fdetails%252Fwhy-you-need-a-software-architect-on-your-team%253F__vercel_draft%253D1%26nonce%3D717159545de1c063648c116c15286f3a356b1fabf89cdba43bfca9d652e8c1a0"
type: "video"
browser: "Opera 114.0.5282.185"
os: "Windows (x86) 11"
author: "Nash Belandres"
date: "2024-11-25T06:47:47.615Z"
---

## Get the full capture

This page is a summary. The console logs, network requests, video/screenshot, and device info are exposed through the Jam MCP server — connect an agent to `https://mcp.jam.dev/mcp` and start with `getDetails` (setup: https://jam.dev/docs/jam-mcp).

Prefer the terminal? Install the Jam CLI: `curl -fsSL https://native.jam.dev/install | bash` (https://jam.dev/docs/cli).