Jam - Gitlab Debugging Plugin with Screen Recording

TL;DR

TL;DR: Jam is a browser extension that turns bug reports into replayable sessions — screen recordings bundled with console logs, network requests, and device info — integrated directly into Gitlab as a plugin.

What Is Jam?

Debugging existing systems is one of the most frustrating parts of software engineering. Even with a clear bug report, reproducing the exact conditions that caused the issue often requires multiple back-and-forth calls with the reporter.

Jam is a browser extension that solves this by automatically capturing everything a developer needs to reproduce a bug: a screen recording, console logs, network requests, device details, and user events — all bundled into a single shareable session and attached directly to a Gitlab issue as a plugin.

The core product claim is straightforward: instead of three calls to understand a bug, you get one replayable session that has all the context baked in.

Setup Workflow

Step 1: Install the Browser Extension

Jam is available as a browser extension for Chrome and Firefox. Install it from the Jam website:

# Visit the Chrome Web Store or Firefox Add-ons page
# Search for "Jam - Debugging for developer teams"
# Click "Add to Chrome" / "Add to Firefox"

After installation, the Jam icon appears in your browser toolbar.

Step 2: Connect to Gitlab

1. Open Gitlab and navigate to your project
2. Click the Jam icon in your browser toolbar
3. Sign up or log in with your email or SSO
4. Authorize the Gitlab integration when prompted
5. The Jam panel now appears in your Gitlab issue view

No server-side installation is required — the plugin runs entirely in the browser.

Step 3: Record a Bug Session

When you encounter a bug in your app:

1. Click the Jam extension icon in the toolbar
2. Click Record — Jam begins capturing your session
3. Perform the actions that reproduce the bug
4. Click Stop to end the recording
5. Optionally add a text description of the issue
6. Click Attach to Gitlab Issue and select the relevant issue

The recording is processed and attached to the Gitlab issue as a Jam session.

Step 4: Review a Bug Session

When viewing an issue with a Jam recording attached:

1. Click the Jam session link in the issue
2. The session opens in the Jam player with timeline scrubbing
3. You can replay the full session and inspect:
   • Console logs — full output with filterable log levels
   • Network requests — all HTTP requests with headers and response bodies
   • Device info — browser, OS, screen resolution, and viewport size
   • User events — clicks, key presses, and scroll events

You can scrub through the recording and click on any captured event to jump to that moment.

Deeper Analysis

What Makes It Different

Traditional bug reporting requires the reporter to manually describe steps, environment, and behavior. Jam automates the data collection — every session is self-contained and replayable.

Key differentiators from tools like Loom or CloudApp:

• Automatic context capture — console logs, network, and device info are collected silently, not manually exported
• Gitlab-native integration — sessions attach directly to issues, no copy-pasting links
• Timeline inspection — click any captured event to jump to that moment in the recording

Gitlab Plugin Architecture

Jam installs as a Gitlab Marketplace app scoped to your group or project. Once installed, it appears as a sidebar panel in Gitlab issues. The plugin uses Gitlab’s OAuth 2.0 flow for authentication.

The extension itself runs client-side and does not require a self-hosted server component.

Recording Storage

Sessions are stored on Jam’s cloud infrastructure. Each recording is assigned a unique URL that can be shared independently of Gitlab.

Limitations

• Browser-only — Jam only captures browser-based sessions; server-side bugs, mobile app issues, and desktop application bugs are outside scope
• Performance overhead — active recording may add slight latency to the browser session being recorded
• Privacy — recordings capture all browser activity in the active tab; teams should be aware of what is being recorded
• Free tier limits — the free plan includes a limited number of sessions per month; team plans offer higher limits

Practical Evaluation Checklist

• [ ] Install the Chrome or Firefox extension
• [ ] Connect to a Gitlab project via the Marketplace integration
• [ ] Record a bug reproduction session in a web app
• [ ] Attach the session to a Gitlab issue
• [ ] Open the session in the Jam player and inspect console logs
• [ ] Use timeline scrubbing to navigate to a specific network event
• [ ] Verify device info (browser, OS) is captured correctly

Security Notes

Data captured: When recording, Jam captures all content visible in the browser tab, including potentially sensitive data in console logs, network responses, and user input.

Before rolling out team-wide: Establish a recording policy. Ensure your team understands that recordings capture full browser sessions, not just the application UI.

Privacy for end-users: If using Jam to record user-reported bugs in a customer-facing application, consider obtaining explicit consent before capturing sessions that may contain user data.

Storage and access: Recordings are stored on Jam’s servers. Review their data retention and access policies if you handle regulated data.

FAQ

Q: Does Jam work with Github or Jira? A: The current launch targets Gitlab specifically. The product page and HN thread describe a Gitlab plug-in. Github and Jira integrations may be on the roadmap — check the official site for the latest.

Q: Is there a self-hosted version? A: At launch, Jam is a cloud-hosted service with no self-hosted option. There is no mention of a self-deployable version in the launch announcement.

Q: What browsers are supported? A: Chrome and Firefox are explicitly mentioned in the product description.

Q: Does recording slow down my browser? A: The extension adds overhead proportional to the activity in the captured tab. Light recording (static pages) has minimal impact; heavy network activity (streaming, large payloads) may be noticeable.

Q: Can I export recordings? A: The session player is the primary way to consume recordings. Direct export options (MP4, JSON logs) were not documented at launch — check the official docs for the latest.

Source and Accuracy Notes

• Project page: jam.dev
• Official site (from HN): jam.dev/gitlab — the Gitlab plugin page
• HN launch thread: news.ycombinator.com/item?id=40298525
• Source last checked: 2026-07-27 (HN thread content, Jam homepage)