# Snags > Snags is a Chrome extension for leaving comments on any website. Each comment carries a screenshot, a replay of the moments before it, the steps taken, and the console errors and failed requests behind it. A finished audit is one link anyone can open without an account. Comments become Linear, GitHub or Jira issues, and coding agents read audits and mark comments fixed over MCP. Each page below is also available as raw markdown by appending /md to its URL. ## Getting started - [Install Snags](https://snags.com/docs/get-started): Add the extension to Chrome, start an audit on a website, leave your first comment and share the link. ## Product - [What gets captured](https://snags.com/docs/what-gets-captured): What a comment carries, how masking works, the replay, the automatic checks and how long it's all kept. - [Source context](https://snags.com/docs/source-attribution): How Snags finds the component behind an element, reads the site's release and links to the file in your repository. - [Share an audit](https://snags.com/docs/sharing): The audit link, passwords and branding, Copy for AI, Markdown and CSV exports, Playwright tests and the offline file. - [Status, discussion & fixes](https://snags.com/docs/triage): Mark comments open, fixed or won't fix, reply and assign, and check that fixes really landed on the site. ## Integrations - [Trackers & sync](https://snags.com/docs/integrations): How comments become issues in Linear, GitHub and Jira, what the issue contains, and how status comes back to Snags. - [GitHub](https://snags.com/docs/github): Install the Snags GitHub App on the repositories you pick, and send comments there as issues. - [Linear](https://snags.com/docs/linear): Connect Linear, choose a team, and send comments there as issues with the screenshot, steps and errors. - [Jira](https://snags.com/docs/jira): Connect Jira, choose a project, and send comments there as issues that sync their status back. ## AI agents - [MCP for coding agents](https://snags.com/docs/mcp): Give Claude Code, Cursor, Codex or any MCP client an audit link: it reads every comment, fixes the code and marks each one fixed. ## Account - [Workspaces & roles](https://snags.com/docs/teams): Team workspaces: owners, admins, members and clients, invitations, and who sees which sites. - [Billing & plans](https://snags.com/docs/billing): Free, Pro and Team, what each includes, the storage and size limits, and what happens when you downgrade. - [Privacy & compliance guide](https://snags.com/docs/compliance-guide): Use Snags responsibly on websites with real people's data: where to audit, what to mask, who sees an audit and how to delete it. - [Security & privacy](https://snags.com/docs/security): What Snags can reach in your browser, who can open an audit, sign-in and tokens, and how secrets are kept out. ## Pricing Free (5 shared audits, links last 7 days), Pro ($5 a month or $36 a year) and Team ($19 a month or $180 a year, 10 seats and unlimited free clients). See https://snags.com/pricing. ## Guides All guides: https://snags.com/guides ### HAR files - [HAR analyzer](https://snags.com/tools/har-checker): Free tool. Find the failed requests and the secrets in a HAR file, without uploading it. - [What is a HAR file? How to make, read and share one safely](https://snags.com/guides/what-is-a-har-file): A HAR file logs every request your browser made. How to export one in Chrome, Firefox, Edge or Safari, read it, and strip the secrets before you share it. ### Console and dev tools - [How to open the console in Chrome, Edge, Firefox and Safari](https://snags.com/guides/open-the-console): The keys that open the console and developer tools in Chrome, Edge, Firefox and Safari on Windows and Mac, plus the setting Safari needs switched on first. - [What is a source map? How browsers find them and when to ship them](https://snags.com/guides/what-is-a-source-map): A source map links minified JavaScript back to your original code. What's inside one, the three ways a browser finds it, and whether to publish maps in production. - [What is a stack trace? How to read one in JavaScript](https://snags.com/guides/what-is-a-stack-trace): A stack trace lists the function calls that were running when an error happened. How to read a JavaScript stack trace, and why production ones need a source map. ### Console errors - [Cannot read properties of undefined: causes and fixes](https://snags.com/guides/cannot-read-properties-of-undefined): What "Cannot read properties of undefined" means, the four things that cause it in production, and how to tell which one from a bug report before you fix it. - [TypeError: Failed to fetch: what it means and how to find the cause](https://snags.com/guides/failed-to-fetch): Failed to fetch means a fetch() request never got an HTTP response. The six usual causes, and how to tell them apart using the console and the Network tab. ### Browser and device - [Browser info](https://snags.com/tools/browser-info): Free tool. Your browser, device and screen in one copyable block for a bug report. - [How to hard refresh in Chrome, Edge, Firefox and Safari](https://snags.com/guides/hard-refresh): A hard refresh reloads a page without your browser's saved copies. The keys for Chrome, Edge, Firefox and Safari on Windows and Mac, and when to clear cache. - [What is a user agent? How to read a user agent string](https://snags.com/guides/what-is-a-user-agent): A user agent string tells websites which browser and system you use. How to read one part by part, why it misleads, and what Client Hints change. ### Bug reports - [The bug report template that actually gets bugs fixed](https://snags.com/guides/bug-report-template): A copy-paste bug report template with a filled-in example, GitHub and Jira variants, and honest notes on which fields matter and which are theater. ## Tools Free tools that run in the browser: https://snags.com/tools - [HAR analyzer](https://snags.com/tools/har-checker): Find the failed requests and the secrets in a HAR file, without uploading it. - [Browser info](https://snags.com/tools/browser-info): Your browser, device and screen in one copyable block for a bug report. ## Insights Also as RSS: https://snags.com/insights/rss.xml - [How to write bug reports an AI coding agent can actually fix](https://snags.com/insights/bug-reports-ai-agents-can-fix): Agents fix bugs fast when the report carries the element, the action trail, the real error and a failing test. Here is what that looks like in practice.