Report a bug
Send a catalog-linked defect report through the existing authenticated feedback contract.
Build a reproducible report
Choose the affected tool, describe the action and result, then state what you expected instead.
Catalog-linked feedback
Select the tool before describing the failure.
The report sends only the selected catalog slug, bug type, localized route, and the message you write here.
Useful evidence
Include browser family, operating system, approximate file size, input format, and the exact control used.
- Redacted exampleUse synthetic or redacted examples when input shape matters.
- RepeatabilityMention whether the failure repeats after a reload.
- Failure typeSeparate a visual issue from an incorrect or missing result.
Keep private material out
The report channel stores the text you submit, so it is intentionally separate from the local workspace.
- Exclude secretsNever include passwords, tokens, financial records, or personal documents.
- Exclude workspace dataDo not paste full tool input or generated output.
- Confirm deliveryThe action returns an explicit failure state if feedback cannot be stored.
How reports progress
A public explanation of the process. Individual submissions remain private unless a verified, redacted update is published.
- 01Received
- 02Reproduce
- 03Fix
- 04Verify
We review feedback and share updates when progress is verified. We cannot promise a response or fix by a specific date.
No verified issue updates are published yet. We will add one only after checking the facts and removing private details.
View your feedback in your accountUnsure whether it is a defect?
Check the operating pattern and privacy guidance before filing a report.