[{"data":1,"prerenderedAt":703},["ShallowReactive",2],{"blog-posts":3,"post-\u002Fblog\u002Fclaude-code-fix-bugs":292},[4,19,39,54,69,84,95,107,122,134,144,155,168,177,192,201,213,225,236,247,258,271,280],{"path":5,"title":6,"description":7,"date":8,"modified":8,"draft":9,"locale":10,"category":11,"image":12,"translationKey":12,"tags":13,"readingTime":18},"\u002Fblog\u002Fclaude-code-fix-bugs","How to Use Claude Code to Fix the Bugs Your Clients Report","How to use Claude Code to fix bugs: what it needs from a bug report, how to connect it to client feedback over MCP, and how to review the fix before you resolve it.","2026-10-27T08:00:00+00:00",false,"en","workflow",null,[14,15,16,17],"claude code fix bugs","claude code mcp","ai bug fixing","bug report",7,{"path":20,"title":21,"description":22,"date":23,"modified":24,"draft":9,"locale":10,"category":25,"image":26,"translationKey":32,"tags":33,"readingTime":38},"\u002Fblog\u002Fbest-website-feedback-tools","How to Choose a Website Feedback Tool (2026 Checklist)","How to choose the best website feedback tool in 2026: the tool types, 12 criteria, a free scoring template (Excel) and a one-week trial plan with a real client.","2026-10-07T09:00:00+00:00","2026-10-22T10:00:00+00:00","guides",{"src":27,"card":28,"alt":29,"width":30,"height":31},"\u002Fwp-content\u002Fuploads\u002F2023\u002F09\u002Fscreencode_7_Bug_tracker_GiveFeedback.jpg","\u002Fwp-content\u002Fuploads\u002F2023\u002F09\u002Fscreencode_7_Bug_tracker_GiveFeedback-400x250.jpg","Code on a screen, illustrating how to choose a website feedback tool",1200,630,"feedback-tools",[34,35,36,37],"best website feedback tool","website feedback tool free","visual website feedback tool","client feedback",8,{"path":40,"title":41,"description":42,"date":23,"modified":24,"draft":9,"locale":10,"category":11,"image":43,"translationKey":48,"tags":49,"readingTime":38},"\u002Fblog\u002Fclient-website-approval","Client Website Approval: How to Get Sign-Off Without Delays","Client website approval made simple: the 5 approval stages, a revision-limit clause, a sign-off email, a free website sign-off form (Word) and a checklist.",{"src":44,"card":45,"alt":46,"width":47,"height":30},"\u002Fwp-content\u002Fuploads\u002F2023\u002F06\u002FAutomating-Project-Management-for-Efficiency-Sized.jpg","\u002Fwp-content\u002Fuploads\u002F2023\u002F06\u002FAutomating-Project-Management-for-Efficiency-Sized-400x250.jpg","Two people reviewing a printed document with a pen, ready for client website approval",1920,"client-approval",[50,51,52,53],"client approval process","website sign off","revision rounds","web agency",{"path":55,"title":56,"description":57,"date":23,"modified":24,"draft":9,"locale":10,"category":25,"image":58,"translationKey":62,"tags":63,"readingTime":68},"\u002Fblog\u002Fhow-to-collect-client-feedback-on-a-website","How to Collect Client Feedback on a Website (Step by Step)","How to collect client feedback on a website: 5 methods compared, a review round step by step, good vs vague feedback examples and a briefing email to send today.",{"src":59,"card":60,"alt":61,"width":30,"height":31},"\u002Fwp-content\u002Fuploads\u002F2023\u002F07\u002FFree_Bug_tracking_web_Designer_GiveFeedback.jpg","\u002Fwp-content\u002Fuploads\u002F2023\u002F07\u002FFree_Bug_tracking_web_Designer_GiveFeedback-400x250.jpg","Web designer at a desk reviewing client feedback on a website","client-feedback",[64,65,66,67],"client feedback on website","website feedback examples","client feedback examples","website review process",9,{"path":70,"title":71,"description":72,"date":23,"modified":24,"draft":9,"locale":73,"category":25,"image":74,"translationKey":78,"tags":79,"readingTime":18},"\u002Fes\u002Fblog\u002Fanotar-capturas-de-pantalla-web","Cómo anotar capturas de pantalla de una web (Mac, Windows y online)","Cómo anotar capturas de pantalla en Windows, Mac, online o en Chrome, cómo capturar una página web entera y cómo marcar los errores para que se arreglen.","es",{"src":75,"card":76,"alt":77,"width":30,"height":31},"\u002Fwp-content\u002Fuploads\u002F2023\u002F07\u002FFree_Bug_tracking_office_colours_pc_GiveFeedback.jpg","\u002Fwp-content\u002Fuploads\u002F2023\u002F07\u002FFree_Bug_tracking_office_colours_pc_GiveFeedback-400x250.jpg","Persona anotando capturas de pantalla de una web para enviarlas al equipo de desarrollo","screenshot-annotation",[80,81,82,83],"anotar capturas de pantalla","captura de pantalla","anotar captura en Mac","anotar captura en Windows",{"path":85,"title":86,"description":87,"date":23,"modified":24,"draft":9,"locale":73,"category":11,"image":88,"translationKey":48,"tags":90,"readingTime":38},"\u002Fes\u002Fblog\u002Faprobacion-cliente-proyecto-web","Aprobación del cliente en un proyecto web: cómo conseguirla","Aprobación del cliente en un proyecto web: las 5 fases, una cláusula para limitar revisiones, un email de aprobación, un formulario de aprobación gratis y una checklist.",{"src":44,"card":45,"alt":89,"width":47,"height":30},"Dos personas revisan un documento con un bolígrafo antes de la aprobación del cliente en un proyecto web",[91,92,93,94],"aprobación del cliente","rondas de revisión","presupuesto web","agencia web",{"path":96,"title":97,"description":98,"date":23,"modified":24,"draft":9,"locale":73,"category":11,"image":99,"translationKey":101,"tags":102,"readingTime":68},"\u002Fes\u002Fblog\u002Fcapturas-anotadas-en-asana","Capturas anotadas en Asana: cómo llevar el feedback web a tareas","Cómo llevar capturas anotadas y feedback web a Asana: plantilla CSV gratis, cinco métodos comparados y tareas automáticas desde el feedback del cliente.",{"src":27,"card":28,"alt":100,"width":30,"height":31},"Capturas anotadas de una web convertidas en tareas de Asana","asana",[103,104,105,106],"capturas anotadas en Asana","plantilla Asana","gestión de bugs","feedback web",{"path":108,"title":109,"description":110,"date":23,"modified":24,"draft":9,"locale":73,"category":25,"image":111,"translationKey":115,"tags":116,"readingTime":121},"\u002Fes\u002Fblog\u002Fchecklist-qa-web-antes-de-lanzar","Checklist web: más de 70 comprobaciones antes de lanzar","Checklist web con más de 70 comprobaciones por áreas: formularios, enlaces, móvil, navegadores, velocidad, SEO, accesibilidad y WordPress, con plantilla Excel gratis.",{"src":112,"card":113,"alt":114,"width":30,"height":31},"\u002Fwp-content\u002Fuploads\u002F2023\u002F08\u002FFree_Bug_tracker_people_pc_GiveFeedback.jpg","\u002Fwp-content\u002Fuploads\u002F2023\u002F08\u002FFree_Bug_tracker_people_pc_GiveFeedback-400x250.jpg","Persona revisando una web con una checklist QA antes del lanzamiento","qa-checklist",[117,118,119,120],"checklist web","checklist QA web","pruebas web","lanzamiento web",12,{"path":123,"title":124,"description":125,"date":23,"modified":24,"draft":9,"locale":73,"category":25,"image":126,"translationKey":128,"tags":129,"readingTime":68},"\u002Fes\u002Fblog\u002Fcomo-escribir-un-informe-de-bugs","Plantilla de reporte de errores (bugs): gratis, con ejemplos","Plantilla de reporte de errores gratis en Excel, Google Sheets y Word, con un ejemplo de informe de bugs bueno y uno malo y los campos que importan en una web.",{"src":27,"card":28,"alt":127,"width":30,"height":31},"Código JavaScript en una pantalla, ilustrando cómo escribir un informe de bugs de una web","bug-report",[130,131,132,133],"plantilla de reporte de errores","reporte de errores","informe de bugs","ejemplo de reporte de errores",{"path":135,"title":136,"description":137,"date":23,"modified":24,"draft":9,"locale":73,"category":25,"image":138,"translationKey":62,"tags":140,"readingTime":68},"\u002Fes\u002Fblog\u002Fcomo-recoger-feedback-de-clientes-en-una-web","Cómo pedir feedback a un cliente sobre su web (paso a paso)","Cómo pedir feedback a un cliente sobre su web: 5 métodos comparados, una ronda de revisión paso a paso, ejemplos de feedback bueno y vago y un email para enviar hoy.",{"src":59,"card":60,"alt":139,"width":30,"height":31},"Diseñador web en su mesa revisando el feedback de clientes sobre una web",[141,142,106,143],"cómo pedir feedback a un cliente","feedback de clientes","revisión de una web",{"path":145,"title":146,"description":147,"date":23,"modified":24,"draft":9,"locale":73,"category":11,"image":148,"translationKey":150,"tags":151,"readingTime":38},"\u002Fes\u002Fblog\u002Ffeedback-web-en-notion","Bugs en Notion: gestiona el feedback de tu web paso a paso","Cómo gestionar bugs en Notion en proyectos web: plantilla gratis, propiedades, vistas tablero, rutina de triaje y cómo recibir el feedback del cliente solo.",{"src":44,"card":45,"alt":149,"width":47,"height":30},"Equipo organizando bugs y feedback de clientes de una web en Notion","notion",[152,153,154,106],"bugs en Notion","plantilla Notion","seguimiento de bugs",{"path":156,"title":157,"description":158,"date":23,"modified":24,"draft":9,"locale":73,"category":159,"image":160,"translationKey":162,"tags":163,"readingTime":68},"\u002Fes\u002Fblog\u002Fherramientas-gratis-seguimiento-bugs","Herramientas gratis de seguimiento de bugs para webs (2026)","Herramientas gratis de seguimiento de bugs para equipos web: los planes gratuitos de Jira, Trello, ClickUp, Notion, Asana, monday.com y Wrike, y una hoja de cálculo gratis.","comparisons",{"src":112,"card":113,"alt":161,"width":30,"height":31},"Equipo revisando incidencias en una herramienta gratis de seguimiento de bugs","free-bug-tracking",[164,165,166,167],"herramientas gratis seguimiento de bugs","bug tracker","gestión de incidencias","hoja de seguimiento de bugs",{"path":169,"title":170,"description":171,"date":23,"modified":24,"draft":9,"locale":73,"category":25,"image":172,"translationKey":32,"tags":174,"readingTime":68},"\u002Fes\u002Fblog\u002Fmejores-herramientas-feedback-visual-web","Cómo elegir una herramienta de feedback visual para tu web","Cómo elegir entre las herramientas de feedback visual web en 2026: tipos, 12 criterios, una plantilla de evaluación gratis en Excel y una prueba de una semana.",{"src":27,"card":28,"alt":173,"width":30,"height":31},"Código en una pantalla, ilustración de cómo elegir entre herramientas de feedback visual web",[175,106,176,142],"herramientas de feedback visual","feedback visual",{"path":178,"title":179,"description":180,"date":23,"modified":24,"draft":9,"locale":73,"category":25,"image":181,"translationKey":185,"tags":186,"readingTime":191},"\u002Fes\u002Fblog\u002Fpruebas-de-aceptacion-uat-web","Pruebas de aceptación de usuario (UAT): ejemplos y plantilla","Qué son las pruebas de aceptación de usuario (UAT), diferencias con el QA, ejemplos de escenarios, checklist para webs y plantillas gratis en Excel y Word.",{"src":182,"card":183,"alt":184,"width":30,"height":31},"\u002Fwp-content\u002Fuploads\u002F2023\u002F08\u002FFree_Bug_tracking_testing-man_GiveFeedback.jpg","\u002Fwp-content\u002Fuploads\u002F2023\u002F08\u002FFree_Bug_tracking_testing-man_GiveFeedback-400x250.jpg","Cliente haciendo pruebas de aceptación UAT de su nueva web frente al ordenador","uat",[187,188,189,190],"pruebas de aceptación","pruebas de aceptación de usuario","plan de pruebas de aceptación","ejemplo pruebas de aceptación",10,{"path":193,"title":194,"description":195,"date":23,"modified":24,"draft":9,"locale":73,"category":25,"image":196,"translationKey":198,"tags":199,"readingTime":38},"\u002Fes\u002Fblog\u002Fque-es-el-feedback-visual","Qué es el feedback visual y por qué agiliza tus proyectos web","Qué es el feedback visual: comentarios sobre la propia web con capturas marcadas, vídeo o notas. Tipos, ventajas, ejemplos y qué pedirle a una herramienta.",{"src":59,"card":60,"alt":197,"width":30,"height":31},"Diseñador web revisando el feedback visual sobre una interfaz","visual-feedback",[176,106,200,142],"capturas anotadas",{"path":202,"title":203,"description":204,"date":205,"modified":24,"draft":9,"locale":10,"category":11,"image":206,"translationKey":150,"tags":208,"readingTime":38},"\u002Fblog\u002Fsupercharge-your-workflow-with-the-notion-bug-tracker-extension","Notion Bug Tracker Template (Free) for Website Projects","Free Notion bug tracker template for website projects: import the CSV, set up the properties and board views, and send client feedback into Notion.","2025-04-24T16:17:44+00:00",{"src":44,"card":45,"alt":207,"width":47,"height":30},"Team organizing website bugs and client feedback in a Notion bug tracker",[209,210,211,212],"notion bug tracker template","notion issue tracker template","bug tracking","website feedback",{"path":214,"title":215,"description":216,"date":217,"modified":24,"draft":9,"locale":10,"category":25,"image":218,"translationKey":185,"tags":220,"readingTime":68},"\u002Fblog\u002Fuser-acceptance-testing-in-software-development","User Acceptance Testing (UAT): Template, Checklist & Examples","What user acceptance testing is, UAT vs QA, test scenario examples, a UAT checklist for websites and free templates: Excel test plan and Word sign-off form.","2023-09-28T17:32:27+00:00",{"src":182,"card":183,"alt":219,"width":30,"height":31},"Client doing user acceptance testing on a new website at his desk",[221,222,223,224],"user acceptance testing","UAT testing","user acceptance testing template","user acceptance testing checklist for website",{"path":226,"title":227,"description":228,"date":229,"modified":24,"draft":9,"locale":10,"category":159,"image":230,"translationKey":162,"tags":232,"readingTime":68},"\u002Fblog\u002Fbug-tracking-tools-free","Free Bug Tracking Tools for Web Teams (2026 Comparison)","Free bug tracking tools compared for web teams: the free plans of Jira, Trello, ClickUp, Notion, Asana, monday.com and Wrike, plus a free bug tracking spreadsheet.","2023-09-21T16:56:47+00:00",{"src":112,"card":113,"alt":231,"width":30,"height":31},"Team at a computer reviewing issues in a free bug tracking tool",[233,165,234,235],"free bug tracking tools","bug tracking spreadsheet","issue tracking",{"path":237,"title":238,"description":239,"date":240,"modified":24,"draft":9,"locale":10,"category":25,"image":241,"translationKey":128,"tags":243,"readingTime":38},"\u002Fblog\u002Fwhat-to-put-in-a-bug-report","Bug Report Template (Free Excel, Word & Google Sheets) + Examples","Free bug report template for Excel, Google Sheets and Word, with a good and a bad bug report example and the fields that matter for website bugs.","2023-09-11T14:43:18+00:00",{"src":27,"card":28,"alt":242,"width":30,"height":31},"JavaScript code on a screen, illustrating how to write a bug report for a website",[244,245,246,234],"bug report template","bug report example","how to write a bug report",{"path":248,"title":249,"description":250,"date":251,"modified":24,"draft":9,"locale":10,"category":11,"image":252,"translationKey":101,"tags":254,"readingTime":38},"\u002Fblog\u002F1-way-to-get-annotated-screengrabs-into-asana","Asana Bug Tracking: Free Template and Annotated Screenshots","Asana bug tracking for website projects: a free CSV template, five ways to get annotated screenshots into tasks, and automatic tasks from client feedback.","2023-09-11T11:56:04+00:00",{"src":27,"card":28,"alt":253,"width":30,"height":31},"Annotated screenshots of a website being turned into Asana tasks",[255,256,257,212],"asana bug tracking","asana bug tracking template","annotated screenshots",{"path":259,"title":260,"description":261,"date":262,"modified":24,"draft":9,"locale":10,"category":25,"image":263,"translationKey":115,"tags":265,"readingTime":270},"\u002Fblog\u002Fspeed-up-qa-testing","Website QA Checklist: 70+ Checks Before Launch (Free Template)","A website QA checklist with 70+ checks by area (forms, links, devices, browsers, speed, SEO, accessibility, WordPress), plus a free Excel and Google Sheets template.","2023-08-19T11:32:36+00:00",{"src":112,"card":113,"alt":264,"width":30,"height":31},"Person running a website QA checklist on a laptop before launch",[266,267,268,269],"website QA checklist","website testing checklist","website qa checklist template excel","wordpress website testing checklist",11,{"path":272,"title":273,"description":274,"date":275,"modified":24,"draft":9,"locale":10,"category":25,"image":276,"translationKey":198,"tags":278,"readingTime":38},"\u002Fblog\u002Fvisual-feedback-faster-bug-testing","What Is Visual Feedback? A Guide for Web Teams","What is visual feedback? Feedback given on the website itself with marked-up screenshots, video or pinned comments. Types, examples and a tool checklist.","2023-08-09T17:41:00+00:00",{"src":59,"card":60,"alt":277,"width":30,"height":31},"Web designer reviewing visual feedback on a website interface",[279,36,257,212],"visual feedback",{"path":281,"title":282,"description":283,"date":284,"modified":24,"draft":9,"locale":10,"category":25,"image":285,"translationKey":78,"tags":287,"readingTime":18},"\u002Fblog\u002Fscreen-grab-annotation-apps","How to Annotate a Screenshot of a Website (Mac, Windows & Online)","How to annotate a screenshot on Mac, Windows, online or in Chrome, how to capture a full web page, and how to mark up website screenshots so developers fix them.","2023-08-02T23:25:13+00:00",{"src":75,"card":76,"alt":286,"width":30,"height":31},"Person at a computer annotating website screenshots for a developer",[288,289,290,291],"annotate screenshot","annotate screenshot mac","annotate screenshot windows","annotate screenshot online",{"id":293,"title":6,"body":294,"category":11,"date":8,"description":7,"draft":9,"extension":679,"faq":680,"image":12,"locale":10,"meta":695,"modified":8,"navigation":696,"path":5,"readingTime":18,"seo":697,"seoTitle":698,"stem":699,"tags":700,"tldr":701,"translationKey":12,"__hash__":702},"blog\u002Fblog\u002Fclaude-code-fix-bugs.md",{"type":295,"value":296,"toc":669},"minimark",[297,301,306,309,312,316,319,363,366,370,373,408,416,420,430,457,513,527,535,539,542,550,553,585,588,592,599,605,608,612,615,632,638,642,645,651,654,657,665],[298,299,300],"p",{},"Using Claude Code to fix bugs works best when the bug arrives with evidence. Ask it to \"fix the contact form\" and it will read your code and guess; give it the page, the browser, the console error and a screenshot of what the client saw, and it can usually go straight to the cause. The difference is in the bug report, so most of the work is getting complete reports to Claude without copying and pasting them.",[302,303,305],"h2",{"id":304},"what-does-fixing-bugs-with-claude-code-mean","What does fixing bugs with Claude Code mean?",[298,307,308],{},"Fixing bugs with Claude Code means handing a bug to Anthropic's coding agent, which runs in your terminal inside your repository, and letting it find the cause, change the code and run your checks while you review the result. It reads files, searches the codebase, runs commands such as your tests, and edits code, asking for permission as it goes.",[298,310,311],{},"What it can't do is see the client's screen. A bug that only happens on a 390-pixel-wide phone in Safari is invisible from the repository. That information has to come from the report.",[302,313,315],{"id":314},"can-claude-code-fix-bugs-on-its-own","Can Claude Code fix bugs on its own?",[298,317,318],{},"It can fix a large share of everyday website bugs on its own when the report is complete, and almost none when it isn't. A vague report sends any developer, human or not, into guessing. The table shows what Claude can do with each kind of report.",[320,321,322,335],"table",{},[323,324,325],"thead",{},[326,327,328,332],"tr",{},[329,330,331],"th",{},"What the report says",[329,333,334],{},"What Claude Code can do with it",[336,337,338,347,355],"tbody",{},[326,339,340,344],{},[341,342,343],"td",{},"\"The form is broken\"",[341,345,346],{},"Read every form in the codebase and guess which one, then guess how it breaks",[326,348,349,352],{},[341,350,351],{},"\"The contact form on \u002Fcontact doesn't send\"",[341,353,354],{},"Find the right form and its handler, but not the reason it fails",[326,356,357,360],{},[341,358,359],{},"The page URL, \"Safari 18, iOS 18, 390x844\", the console error \"TypeError: cart is undefined\" and a screenshot",[341,361,362],{},"Open the component for that page, trace the error to the line that throws it, and check the layout at that screen size",[298,364,365],{},"The third report is what a developer would ask the client for anyway. The point is to collect it before anyone asks.",[302,367,369],{"id":368},"what-does-claude-code-need-from-a-bug-report","What does Claude Code need from a bug report?",[298,371,372],{},"The same fields a good bug report has always had, with two that matter even more for an AI: the console log and the screenshot, because Claude can't reproduce the client's session.",[374,375,376,384,390,396,402],"ul",{},[377,378,379,383],"li",{},[380,381,382],"strong",{},"Page URL:"," where it happened, so Claude can map it to a route, template or component.",[377,385,386,389],{},[380,387,388],{},"Browser, operating system and screen size:"," many website bugs only exist in one browser or below one width.",[377,391,392,395],{},[380,393,394],{},"Console messages, errors and failed requests:"," the closest thing to a stack trace a website visitor can give you.",[377,397,398,401],{},[380,399,400],{},"Screenshot, annotated:"," what the client saw and where they pointed, which settles \"which button?\" at once.",[377,403,404,407],{},[380,405,406],{},"What they expected and what happened instead:"," separates a bug from a change request.",[298,409,410,411,415],{},"Our ",[412,413,244],"a",{"href":414},"\u002Fblog\u002Fwhat-to-put-in-a-bug-report\u002F"," lists every field with examples. A feedback widget fills most of them in automatically: GiveFeedback.io attaches the URL, the browser details and the console log to every report and lets the client mark up the screenshot.",[302,417,419],{"id":418},"how-do-you-connect-claude-code-to-your-client-feedback","How do you connect Claude Code to your client feedback?",[298,421,422,423,429],{},"Claude Code talks to other services through MCP, the ",[412,424,428],{"href":425,"rel":426},"https:\u002F\u002Fmodelcontextprotocol.io",[427],"nofollow","Model Context Protocol",", an open standard for giving AI assistants tools. GiveFeedback.io is an MCP server, so once it's added, Claude can read your reports directly instead of you pasting them in.",[431,432,433,444,451,454],"ol",{},[377,434,435,436,439,440,443],{},"In GiveFeedback.io, open the project's ",[380,437,438],{},"Integrations"," tab and choose ",[380,441,442],{},"Connect Claude",". It works alongside the project's integration, so reports keep reaching Jira, Slack or your email as before.",[377,445,446,447,450],{},"Under ",[380,448,449],{},"Projects it reaches",", tick any other of your projects Claude should see, such as the staging copy of the same site.",[377,452,453],{},"Copy the command it shows. It contains your token and is only shown once.",[377,455,456],{},"Run it in your project folder:",[458,459,464],"pre",{"className":460,"code":461,"language":462,"meta":463,"style":463},"language-bash shiki shiki-themes github-light github-dark","claude mcp add --transport http \\\n  givefeedback https:\u002F\u002Fapp.givefeedback.io\u002Fmcp \\\n  --header \"Authorization: Bearer gfmcp_...\"\n","bash","",[465,466,467,493,504],"code",{"__ignoreMap":463},[468,469,472,476,480,483,487,490],"span",{"class":470,"line":471},"line",1,[468,473,475],{"class":474},"sScJk","claude",[468,477,479],{"class":478},"sZZnC"," mcp",[468,481,482],{"class":478}," add",[468,484,486],{"class":485},"sj4cs"," --transport",[468,488,489],{"class":478}," http",[468,491,492],{"class":485}," \\\n",[468,494,496,499,502],{"class":470,"line":495},2,[468,497,498],{"class":478},"  givefeedback",[468,500,501],{"class":478}," https:\u002F\u002Fapp.givefeedback.io\u002Fmcp",[468,503,492],{"class":485},[468,505,507,510],{"class":470,"line":506},3,[468,508,509],{"class":485},"  --header",[468,511,512],{"class":478}," \"Authorization: Bearer gfmcp_...\"\n",[431,514,516],{"start":515},5,[377,517,518,519,522,523,526],{},"In Claude Code, type ",[465,520,521],{},"\u002Fmcp"," to check that ",[465,524,525],{},"givefeedback"," is connected.",[298,528,529,530,534],{},"Claude now has four tools: list your projects, list their feedback (newest first, filtered by project, status or words), read one report in full, and change a report's status. The ",[412,531,533],{"href":532},"\u002Fclaude-mcp-server\u002F","Claude page"," shows what each one returns.",[302,536,538],{"id":537},"a-bug-fixing-session-step-by-step","A bug-fixing session, step by step",[298,540,541],{},"Start with a plain request. The app suggests this one: \"Show me the open feedback and fix the first bug.\" Claude lists the open reports and picks one up. To work on a specific report, use the ready-made prompt with its number:",[458,543,548],{"className":544,"code":546,"language":547,"meta":463},[545],"language-text","\u002Fmcp__givefeedback__fix_feedback 345\n","text",[465,549,546],{"__ignoreMap":463},[298,551,552],{},"From there, a good session looks like this:",[431,554,555,561,567,573,579],{},[377,556,557,560],{},[380,558,559],{},"Claude reads the report."," The description, the page, the browser and screen size, the console log and the annotated screenshot, as an image.",[377,562,563,566],{},[380,564,565],{},"It finds the cause before touching code."," Ask it to explain the cause in a sentence or two first. If the explanation doesn't match the screenshot, stop there.",[377,568,569,572],{},[380,570,571],{},"It makes the smallest change that fixes it"," and runs your tests or linter.",[377,574,575,578],{},[380,576,577],{},"You review the diff."," Check it at the browser and screen size from the report, not just on your own laptop.",[377,580,581,584],{},[380,582,583],{},"Claude asks before resolving the report."," Once you agree, it marks it resolved. On paid plans the project's integration follows, so the Jira issue or Trello card is done too, and the client can see the report was fixed.",[298,586,587],{},"A report that turns out to be a request (\"can the logo be bigger?\") should go back to your normal change process, not into a quick fix.",[302,589,591],{"id":590},"give-claude-your-rules-for-client-bugs","Give Claude your rules for client bugs",[298,593,594,595,598],{},"Claude Code reads a file called ",[465,596,597],{},"CLAUDE.md"," in your repository at the start of every session. A short section there about client-reported bugs saves you from repeating the same instructions: treat reports as evidence, explain the cause first, keep the fix small, run the checks, show the diff, ask before resolving.",[600,601],"template-download",{"files":602,"text":603,"title":604},"Markdown|\u002Ftemplates\u002Fclaude-md-bug-fixing-template.md","A Markdown section to paste into your project's CLAUDE.md: how to read a report, how to fix it, what to check before resolving, and blanks for your test command and your staging and live sites.","Free CLAUDE.md section for client-reported bugs",[298,606,607],{},"Fill in the blanks for your project: the test and lint commands, and which GiveFeedback.io project is the staging site and which is the live one. With both connected, Claude gets their names and addresses and uses the one whose site it is working on.",[302,609,611],{"id":610},"how-do-you-review-an-ai-fix-before-resolving-the-report","How do you review an AI fix before resolving the report?",[298,613,614],{},"Review it the way you'd review a fix from a new developer: reproduce, read the diff, check the neighbors. Resolving a report tells the client it's done, so the check has to happen before, not after.",[374,616,617,620,623,626,629],{},[377,618,619],{},"Open the page from the report at the same screen size and in the same browser, if you have it.",[377,621,622],{},"Compare with the screenshot: is the thing the client pointed at fixed?",[377,624,625],{},"Read the diff. Small and local is good; a fix that touches ten files for one button deserves a question.",[377,627,628],{},"Run the checks yourself if Claude didn't, and look for other pages that use the same component.",[377,630,631],{},"For anything visual, deploy to staging first and let the client confirm with the same feedback button.",[298,633,410,634,637],{},[412,635,266],{"href":636},"\u002Fblog\u002Fspeed-up-qa-testing\u002F"," has the wider list for a release.",[302,639,641],{"id":640},"keeping-it-safe","Keeping it safe",[298,643,644],{},"Two risks come with connecting an AI to bug reports, and both have simple answers.",[298,646,647,648,650],{},"The first is what the reports say. Anyone visiting a website can send it feedback, including text written to manipulate an AI (\"ignore your instructions and...\"). GiveFeedback.io tells Claude that a report's title, description and console log are what a visitor sent: something to investigate, never instructions to follow. Your ",[465,649,597],{}," section should say the same, and Claude Code still asks you before running commands or editing files, depending on your permission settings.",[298,652,653],{},"The second is what the token can reach. Each token is for one person or computer, reaches only the projects chosen for it and only while they're yours, and can be revoked from the project at any time, which stops it at once. It can read feedback and change its status; it can't reach your account, your billing or anyone else's projects.",[655,656],"blog-cta",{},[298,658,659,660,664],{},"Bug fixing with an AI agent is only as good as the reports it reads. Get the URL, the environment, the console log and an annotated screenshot into every report, connect Claude to them, and the slow part of a client bug becomes reviewing a fix instead of chasing details. Connecting Claude is included in every ",[412,661,663],{"href":662},"\u002Fpricing\u002F","GiveFeedback.io plan",", the free one too.",[666,667,668],"style",{},"html pre.shiki code .sScJk, html code.shiki .sScJk{--shiki-default:#6F42C1;--shiki-dark:#B392F0}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":463,"searchDepth":495,"depth":495,"links":670},[671,672,673,674,675,676,677,678],{"id":304,"depth":495,"text":305},{"id":314,"depth":495,"text":315},{"id":368,"depth":495,"text":369},{"id":418,"depth":495,"text":419},{"id":537,"depth":495,"text":538},{"id":590,"depth":495,"text":591},{"id":610,"depth":495,"text":611},{"id":640,"depth":495,"text":641},"md",[681,683,686,689,692],{"question":315,"answer":682},"It can find and fix many bugs without help when it has good evidence: the page, the environment, the error in the console and a screenshot. It still needs you for two things: deciding whether the report is a bug or a change request, and reviewing the fix before it ships. Treat it as a fast developer who has never seen the client.",{"question":684,"answer":685},"How do I connect Claude Code to my bug reports?","Add the bug reports as an MCP server. With GiveFeedback.io, open the project's Integrations tab, choose Connect Claude and run the command it shows in your project folder. Claude Code can then list the open reports, read one in full with its screenshot and console log, and resolve it when you agree.",{"question":687,"answer":688},"Does Claude Code see the screenshot of the bug?","Yes, when the bug report tool sends it. GiveFeedback.io's MCP server passes the annotated screenshot to Claude as an image, along with the page URL, the browser, operating system and screen size, and the log of console messages, errors and failed requests captured with the report.",{"question":690,"answer":691},"Is it safe to let an AI read bug reports from website visitors?","Only if the reports are treated as data. Anyone can type anything into a feedback form, so the text must never be read as instructions. GiveFeedback.io tells Claude that a report's title, description and console log are what a visitor sent, and a token only reaches the projects you chose, which you can revoke at any time.",{"question":693,"answer":694},"Which plan do I need to connect Claude?","Any plan, including the free one. Connecting Claude is included everywhere. On Pro and Company, resolving a report from Claude also marks the linked task done in your project tool, such as a Jira issue or a Trello card, the same as resolving it in the dashboard.",{},true,{"title":6,"description":7},"How to Use Claude Code to Fix Bugs From Client Reports","blog\u002Fclaude-code-fix-bugs",[14,15,16,17],"To use Claude Code to fix bugs, give it the same evidence a developer needs: the page URL, the browser and screen size, the console errors, the steps and a screenshot. Connect it to your bug reports through an MCP server so it reads them directly, ask it to find the cause before changing code, and review the diff yourself before the report is marked resolved.","4hgTK4XCy1h8kgDXInKs-MH1VPwqpSNFShyJByQNmuY",1793101557446]