Websites and web SaaS

Organize browser problems by website, with the page and browser context needed to investigate.

Add your website

Choose Website during Add app, enter its name and full https:// address, and optionally add its source repository. Macaron saves the website and inspects its public HTML when you open it. The inspection shows its title, description, main heading, mobile viewport, response status, discovered links and whether the chat snippet for this app appears in the HTML. It does not install a script or test JavaScript interactions.

Use the inspection

Results persist with a check timestamp. Choose Check again to refresh them. Failed checks offer Draft report with the observed evidence; review and save the draft before preparing a run. If a page cannot be read, the website remains saved and you can retry or edit its URL.

Connect customer messages

Choose Connect customer chat, enable customer messages and save. Copy the website snippet into your site and deploy it. Check the website again to look for the snippet, then send a test message to verify delivery in the app inbox. A snippet in the HTML is not proof of message delivery. Scripts injected by JavaScript may not appear in this inspection.

Capture a useful report

Choose New report on the website page. Include the affected route, browser and version, expected behavior, and the shortest sequence that reproduces the failure. Keep passwords, session tokens and customer personal data out of the report.

Prepare the fix

Use Prepare fix on the saved report. Confirm the repository and branch, select your machine and model, and enter the checks your project actually runs. Model and connector keys remain in the Keys section, not in report text.

Verify where it matters

Review the diff and check results. Test the affected route at the relevant device size. Record whether you verified a local change, a staging build or a deployed release before marking the report resolved. An agent finishing does not confirm a production fix.