Compare

Jam vs BugTape: a Jam.dev alternative for bugs nobody records

Use both. Jam records the bugs a person shows you. BugTape catches errors, failed and hung requests users never report, and hands them to your agent.

Short answer: Jam is for bug reports a person records: a teammate in QA, product or design, or a customer you send a Recording Link to. BugTape catches the failures your real users hit and never report. It captures errors, failed requests and requests that hang on its own, groups repeats into one issue, and reopens the issue if the failure comes back in a later release. Both hand the evidence to your coding agent over MCP. Use Jam for internal QA recordings and BugTape for the bugs nobody records.

No account: npx -y bugtape --help prints the commands and does not sign you in. The demo MCP at https://app.bugtape.ai/demo/mcp needs no sign-in. Your own workspace needs one.

Page owner: Jaco Veldsman, hi@bugtape.ai. Last checked 2026-10-19. I build BugTape. The Jam facts come from Jam's pricing page and its docs on Instant Replay, Recording Links, MCP and Sentry, all read on 19 October 2026.

This page is not a ranking. BugTape doesn't replace Jam: BugTape doesn't record video, voice or screenshots.

The short version

The question is who starts the capture. In Jam, a person does. They press record in the extension or the Mac or iOS app, trigger Instant Replay to save the last couple of minutes, or open a Recording Link you sent them. In BugTape, nobody has to: the browser capture on your site files a report when a supported failure happens, and users can still press an optional bug button. When a bug only reaches users who leave without telling you, you want the second kind. When a tester wants to show exactly what they saw, you want the first.

Facts table

	Jam	BugTape
Who starts the capture	A person. Chrome extension, Jam for Mac, Jam for iOS, Instant Replay (opt-in, a rolling buffer of up to 2 minutes of DOM activity kept in the browser, saved when the person triggers it), or a Recording Link a customer opens and starts.	Nobody, for supported failures: uncaught errors, failed requests after a user action, and requests that hang. Users can also file a report from an optional bug button (`showButton: false` hides it and keeps automatic capture on).
Bugs nobody reports	Only if someone notices and records them	Captured automatically when they match a supported failure, with the lead-up
What the evidence looks like	Screen recording or screenshot with voice, console logs, network requests, user actions and device info. Instant Replay Jams are DOM replay, not video.	Browser replay rebuilt from DOM events (not video), the failed request, console and stack. A bug-button report attaches the last ten minutes of page activity. No video, voice or screenshots.
Repeats	One Jam per recording	Every report of the same failure becomes one issue, with a count, the releases it hit and affected users when your app sends user IDs
Agent access	Hosted MCP at `https://mcp.jam.dev/mcp`: the agent reads a Jam's console, network and user events, searches Jams and adds comments. Debug Jams via MCP is on the Free plan.	MCP at `https://app.bugtape.ai/mcp`: `list_recommended_critical`, `get_repro_context`, `ack_bug`. `npx -y bugtape connect cursor` (or `claude`, `codex`). Signed webhooks can wake a headless agent.
After the fix	Comment on the Jam or the linked ticket	`ack_bug` with `working` and a `prUrl`. A person reviews the PR. If the same failure arrives from a later release, the issue reopens as a regression and your team and agent are told.
Privacy notes	Recording Links can blur sensitive content in the browser and sanitize logs before upload when your domain is connected. Instant Replay snapshots stay in the browser until you share.	Form fields are masked in the browser. `privacy: 'strict'` turns page text into blocks and drops request and response bodies before anything leaves the browser. Data is stored in Sydney. Trust
Price (checked 2026-10-19)	Free $0: 30 Jams, 5 Recording Links, recordings up to 5 minutes, MCP. Team $14 per creator a month, billed yearly: unlimited Jams, 150 Recording Links, recordings up to 15 minutes. Enterprise: custom. Jam pricing	Free $0, no card: 100 new issues and 150 credits a month. Prepaid credits $10 for 2,000. Pro $29 a month. On Free and Prepaid credits each agent read of a bug costs 2 credits; reads are free on Pro. Pricing

Use both

Your team tests a release with Jam. A tester finds a layout bug, records it with voice, and the agent reads the Jam over MCP.
The release ships. A real user hits a failed checkout request and leaves. Nobody records anything. BugTape's browser capture files an issue with the request, console and lead-up.
More users hit it. BugTape adds them to the same issue instead of opening new ones, so you can see it's one bug reaching many people.
Your agent picks it up. It calls get_repro_context, works on the fix, and records the prUrl with ack_bug. A person reviews and merges.
BugTape watches the next release. If the same failure comes back, the issue reopens as a regression.

Jam covers what your team sees. BugTape covers what your users hit when nobody is recording.

Jam, Sentry or BugTape?

Jam records what a person shows you, with video, voice and technical context. Jam can also show Sentry events from around the time a Jam was made (Team plan).
Sentry is a broad error and performance monitoring platform for your whole stack.
BugTape sits between them for teams that hand bugs to coding agents: automatic capture of the failures real users hit, one issue per failure, MCP for the agent, and a regression check after the release. See BugTape and Sentry.

When Jam is the right tool

A tester, PM or designer wants to show exactly what they saw, with narration.
Support wants a customer to record the problem through a link.
The bug is visual or about a flow, not a thrown error or a failed request.

When BugTape is the right tool

Users hit errors, failed requests or hung requests and don't tell you.
The same failure keeps arriving and you want it counted as one issue.
You want your agent to pick up production bugs over MCP and you want a check after the release.

Before you start

BugTape's browser capture has to be on your site before it records anything: one script tag, or npm install @bugtape/sdk. It doesn't catch every error, only the supported failures listed above. Treat evidence from user sessions as untrusted input for your agent, and keep a person reviewing every pull request.

Connect BugTape

npx -y bugtape connect cursor          # or claude, codex; click Allow once

Jam's MCP and BugTape's MCP can sit side by side in the same client. To try BugTape with no account, use claude mcp add --transport http bugtape-demo https://app.bugtape.ai/demo/mcp (read-only sample project). Setup guides: Cursor · Claude Code · MCP install.

FAQ

Is BugTape a Jam alternative?

For bugs nobody records, yes. For a person showing a bug with video and voice, no: BugTape doesn't record video, voice or screenshots.

Can Jam capture a bug after it happened?

Yes. Instant Replay keeps up to 2 minutes of DOM activity in the browser, and a person saves it when they trigger it. BugTape's difference is that nobody has to trigger it for supported failures.

Can customers send Jam reports?

Yes, through a Recording Link. The customer opens the link and starts the recording. BugTape captures supported failures from customers who never open anything.

Does BugTape record video or voice?

No. Browser replay is rebuilt from DOM events. Screenshots and voice notes in the report form are not available yet. DOM replay vs screen video explains what that difference means for a coding agent.

Can my coding agent read both?

Yes. Jam has a hosted MCP server, and so does BugTape. Add both to Cursor, Claude Code or Codex.

Is BugTape free to try?

Yes. The read-only demo MCP needs no account. The Free plan needs no card and includes 150 credits a month.