pincushionJam shows you the bug. Pincushion collects the client's ask.
Jam is a fast way to record a bug with its console logs and network requests attached. Pincushion starts with a different input: a client pins the element they want changed on the live page, for free, and your agent gets a work packet with a commit, PR and verify trail behind it.
What Jam does well
Credit where it's due. Jam's own site describes a browser extension that records your screen or captures screenshots, keeps logs, network requests, user events and device details with each recording, and uses AI to suggest a title, summary and repro steps. Recording Links let a customer show you an issue as it happens, and a Jam can be sent to Linear, Jira or Slack, or handed to AI tooling so a coding agent can investigate. Jam documents an MCP option that gives agents the recording, logs, network requests and user events from a Jam, and its site says agents can record Jams through a CLI.
For a bug that is hard to reproduce, a recording with the network and console trail attached is exactly the right evidence.
Where the model differs
Jam is built around a report: someone reproduces a problem, and the recording explains it. Pincushion is built around a request on a specific element: "make this headline shorter", "this button is the wrong blue on mobile". A client rarely wants to record their screen; they want to point.
- Free client pins from a link. Share a report link and reviewers pin the real page with just a name, no account or install on projects open to feedback. Collaborators never pay.
- The agent work packet. Each pin carries the selector, DOM snippet, screenshot, viewport, thread and project context, readable over MCP by Cursor, Claude Code or Codex.
- The commit, PR and verify trail.
fix_and_resolverecords the commit SHA, branch and PR URL on the pin, and the client sees what shipped on the pin they left.
How they differ
| Pincushion | Jam | |
|---|---|---|
| Typical input | Free pin on the exact element, left from a link | Screen recording or screenshot with logs |
| Who leaves feedback | Clients, PMs and teammates from a link — free and unlimited | People who capture a Jam (extension, apps or a Recording Link) |
| Context handed to the agent | Selector, DOM snippet, screenshot, viewport, thread, project context | Recording, logs, network requests, user events, device details |
| Agent reads it via MCP | Yes — and resolves it with fix_and_resolve | Yes — Jam documents an MCP option for reading a Jam |
| Commit SHA, branch and PR recorded on the feedback | Yes | Not described |
| Post-deploy check of the fix | Yes (Pro) | Not described |
| Best for | Change requests from people outside your codebase | Reproducing and debugging a bug |
Jam gives your agent the replay of a bug. Pincushion gives it the client's request, pinned to the element, and keeps the receipt of what shipped.
When Jam is the better fit
If the problem is "it broke and I can't reproduce it", Jam's recording with logs and network requests is more useful than a pin. Use it. Pincushion is the better fit when the feedback is a change request on how the deployed page looks, reads or behaves, and it comes from someone who will never open dev tools.
Use both, or start free
Many teams will: Jam when something is broken, Pincushion for the review round that follows. The free plan covers one project with unlimited manual pins and 25 AI actions a month, and reviewers never need a paid seat. Every new account starts with a 14-day full-Pro trial — no card required. See the loop in Cursor, Claude Code or Codex, or compare with Marker.io and BugHerd. All comparisons are on the alternatives overview.
Sources
Statements about Jam come from its own public pages, checked on October 25, 2026. Products change; confirm current details with the vendor.