> ## Documentation Index > Fetch the complete documentation index at: https://jam.dev/docs/llms.txt > Use this file to discover all available pages before exploring further. # DevTools > Inspect console logs, network requests, user events, and device info inside every Jam. The same toolkit engineers use in the browser. Every Jam capture includes developer information to help engineers debug faster. Get instant access to console logs, network data, and environment details without switching between tools or losing context. ## Core Features Screenshots and screen recordings with annotation tools URL, timestamp, device info, browser version, OS and more Console logs and complete network request details and more Clicks, navigation events, and more Send DevTools context to AI agents so they can inspect logs, network requests, and user events. ## Layouts Switch between side and bottom layouts to fit your workflow: DevTools appear on the right side in the properties panel for wide-screen debugging. Ideal when you need to see both the captured page and technical details simultaneously. Hide DevTools to show only the visual captured content and activity including comments. ## FAQs No. DevTools data is automatically captured with every Jam. No setup or configuration required. You can capture additional meta data with [Custom logs](/custom-logs). Yes. Use the severity filter to show only errors, warnings, or specific log levels that matter for debugging. You get complete timing breakdowns including DNS lookup, connection time, and response duration, matching the data engineers expect from Chrome DevTools.