Website bug reports your team can act on.
“It doesn’t work” is a starting point. Build a free Markdown bug report below, or collect customer messages inside your website and keep the conversation, reproduction steps and reviewed fix together in Macaron.
Build a bug report — no signupBy Macaron · Updated
Build a bug report
Turn what happened into a Markdown report. Free, with no account or model key. This tool formats your words; it does not diagnose the bug.
The draft is built in your browser and is not submitted by this tool. Leave out passwords, tokens, payment details and customer personal information.
Copying does not save a report or start an agent.
Keep reports and fixes together in Macaron. Add your app or website, then paste this draft into a new report.
Capture the context that makes a bug reproducible
Start with a short title that describes the failure. Record the website route, browser and version, device and relevant app state. Ask what the customer did immediately before the problem and whether they can repeat it. Expected behavior should describe the result they wanted, not your proposed implementation.
Do not assume a support message includes this information automatically. Ask for missing details and add them to the report. Avoid passwords, session tokens, payment details and unnecessary personal information.
Example bug report
Title: Pay button stays disabled after returning to checkout
Page: /checkout
Environment: Safari on iPhone; record the actual iOS version
Steps:
1. Open checkout with an item in the cart.
2. Switch to another app, then return.
3. Try to continue with payment.
Expected: The customer can continue checkout.
Observed: The Pay button stays disabled.Collect reports from your website
Add the website in Macaron, enable customer chat and copy the installation code from setup. The website widget opens inside your site and routes messages to that product’s inbox. HTML, React / Vite and Next.js installation paths are available.
Adding a URL lets Macaron inspect public HTML for basic page information and the chat snippet. It does not crawl private pages, test checkout, install code or grant access to revenue and analytics. Those connections require separate setup and permission.
Keep the conversation attached to the report
Open the customer conversation and create a fix report when you have enough information to investigate. A manually created report is also useful for problems found by your team. Reports belong to the selected app or website so unrelated products do not share a problem queue.
Save the report before preparing a run. Saving captures the evidence; it does not launch an agent. When you are ready, review the proposed task, repository, branch and checks in run setup.
Verify the original problem before resolving it
Review the diff and the actual test output. Repeat the customer’s steps on the affected browser and device size. Passing a unit test does not prove that the deployed website behaves correctly, and a completed agent run does not automatically resolve a report.
Record what you tested, what happened and whether the fix exists locally, in staging or in production. Resolve the report after verification, then reply to the customer with the status you can confirm.