{"id":295818,"date":"2026-04-07T13:29:30","date_gmt":"2026-04-07T13:29:30","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/snagrelay-intelligent-bug-capture\/"},"modified":"2026-10-10T14:43:30","modified_gmt":"2026-10-10T14:43:30","slug":"snagrelay","status":"publish","type":"plugin","link":"https:\/\/kn.wordpress.org\/plugins\/snagrelay\/","author":23474040,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.2.0","stable_tag":"1.2.0","tested":"7.1.3","requires":"6.3","requires_php":"7.4","requires_plugins":null,"header_name":"SnagRelay","header_author":"SnagRelay","header_description":"Integrate SnagRelay bug reporting widget into your WordPress site.","assets_banners_color":"8a888a","last_updated":"2026-10-10 14:43:30","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/snagrelay.com\/wordpress\/","header_author_uri":"https:\/\/snagrelay.com","rating":0,"author_block_rating":0,"active_installs":0,"downloads":668,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.0.2":{"tag":"1.0.2","author":"snagrelay","date":"2026-04-07 13:40:56","revision":3500806},"1.1.0":{"tag":"1.1.0","author":"snagrelay","date":"2026-05-20 20:34:48","revision":3540059},"1.2.0":{"tag":"1.2.0","author":"snagrelay","date":"2026-10-10 14:43:30","revision":3738182}},"upgrade_notice":[],"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3738182,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3738182,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3738182,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3738182,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.2","1.1.0","1.2.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3738182,"resolution":"1","location":"assets","locale":"","width":1280,"height":900},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3738182,"resolution":"2","location":"assets","locale":"","width":1280,"height":900}},"screenshots":{"1":"Settings page \u2014 connect with your API key and choose who sees the button, and where.","2":"Developer context \u2014 per-group privacy switches and the Site URL and secret for your SnagRelay project."}},"plugin_section":[],"plugin_tags":[189089,108,7615,8201,55692],"plugin_category":[42],"plugin_contributors":[259648],"plugin_business_model":[],"class_list":["post-295818","plugin","type-plugin","status-publish","hentry","plugin_tags-bug-reporting","plugin_tags-feedback","plugin_tags-qa","plugin_tags-screenshots","plugin_tags-session-replay","plugin_category-contact-forms","plugin_contributors-snagrelay","plugin_committers-snagrelay"],"banners":{"banner":"https:\/\/ps.w.org\/snagrelay\/assets\/banner-772x250.png?rev=3738182","banner_2x":"https:\/\/ps.w.org\/snagrelay\/assets\/banner-1544x500.png?rev=3738182","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/snagrelay\/assets\/icon-128x128.png?rev=3738182","icon_2x":"https:\/\/ps.w.org\/snagrelay\/assets\/icon-256x256.png?rev=3738182","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/snagrelay\/assets\/screenshot-1.png?rev=3738182","caption":"Settings page \u2014 connect with your API key and choose who sees the button, and where."},{"src":"https:\/\/ps.w.org\/snagrelay\/assets\/screenshot-2.png?rev=3738182","caption":"Developer context \u2014 per-group privacy switches and the Site URL and secret for your SnagRelay project."}],"raw_content":"<!--section=description-->\n<p><a href=\"https:\/\/snagrelay.com\">SnagRelay<\/a> is an AI-powered bug reporting tool that captures everything developers need to fix issues fast \u2014 annotated screenshots, session replay, video recording, console logs, network activity, and AI-generated reproduction steps. This plugin installs the SnagRelay widget on your WordPress site in seconds, with no code required.<\/p>\n\n<p>Reports land directly in your existing issue tracker. No separate board to check, no context switching.<\/p>\n\n<h4>WordPress plugin features<\/h4>\n\n<ul>\n<li>No-code installation \u2014 just paste your API key<\/li>\n<li>Independently enable the widget on the frontend and\/or the WP admin area<\/li>\n<li>Control visibility by user role (everyone, logged-in users, or specific roles)<\/li>\n<li>Filter by post type (all, pages, posts, or specific types)<\/li>\n<li>Filter by post status (all, published, or drafts\/pending)<\/li>\n<li>Lightweight \u2014 loads asynchronously, zero performance impact<\/li>\n<li>14-day free trial, no credit card required<\/li>\n<\/ul>\n\n<h4>Developer context (new in 1.2)<\/h4>\n\n<p>When a visitor or client submits a report, SnagRelay asks your site \u2014 server to server, signed with a secret only you and SnagRelay know \u2014 for the technical context a developer needs:<\/p>\n\n<ul>\n<li>WordPress, PHP and MySQL versions, multisite flag<\/li>\n<li>Active theme (and parent) with versions<\/li>\n<li>Active plugins with versions, plus recently updated plugins and themes<\/li>\n<li>PHP warnings, notices and fatals raised by the page, AJAX (admin-ajax.php, WooCommerce wc-ajax) or REST request the visitor hit (paths relative to wp-content)<\/li>\n<li>WooCommerce, when active: version, cart item count, coupon codes, shipping and payment method IDs, currency. No customer data.<\/li>\n<li>Page builder version (Elementor, Bricks, Divi)<\/li>\n<\/ul>\n\n<p>Each group can be switched off in Settings \u2192 SnagRelay. Nothing from this list is ever printed into your public pages: pages and AJAX\/REST responses only carry an opaque, signed request ID.<\/p>\n\n<p>Developer context is optional and needs one extra step: paste the Site URL and Site secret shown in Settings \u2192 SnagRelay into your SnagRelay project (Install \u2192 WordPress). Your site must be reachable from the internet; local and private-network sites are skipped. A page served from a page cache did not run PHP, so it has no errors to report; AJAX and REST requests are always matched.<\/p>\n\n<h4>What SnagRelay captures<\/h4>\n\n<ul>\n<li>HD annotated screenshots<\/li>\n<li>Session replay recording<\/li>\n<li>60-second screen video with auto-generated reproduction steps<\/li>\n<li>Full console logs and error stack traces<\/li>\n<li>Network requests and payloads<\/li>\n<li>Browser metadata and environment details<\/li>\n<\/ul>\n\n<h4>AI intelligence<\/h4>\n\n<ul>\n<li>Automatic duplicate detection<\/li>\n<li>Priority suggestions (P1\u2013P5)<\/li>\n<li>Smart assignee matching<\/li>\n<li>Learns from your team's decisions over time<\/li>\n<\/ul>\n\n<h4>Integrations<\/h4>\n\n<p>Sends reports directly to the tools your team already uses:<\/p>\n\n<ul>\n<li>Jira<\/li>\n<li>Linear<\/li>\n<li>Trello<\/li>\n<li>GitHub<\/li>\n<li>Custom webhooks<\/li>\n<\/ul>\n\n<h3>External Services<\/h3>\n\n<p>This plugin connects to the SnagRelay service (https:\/\/app.snagrelay.com) to load the bug-capture widget and to transmit bug reports to your configured issue tracker.<\/p>\n\n<p><strong>What is sent and when:<\/strong><\/p>\n\n<ul>\n<li>When a page is loaded with the widget enabled, the plugin loads a script from <code>https:\/\/app.snagrelay.com\/widget\/load\/{api_key}<\/code>. Your API key is included in this request so the service can identify your project.<\/li>\n<li>When a user submits a bug report via the widget, SnagRelay collects and transmits the data selected by the user, which may include: annotated screenshots, session replay recording, screen video, console logs, network request details, browser metadata, and environment information.<\/li>\n<li>No data is sent to the external service unless the widget is enabled and a valid API key is configured.<\/li>\n<li><strong>Developer context (1.2+):<\/strong> after a report is submitted, SnagRelay calls <code>POST \/wp-json\/snagrelay\/v1\/snapshot<\/code> on your site, signed with HMAC-SHA256 and the site secret shown in Settings \u2192 SnagRelay. Your site replies with the data listed under \"Developer context\" above. Requests with a missing, wrong or stale (older than 5 minutes) signature are rejected. PHP errors for a request are kept in a transient for 15 minutes. You can turn each data group off, or regenerate the secret, at any time.<\/li>\n<li><strong>Request IDs (1.2+):<\/strong> page loads include <code>&lt;meta name=\"snagrelay-req\"&gt;<\/code>, and admin-ajax.php, wc-ajax and REST responses include an <code>X-SnagRelay-Req<\/code> header. Both contain only a random ID and a signature, never any site data. The widget sends the IDs with a report so SnagRelay can ask your site for the errors of those requests.<\/li>\n<\/ul>\n\n<p><strong>Service provider:<\/strong> SnagRelay (https:\/\/snagrelay.com)<\/p>\n\n<ul>\n<li><a href=\"https:\/\/snagrelay.com\/terms\/\">Terms of Service<\/a><\/li>\n<li><a href=\"https:\/\/snagrelay.com\/privacy\/\">Privacy Policy<\/a><\/li>\n<\/ul>\n\n<!--section=installation-->\n<ol>\n<li>Upload the plugin files to <code>\/wp-content\/plugins\/snagrelay<\/code>, or install through the WordPress plugins screen directly.<\/li>\n<li>Activate the plugin through the <strong>Plugins<\/strong> screen.<\/li>\n<li>Go to <strong>Settings \u2192 SnagRelay<\/strong> to configure the plugin.<\/li>\n<li>Paste your API key from your <a href=\"https:\/\/app.snagrelay.com\">SnagRelay dashboard<\/a> (project \u2192 Install \u2192 WordPress).<\/li>\n<li>Enable the widget on the frontend and\/or admin as needed.<\/li>\n<li>Optionally configure user role, post type, and post status filters.<\/li>\n<li>Optional: paste the Site URL and Site secret into your SnagRelay project to enable developer context.<\/li>\n<\/ol>\n\n<!--section=faq-->\n<dl>\n<dt id=\"where%20do%20i%20get%20an%20api%20key%3F\"><h3>Where do I get an API key?<\/h3><\/dt>\n<dd><p>Sign up at <a href=\"https:\/\/snagrelay.com\">snagrelay.com<\/a> \u2014 anyone can start a 14-day free trial with no credit card required. Your API key is available in your project dashboard under Install \u2192 WordPress.<\/p><\/dd>\n<dt id=\"can%20i%20show%20the%20widget%20only%20to%20logged-in%20users%20or%20specific%20roles%3F\"><h3>Can I show the widget only to logged-in users or specific roles?<\/h3><\/dt>\n<dd><p>Yes. The Users setting lets you choose between everyone, authenticated users only, or specific WordPress roles such as Editor or Administrator.<\/p><\/dd>\n<dt id=\"can%20i%20limit%20the%20widget%20to%20specific%20post%20types%20or%20page%20statuses%3F\"><h3>Can I limit the widget to specific post types or page statuses?<\/h3><\/dt>\n<dd><p>Yes. You can restrict the widget to pages, posts, or specific post types, and further filter by published or draft\/pending status.<\/p><\/dd>\n<dt id=\"can%20i%20enable%20it%20only%20in%20the%20wordpress%20admin%20area%3F\"><h3>Can I enable it only in the WordPress admin area?<\/h3><\/dt>\n<dd><p>Yes. The \"Show in admin\" toggle is independent of the frontend toggle, so you can run the widget on admin screens only, on the public site only, or on both.<\/p><\/dd>\n<dt id=\"will%20it%20slow%20down%20my%20site%3F\"><h3>Will it slow down my site?<\/h3><\/dt>\n<dd><p>No. The widget script is loaded asynchronously and does not block page rendering or affect your Core Web Vitals.<\/p><\/dd>\n<dt id=\"does%20snagrelay%20work%20on%20local%20and%20staging%20environments%3F\"><h3>Does SnagRelay work on local and staging environments?<\/h3><\/dt>\n<dd><p>Yes, the widget works on any environment. Developer context (plugins, theme, PHP errors) is fetched by SnagRelay's servers, so it needs a site reachable from the internet: use a public staging URL or a tunnel for local sites.<\/p><\/dd>\n<dt id=\"why%20are%20there%20no%20php%20errors%20on%20a%20cached%20page%3F\"><h3>Why are there no PHP errors on a cached page?<\/h3><\/dt>\n<dd><p>A page served from a page cache (WP Rocket, Cloudflare APO, host-level caches) did not run PHP, so there is nothing to record. Errors from AJAX and REST requests, and from uncached page loads, are matched to the report.<\/p><\/dd>\n<dt id=\"what%20does%20the%20site%20secret%20do%3F\"><h3>What does the site secret do?<\/h3><\/dt>\n<dd><p>It lets your site verify that a context request really comes from SnagRelay (HMAC-SHA256, with a five minute replay window) and signs the opaque request IDs. Regenerate it any time in Settings \u2192 SnagRelay, then paste the new one into SnagRelay. Uninstalling the plugin removes it.<\/p><\/dd>\n<dt id=\"how%20much%20does%20snagrelay%20cost%3F\"><h3>How much does SnagRelay cost?<\/h3><\/dt>\n<dd><p>All plans include a 14-day free trial.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.2.0<\/h4>\n\n<ul>\n<li>New: developer context snapshot (plugins, theme, versions, recent updates, PHP errors for the request, WooCommerce cart context), fetched server to server with an HMAC-signed request.<\/li>\n<li>New: PHP errors are matched to AJAX (admin-ajax.php, WooCommerce wc-ajax) and REST requests as well as page loads, via an opaque X-SnagRelay-Req response header.<\/li>\n<li>New: per-group privacy toggles and a regenerable site secret in Settings \u2192 SnagRelay.<\/li>\n<li>New: redesigned settings page that matches the SnagRelay app, with a clearer connect flow, copy buttons and a connection status. Fonts are bundled; nothing loads from a CDN.<\/li>\n<li>New: refreshed logo and plugin directory artwork.<\/li>\n<li>Security: repeated failed signature checks on the context endpoint are answered with HTTP 429. A valid signature is never blocked.<\/li>\n<li>Fix: uninstall now removes the site secret, recent-updates log and error transients on every site of a multisite network.<\/li>\n<li>Changed: \"API token\" is now \"API key\" in the interface, matching the SnagRelay dashboard.<\/li>\n<li>Requires WordPress 6.3+ and PHP 7.4+.<\/li>\n<\/ul>\n\n<h4>1.1.0<\/h4>\n\n<ul>\n<li>Support Wordpress 7.0.0<\/li>\n<\/ul>\n\n<h4>1.0.2<\/h4>\n\n<ul>\n<li>Added External Services disclosure to readme to document use of app.snagrelay.com, per WordPress plugin guidelines.<\/li>\n<\/ul>\n\n<h4>1.0.1<\/h4>\n\n<ul>\n<li>Improved compliance with WordPress plugin guidelines.<\/li>\n<\/ul>\n\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>Initial release.<\/li>\n<\/ul>","raw_excerpt":"Bug reports that tell you which plugin broke it: screenshots, logs and a server-side snapshot of plugins, theme and PHP errors.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/kn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/295818","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/kn.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/kn.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=295818"}],"author":[{"embeddable":true,"href":"https:\/\/kn.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/snagrelay"}],"wp:attachment":[{"href":"https:\/\/kn.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=295818"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/kn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=295818"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/kn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=295818"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/kn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=295818"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/kn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=295818"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/kn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=295818"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}