List the bug reports captured by the Feedbug widget, newest first.

Returns: a JSON array carrying, per bug, its UUID, tracker identifier (e.g. PRE-13), title, status, page URL, framework component path, session replay URL and creation date. Use when: you are looking for a bug to work on, checking what is still open, or reviewing every report filed on one page. Do not use when: you already hold a bug id — feedbug_get_bug returns that one report with its screenshot and DOM context. Behavior: read-only and idempotent. The server authenticates with the FEEDBUG_PROJECT_KEY environment variable and can only ever see that single project. There is no pagination: the API truncates to limit, so narrow the set with status or page_url instead of paging. No match returns an empty array, not an error.

Read one bug report in full.

Returns: a JSON object with the title, the Feedbug and tracker statuses, the tracker issue URL, the page URL, the screenshot URL, the session replay URL, the viewport, the user agent, the click coordinates as percentages, and the captured DOM context. Use when: you picked a bug out of feedbug_list_bugs and are about to reproduce or fix it. Do not use when: you only need the DOM tree (feedbug_get_html_context), only the browser environment (feedbug_get_diagnostics) or only the replay link (feedbug_get_replay). Behavior: read-only and idempotent, scoped by FEEDBUG_PROJECT_KEY to a single project. An unknown id, or one belonging to another project, returns a "Bug not found" error.

Read the HTML and DOM context captured at the instant the tester clicked on the bug.

Returns: a JSON object with the CSS selector path, the framework component path (Vue, React, Angular, Svelte), the clicked element itself (tag, id, classes, text, attributes), its ancestors and its siblings. Use when: you need to map a report onto a source file — this is the shortest path from a bug to the component that renders it. Do not use when: the bug is about a behaviour rather than one element; feedbug_get_replay shows what the tester actually did. Behavior: read-only and idempotent, scoped by FEEDBUG_PROJECT_KEY to a single project. A report captured without DOM context errors with "No HTML context captured for this bug" rather than returning an empty tree. Component paths survive a Vue build but are often absent from minified React, in which case fall back to the selector path.

Read the browser environment a bug was reported from.

Returns: a JSON object with the page URL, the viewport size, the user agent and the name of the reporter. Use when: you need to reproduce a bug under the same browser, screen size or account, or to judge whether a report is device-specific. Do not use when: you also want the screenshot, the DOM or the tracker link — this is a strict subset of feedbug_get_bug, so one call there replaces this one. Behavior: read-only and idempotent, scoped by FEEDBUG_PROJECT_KEY to a single project. Fields the widget could not capture come back null; an unknown id returns a "Bug not found" error.

Read the session replay URL of a bug, an rrweb recording of the last 30 seconds of activity before the report was sent.

Returns: a one-line message holding the URL to open in a browser. The recording itself is never inlined, so it costs no context. Use when: the written report is not enough to reproduce the bug and you want to hand the user a link to watch it happen. Do not use when: you already called feedbug_get_bug, which returns the same URL alongside the rest of the record. Behavior: read-only and idempotent, scoped by FEEDBUG_PROJECT_KEY to a single project. A bug with no recording returns "No session replay available" as an ordinary result rather than an error, so the call is always safe to attempt.

Post a comment on the tracker issue linked to a bug.

Returns: a confirmation message once the tracker accepted the comment. Use when: you want to document a fix, ask the reporter for a reproduction, or leave an update the whole team can read on the issue. Do not use when: the bug is tracked in GitHub — only Linear-routed bugs accept comments today and the call errors otherwise. Never use it to talk to the user running you; answer them directly instead. Behavior: writes to Linear and is NOT idempotent — every call adds another comment, and this server can neither edit nor delete one. The comment is public to everyone with access to the issue and is authored by the Linear account that installed Feedbug, so send a single finished comment rather than successive drafts.

Mark a bug as resolved in Feedbug, once its fix is verified.

Returns: a confirmation message. Use when: you have shipped and checked the fix for that exact report. Do not use when: the fix is only proposed or not yet verified — this server exposes no way to reopen a bug. Behavior: writes to Feedbug and is idempotent, since resolving an already resolved bug leaves it resolved. It flips the status of the report and hides its marker from the widget, but does NOT close the linked Linear or GitHub issue: the tracker stays the source of truth, and moving that issue back to an open state syncs the report open again through the webhook.