EveryBug FAQ
Short answers. Longer process lives in guides; longer opinion in the blog.
Live bug bash
Testers join `/bash/{slug}` with a display name. They do not need an account. Organizers see a roster and a findings board. When the end time passes, the bash is treated as closed. PIN is optional.
Organizers export from the board; guests cannot push to Jira, Linear, or GitHub. Process: how to run a live bug bash.
Accounts and price
Sign up with Google or email. Password minimum 8 characters. EveryBug is free. We do not ask for a card.
More reading
Process: guides. Opinion and roundups: blog. Feature list: features. Honest diffs: compare.
FAQ
What is EveryBug?
A place to review recorded demos and QA sessions. You upload the video, mark where things break, draw on the frame if words aren’t enough, and share a link with the team. When you’re done, export a PDF or a Jira CSV.
How do I highlight bugs in a video?
Upload the file, scrub to the bad moment, and set a start/end time. Circle the UI glitch on the frame, write what you expected vs what happened, and move on. No need to re-watch the whole thing later — each bug is a bookmark.
Is EveryBug good for bug bash sessions?
That’s the sweet spot. Everyone uploads their recordings into a shared project, files bugs during or after the bash, and you triage together. Status goes from “did anyone else see this?” to Verified without a spreadsheet.
Can I export bugs to Jira?
Yes — push to Jira Cloud with clips and annotated stills, or download CSV and PDF. Linear and GitHub Issues work the same way from Integrations.
Can QA agents use EveryBug via MCP?
Yes. Create an API token under Integrations → MCP and connect Cursor (or another MCP client) to https://everybug.com/mcp. Agents can start a live bash, import a video, mark timeline bugs, and return a share link.
Can I run a live bug bash without testers signing up?
Yes. Share /bash/{slug}. Testers join with a display name (optional PIN). Findings land on a board. Organizers export to the tracker.
Is EveryBug free?
Free. Sign up with Google or email and start uploading. We don’t ask for a card.
How is EveryBug different from Loom or Jam?
Loom is great for sending someone a quick screen recording. Jam catches bugs while you’re clicking around a live site. EveryBug is for when you already have a video — a bug bash capture, a UAT walkthrough, a client demo — and you need to pull every issue out of it with timestamps. It also runs a live bash with a shared board.
Can guests join a live bug bash without signing up?
Yes. They open the bash link, enter a display name (and PIN if the organizer set one), and get a guest session for that bash only.
Does EveryBug replace Jira?
No. It is the review layer. Push or CSV into Jira (or Linear / GitHub) when triage is done.
Can a QA agent create a bash and mark bugs without opening the editor?
Yes. Create an API token under Integrations → MCP, point Cursor (or another MCP client) at https://everybug.com/mcp, then use create_bug_bash, create_session, and add_bug. Details: /guides/everybug-mcp-for-qa-agents.
Do you index shared session links?
No. /session/* is noindex. Marketing pages are indexed. See robots.txt.