Jam helps support, product, and engineering teams capture bugs with console logs, network requests, and device info attached. More than 250,000 users already capture bugs this way.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.
Two ways to create Jams
Record a Jam yourself
Capture issues while working with the Chrome extension or iOS app
Request a Jam from anyone
Collect recordings from customers, teammates, or external collaborators
| Use case | Best for | When to use |
|---|---|---|
| Request a Jam from anyone | Collecting recordings from customers, teammates, or external collaborators | Customer bug reports, async user feedback, or remote debugging with your team. |
| Record a Jam yourself | Capturing issues while working | Testing your own product, documenting bugs during development, or capturing issues in real time. |
What gets captured automatically
Every Jam automatically captures essential debugging information.
Visual context
Screenshots and screen recordings with annotation tools
Custom logs
URL, timestamp, device info, browser version, and operating system
Developer logs
Console logs, network requests, errors, and warnings
User events
Clicks, navigation events, and typed input
Customization options
Jam’s default capture covers the essentials. You can extend it with custom logs and integrations.Jam SDK
- Custom logs. Push additional context from your app into Jam with a single function call.
- Recording links with console logs. Configure Recording Links to capture console and network logs from customers, with no install required on their end.
Integrations
- Sentry integration. Connect Sentry to show backend errors directly alongside your Jam.
Next steps
Create your first Jam
Capture an issue yourself
Create a Recording Link
Collect issues from customers or teammates