Quick answer (checked October 9, 2026): the best Jam.dev alternative is Clipy. It captures the same browser evidence as Jam (console logs, network requests, GraphQL errors, WebSocket activity and labelled clicks) and adds narration, key moments, native Mac and Windows capture, and a share link any coding agent can read, for $9 a month. The other tools here each cover one slice of the job: BetterBugs is a Jam-style extension, OpenReplay Spot is open source, Disbug is aimed at coding agents and Marker.io is a client feedback widget.
- Every price and limit below comes from the vendor's own pricing page or docs on the date above. Plans change, so check before you buy.
- Clipy has everything Jam has and more: on top of browser capture, it records desktop apps on Mac and Windows, iPhone and Android, and agent screenshots and proof.
- Three open-source tools here capture console and network data: OpenReplay Spot, Crikket and, for failed requests only, Builder.io Clips.
- Disclosure: we make Clipy.
Jam.dev alternatives at a glance
| Tool | Console and network | AI agent access | Free plan | Paid from |
|---|---|---|---|---|
| Clipy (our pick) | Yes, plus GraphQL errors and WebSocket activity; redacted headers and bodies with opt-in full network detail | Public agent context on the share link, MCP, skill | 7-day free trial, no card needed | $9 a month, or $72 a year |
| Jam (for reference) | Yes, including redacted request and response bodies | MCP server on every plan, CLI | 30 Jams a month, 5-minute recordings | $14 per creator a month, billed yearly |
| BetterBugs | Yes | MCP on Team and up | 5 seats, 30 sessions, 5-minute recordings | $12 per seat a month, billed yearly |
| Marker.io | On the Team plan | MCP server | No (15-day trial) | $39 a month billed yearly, for 3 users |
| BrowserStack Bug Capture (formerly Bird Eats Bug) | Yes | None found | 15 uploads a month, or free in BrowserStack's Testing Toolkit | $50 a month, for 5 members |
| Userback | On Business and up | MCP on Team and up | 2 seats, feedback visible for 7 days | $29 a month billed yearly, for 5 seats |
| BugHerd | Not listed | MCP (beta) | No (7-day trial) | $42 a month billed yearly, for 5 members |
| Capture.dev | Yes | None found | No (14-day trial) | $29 a month, for 15 members |
| Disbug | Console errors, network logs and session replay | MCP and CLI on every plan | 1 member, 20 most recent sessions | $16 a month billed yearly, for 3 members |
| OpenReplay Spot | Yes | OpenReplay MCP app (session replays) | Free and open source (AGPL-3.0) | Self-host, or OpenReplay Cloud |
| Crikket | Yes | None found | Open source (AGPL-3.0), self-host | Hosted app (price not published) |
What Jam does, so you know what you are replacing
Jam is a Chromium extension (Chrome, Edge, Arc, Brave and Opera; not Firefox or Safari) plus Jam for Mac, Jam for iOS, Recording Links for customers, an SDK and a CLI. A Jam carries a screenshot or video, console logs, network requests with request and response bodies for XHR and fetch, clicks and navigation, and device, browser and OS details. Sensitive headers and JSON fields are redacted on your machine before upload (Jam DevTools docs). Instant Replay attaches the last two minutes of activity, so you can capture a bug after it happened.
Jam has also moved into the AI agent lane. Its MCP server has about 30 tools and is included on the free plan (Jam MCP docs). The jam CLI records a window, the desktop or a Chromium page on macOS and Linux, and installs skills for coding agents (Jam CLI docs). Adding .md to a Jam link returns a public Markdown summary. That summary is deliberately thin: console, network and user actions stay behind the MCP server or CLI.
The free plan covers 30 Jams a month, 5 Recording Links a month, 5-minute recordings and 30 AI summaries a month. Team is $14 per creator a month, billed yearly, with a 14-day trial, 15-minute recordings and 200 AI summaries a month. Viewers are free.
People switch because of the per-creator price, the 5-minute cap on the free plan, a Chromium-only extension, or a report that has to explain something outside a browser tab. Clipy answers all four: $9 a month, no per-recording length cap, a browser recorder that also runs in Firefox and Safari, and native apps for Mac and Windows.
How to choose a Jam alternative
- Who files the report? Engineers and QA want an extension with DevTools data. Clients and end users need a widget on the site, or a link that works without an account.
- What evidence does the fix need? A failing API call needs network capture. A layout problem needs a precise screenshot. A confusing flow needs a narrated recording.
- Who reads it? If a coding agent is the first reader, check how it gets in: a public link, an MCP server that needs a workspace login, or a copied export.
The 10 best Jam.dev alternatives
1. Clipy: everything Jam captures, plus narration, desktop apps and agent-readable links
Clipy is a screen recorder with a Chrome extension, Mac and Windows apps, iPhone and Android apps, and a recorder in the browser. Every share link is a normal video for people and agent context for agents: a summary, the requests you made out loud, key moments with frames and click targets, capture gaps, and a timestamped transcript. A public recording's agent context needs no account or API key to read. Install the Clipy skill once, then paste the link into Claude Code, Cursor or Codex. An MCP server covers private recordings and library search.
Browser evidence comes from the Chrome extension when you turn on bug capture for a tab recording. It captures from the first line of each page load: console output with stack traces and logged objects, uncaught errors and unhandled promise rejections, failed requests with their method, address, status and timing, GraphQL errors returned with HTTP 200, failed scripts and images, WebSocket and event-stream activity, clicks and form fields by their label (never what you typed), and the browser, OS and network speed. Turn on full network detail and it also keeps request and response headers and bodies, redacted in your browser before upload; cookies and authorization headers are never kept. The bug capture docs list every field and limit. The Mac and Windows apps add what no browser extension can reach: native desktop apps, system audio, and clicks with their accessibility labels.
New accounts start with a 7-day free trial, no card needed. Pro is $9 a month or $72 a year (Clipy pricing). People you share with never need to sign in to watch.
Every report gets an AI summary, timestamped transcript, chapters and key moments, and the Generate tab turns the recording into a written bug report, QA steps or a PR description. Send it to Jira, Linear or GitHub as an issue. Viewers can leave timestamped comments, and links can carry a password or an expiry date. Whether the bug is a failing API call, a confusing flow or something that spans a native app and a browser, one Clipy recording carries the evidence and the explanation.
2. BetterBugs: a Jam-style extension
BetterBugs is a Chromium extension (Chrome 109 and later, Edge, Opera, Brave and Arc) plus a web SDK widget. Reports carry screenshots, video, console logs, network requests and environment details, and Rewind attaches the last two minutes, much like Jam's Instant Replay. Its MCP server works with Claude Code and Cursor (BetterBugs MCP docs).
The catch is where the line sits. The free plan gives 5 seats, 1 project, 30 sessions, 10 Recording Links a month, 5-minute recordings and one month of retention, but only Slack and Microsoft Teams integrations. MCP, Jira, Linear and GitHub all need Team, at $12 per seat a month billed yearly.
3. Marker.io: a client feedback widget
Marker.io is a website widget and a browser extension for Chrome and Firefox. Reporters annotate a screenshot or capture the screen, and Marker.io files a structured issue in your tracker with the environment attached. Session replay, console logs and network requests are listed under Developer tools on the Team plan. Its MCP server exposes 33 tools (Marker.io MCP docs).
There is no free plan, only a 15-day trial. Starter is $39 a month billed yearly, flat for 3 users, and Team is $149 a month billed yearly for 15 users. Reporters are free and unlimited (Marker.io pricing).
4. BrowserStack Bug Capture (formerly Bird Eats Bug)
Bird Eats Bug is now part of BrowserStack and sold as Bug Capture. It records the screen with click and key events, console logs, network requests, system details and an instant replay, and it files to Jira, GitHub, Linear and Slack. We found no MCP server or CLI.
The Bird Eats Bug pricing page lists a free plan with 15 uploads a month and paid plans from $50 a month for 5 members, and also says Bug Capture is now free with BrowserStack plans. If your team already pays for BrowserStack, check whether it is already included before you buy anything else.
5. Userback: feedback widget with an MCP server
Userback is a feedback widget for your site or app, plus an extension. Reports carry annotated screenshots, video and browser details; console logs, network requests and per-report session replay are on the Business plan and above. Its MCP server includes a tool that returns a report's console and network logs (Userback MCP docs).
The free plan has 2 seats and 2 projects, but feedback is only visible for 7 days. Team is $29 a month billed yearly, flat for 5 seats (Userback pricing).
6. BugHerd: visual feedback pinned to the page
BugHerd pins feedback to the exact element on a page, with a screenshot, the CSS selector and browser details. Clients can comment as guests without an account, and video feedback is on every plan. Console and network capture is not listed on its feature pages. A BugHerd MCP server is in beta (BugHerd MCP).
There is no free plan. Standard is $42 a month billed yearly for 5 members, and Jira and Linear integrations need Premium (BugHerd pricing). We compared its agent handoff in more detail in BugHerd MCP vs Clipy.
7. Capture.dev: flat price for a whole team
Capture.dev is a toolbar you add to your site with an SDK, a "capture link" for customers, and a Chrome extension for your team. Reports include a screenshot or recording, console logs, network requests and user actions (Capture.dev docs). It integrates with Linear, Jira and Slack, but we found no GitHub integration and no MCP server.
There is one plan, $29 a month for 15 team members, with a 14-day trial and no free tier (Capture.dev pricing).
8. Disbug: bug capture built for coding agents
Disbug now describes itself as browser bug capture for AI coding agents. Its Chrome extension records a screenshot, the DOM selector, console errors, network logs, a user-event trail and browser metadata, and every plan includes session replay with console and network logs. The CLI and MCP server are open source under MIT, and disbug configure sets it up for Claude Code, Codex or Cursor (disbug-cli on GitHub).
The free plan includes MCP and the CLI for 1 member and your 20 most recent sessions. Pro is $16 a month billed yearly, for up to 3 members (Disbug pricing).
9. OpenReplay Spot: open-source session replay
OpenReplay Spot is a free Chrome extension from the open-source OpenReplay project. It records a tab or the desktop with voice narration and attaches console logs, network requests, user interactions and the user agent. Reporters need a free OpenReplay account; viewers do not. It runs on OpenReplay Cloud or on your own OpenReplay install. OpenReplay's MCP app queries session replays and analytics; its docs do not say whether it reads Spot recordings. Public Spot links expire after two days.
OpenReplay's license is AGPL-3.0 by default, with some MIT directories and a separately licensed enterprise folder (OpenReplay on GitHub). Self-hosting means running the whole session-replay platform, which is more than a bug reporter needs.
10. Crikket: a small open-source Jam clone
Crikket describes itself as an open-source alternative to Jam and Marker.io. It captures a screenshot or recording with reproduction steps, console logs and network requests, through an extension or an embeddable SDK. You can self-host it with Docker or use the hosted app. The license is AGPL-3.0 (Crikket on GitHub).
Treat it as early-stage: the repository was created in February 2026 and its latest commit is from March 2026.
Open-source Jam alternatives
Jam's core product is not open source, although its SDK (Apache-2.0) and a few utilities are public. Clipy's Local mode covers the usual reason teams ask for this: it records without uploading, so the video and its agent-readable context stay on your machine. The open-source projects in this space are:
| Project | License | Captures | Self-host | Status |
|---|---|---|---|---|
| OpenReplay Spot | AGPL-3.0 (mixed, see repo) | Video, console, network, interactions | Yes, as part of OpenReplay | Actively released |
| Crikket | AGPL-3.0 | Screenshot or video, console, network, repro steps | Yes, Docker | Early, quiet since March 2026 |
| Builder.io Clips | MIT per its README (no LICENSE file in the repo) | Video, transcript, console logs and failed requests | Yes, needs S3-compatible storage | Active, part of the agent-native repo |
| Disbug CLI and MCP | MIT | CLI only; the extension is not open source | No | Active |
Builder.io Clips is a Loom-style recorder with agent-readable share links. Its extension captures console logs and failed requests, not full network traffic, so it is a partial fit for Jam's job.
Three tools that still show up in older lists are no longer good picks. Requestly's SessionBook recorder is deprecated in its own source code. Highlight.io was acquired by LaunchDarkly and its hosted service has shut down. Screenity is a fine open-source screen recorder (GPL-3.0), but it does not capture console or network data.
Jam alternatives for AI coding agents
Most bug tools now have an MCP server, so "works with AI agents" no longer separates them. What differs is what the agent needs before it can read a report, and how much of the evidence it gets.
| Tool | How the agent reads a report | Needs |
|---|---|---|
| Jam | MCP server (about 30 tools) or the CLI; a public .md summary without the events | Jam account for the events |
| BetterBugs | MCP server | Team plan |
| Marker.io | MCP server (33 tools) | Marker.io account |
| Userback | MCP server | Team plan or higher; console and network logs need Business |
| BugHerd | MCP server (beta) | BugHerd subscription |
| Disbug | MCP server and MIT-licensed CLI | Disbug account, free plan included |
| OpenReplay | MCP app for session replays and analytics (Spot recordings not documented) | OpenReplay account or your own install |
| Builder.io Clips | Public agent-context URL on the share link | Nothing for a public link |
| Clipy | Public agent context on the share link; MCP for private recordings | Nothing for a public link |
The access model matters most when the person debugging is not the person who recorded. A customer, a contractor or a teammate in another workspace can hand you a link. They usually cannot hand you a login to their bug tool. A link your agent can read with an ordinary HTTP request survives that handoff, and it survives you switching agents.
The other difference is the format. A transcript alone loses instructions like "move this button above that one", because the words only make sense against the screen. Frames tied to the moment you spoke, with the click target marked, keep that meaning. For how the formats compare in practice, see screen recorders for AI coding agents, compared.
With Clipy, the handoff to an agent is one message:
Read this Clipy recording and fix the bug I described: [recording link]. Install the Clipy skill if needed. Tell me which evidence was missing before you change code.
Jam vs Clipy
We ran Jam's extension against a scripted bug page on October 6, 2026. Clipy's rows below describe the current release, from its documentation; the narration, agent-read, desktop and plan rows for both come from documentation too.
| Jam | Clipy | |
|---|---|---|
| Console logs | From the first line of page load, with logged objects | From the first line of each page load while recording, with stack traces and logged objects |
| Network | Every request, with redacted headers and bodies | Failed requests plus GraphQL errors returned with HTTP 200 and WebSocket activity, with redacted headers and bodies when full network detail is on |
| Unhandled promise rejections | Not captured in our test | Captured |
| Redaction | By field name in headers and bodies; console text is not redacted | By field name and by value (tokens, emails, card numbers), including console text |
| Narration and key moments | Video and AI summary | Transcript, key-moment frames with click targets, extracted requests |
| Public agent read | .md summary; events need MCP or CLI | Agent context on the share link, with up to 200 diagnostic events |
| Desktop and mobile capture | Jam for Mac, Jam for iOS, CLI on macOS and Linux | Native Mac and Windows apps, iPhone and Android apps |
| Recording length | 5 minutes on free, 15 minutes on Team | No per-recording cap |
| Paid | $14 per creator a month, billed yearly | $9 a month or $72 a year |
Clipy covers Jam's browser evidence and goes further: the recording carries your explanation, any agent or outside teammate can read it from the link, the bug can cross from a browser into a native app, and there is no 5-minute cap. It also costs less per recorder. For the two-tool comparison on its own, see Jam vs Clipy.
Frequently asked questions
Is there a free Jam.dev alternative?
Yes. OpenReplay Spot and Crikket are free and open source. BetterBugs has a free plan with 5 seats and 30 sessions, BrowserStack Bug Capture has a free tier, Disbug has a free plan with MCP included, and Userback has a free plan that keeps feedback for 7 days. Marker.io, BugHerd and Capture.dev offer trials only. Clipy starts with a 7-day trial with no card.
What is the best open-source alternative to Jam?
OpenReplay Spot. It records video with console and network data, is actively maintained and can be self-hosted. Crikket is a closer copy of Jam's workflow but is much smaller and less active.
Which Jam alternatives work with Claude Code or Cursor?
BetterBugs, Marker.io, Userback, BugHerd, Disbug, OpenReplay and Clipy all have MCP servers, and Builder.io Clips serves agent context on its share links. Jam does too. Check which plan includes it and whether the agent needs an account to read a report.
Does Jam work in Firefox or Safari?
Jam's extension is Chromium only, but its Recording Links work in Firefox and Safari. Marker.io's extension supports Firefox, and Clipy's in-browser recorder works in Firefox and Safari too.
How did you check these tools?
Every price, limit and feature comes from the vendor's own pricing page, documentation or repository on October 9, 2026, linked inline. The Jam vs Clipy table also uses a hands-on test from October 6, 2026. The other tools were not run through that test.
Next: screen recorders that capture browser console errors, how to write a bug report, or try the Clipy bug report recorder.