---
title: "Jam | Console logs, network requests, and more"
image: "https://cdn-jam-screenshots.jam.dev/e7f3f2f064001f51df030b534b339a33/screenshot/24e2b5b7-1f8b-413e-9376-0a842358fc7f.png"
url: "https://jam.dev/c/44c7c829-3f83-4e48-99ab-7311213777aa"
capturedOn: "https://aiagentsdirectory.com/agent/agenta"
type: "video"
browser: "Chrome 150.0.7871.187"
os: "macOS (arm) 26.5.1"
author: "sonic"
date: "2026-08-02T10:25:45.911Z"
---

## Transcript

here is the quick demo of the analytics design that i created we have three parts of this design first is this short summary then we have this analytics and then we have these two analytics um the short summary i felt like i need a quick view of what's happening so instead of going the details this helps me to quickly see everything in few seconds what's happening right not sure about the workflow health or agent health you can say uh it's experimental maybe not going in the first iteration we have filters for time will filters for agents models is not going on the first iteration in first iteration it will mostly be a summary quick summary not this maybe and we have this for uh analytics and so this is the second part uh we already have this so no back-end changes no back-end changes here we can compute we can do this in front and we have this in front and already for this to why this is out of scope for the first iteration because it requires uh back-end uh changes uh we get this information from the root span but to get this information we need to get into the child span which is currently we are not doing in the analytics so it's out of scope for the first iteration so for the first iteration the summary is when we will get a summary card and this four charts of the analytics we have over information we have filter here i think it's like useful for me but let me know your thoughts i will share the i will share the design with you

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