Jam helps support, product, and engineering teams capture bugs with console logs, network requests, and device info attached. 250K 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
Directly capture issues while working via Jam’s Chrome extension or iOS app
Request a Jam from anyone
Getting recordings from users, customers, or members
| Use Case | Best for | When to use |
|---|---|---|
| Request a Jam from anyone | Getting recordings from users, customers, or your team | Customer bug reports, a-sync user feedback, or remote debugging with your team. |
| Record a Jam yourself | Direct issue capture 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, OS and more
Developer logs
Console logs and complete network request details and more
User events
Clicks, navigation events, and more
Customization options
Jam’s default capture covers the essentials. You can extend it with custom logs and integrations.JamSDK
- 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 surface backend errors directly alongside your Jam.
Next steps
Create your first Jam
Learn how to capture issues by yourself
Create a Recording Link
Learn how to collect issues from others