Reports, the price, the team, and the connections.

The screenshot, the annotation, the element’s HTML and CSS when one was picked, about 30 seconds of session replay, the last 200 console lines, the last 100 network requests, the page URL, and the environment it was captured in.

Yes. They can click the node that broke, or skip that step. The bug stores a selector, the HTML, the styles that differ from a plain element of the same tag, and the CSS rules that matched.

Yes. Install the Chrome extension, paste the workspace API key, and file from the page you are viewing. That capture is the visible tab and your markup. It does not include a session replay, the console, or the network. The widget is still one script tag on a site you can edit, and that is how a visitor files.

$5 a month for the workspace. Admins, members, and guests are included. Screenshot, annotation, element capture, replay, diagnostics, guest reporting, Asana, MCP, and the Chrome extension come with that price.

The workspace. That is the widget, the dashboard, the Chrome extension, and the people you invite. Screenshot, markup, element HTML and CSS, replay, console and network, guest forms, the queue, Asana, and MCP are on this price.

No. The price stays $5 a month as you invite admins, members, and guests.

Monthly, at $5 plus applicable taxes. The signed-out demo lets you try the widget, and it does not save a report.

New widget reports pause until the invoice is paid. The dashboard stays available so an admin can update the card.

Yes. A visitor can submit without an account. You choose which fields guests and signed-in teammates see, and which ones are required.

Filter by status and priority, assign a teammate, and keep public notes separate from internal ones. Mention someone with @.

Connect an Asana project and each new bug becomes a task there, with the title, the description, and the screenshot. You can map priority, type, status, the reporter, the page URL, and the BugTrap link onto fields that project already has. BugTrap stays the place the team filters, assigns, and closes it.

MCP (Model Context Protocol) is an open way for an agent to call tools outside the chat. The BugTrap connector gives that agent two tools for one workspace: list bugs, and read one report. Describe the bug you want. The agent looks it up.

Any client that can call a remote MCP server and send a bearer token. Configs on the MCP page cover Cursor, Claude Code, Codex, VS Code with GitHub Copilot, Gemini CLI, and Devin Desktop. ChatGPT and the Claude app add custom connectors with OAuth, which this server does not use. For those models, use Codex or Claude Code.

No. Create a token, paste the config, and ask a question. Reading the queue is a conversation. When the agent is inside an editor, it can also use the report to change the code.

The list includes the id, the BT- code, the title, the status, the priority, the type, the assignee, and the page. The report adds the description, the page URL, the environment, a short console excerpt, failed network requests, the HTML and CSS of a picked element when one was captured, the ten most recent comments, and a link to the bug. Public and internal comments are both included.

The report names the screenshot, the annotation, and the replay when they are attached, and it includes the dashboard link. Those files stay on the bug page.

The tools only read bugs. Closing, assigning, and commenting stay in the dashboard.

Yes. An admin or a member of a workspace with an active subscription can create a token. Each person can keep ten. An admin can see every token in the workspace and revoke one. A member sees the tokens they created. Bugs the agent reads are the bugs already in that shared workspace.

The report text is sent to the model that client uses. Console lines are shortened, and BugTrap tokens and bearer tokens in those lines are replaced. When a reporter picked an element, its HTML and CSS are included and shortened the same way. Fields whose names look like passwords, secrets, or API keys are redacted. The screenshot, the annotation, and the replay are not sent.

The dashboard is where the team filters, assigns, comments, and closes. MCP lets an outside agent read that same queue as part of the chat it is already in, including a coding agent that then edits the repo. The widget still files the report.

Open Settings → MCP and create a token. Copy the config for your client from the MCP page, replace YOUR_TOKEN, and ask the agent to list open bugs. The widget API key does not work here. The secret is shown once.