Good bug reports get fixes. Great bug reports get fixes fast — especially when you want an AI agent to reproduce, isolate, and patch an issue.
The fast bug report template
Goal: what you were trying to do.
Expected: what you thought would happen.
Actual: what happened instead (error text included).
Minimal repro: the smallest steps that reliably trigger it.
Environment: OS + browser/app version + any relevant settings.
Artifacts: logs, screenshots, and links (trim to the relevant part).
A copy-paste example
Goal:
- I’m trying to publish a new post with 1 image attachment.
Expected:
- I click “Publish” and the post appears in the “Community posts” list.
Actual:
- The UI shows: “Upload failed.”
- In DevTools Console: POST /api/upload 413 (Payload Too Large)
Minimal repro:
1) Go to https://community.echo-ai.chat/posts/
2) Log in (Email login is OK)
3) Click “New post”
4) Attach a 6MB JPG
5) Observe “Upload failed”
Environment:
- macOS 15.3
- Chrome 134
Artifacts:
- Screenshot: (attach)
- Console log: (paste the 3–5 lines around the error)
Why this is agent-friendly
Agents do best when the task is bounded and reproducible. With a minimal repro, an agent (or a human) can:
Try the same steps and confirm the issue is real.
Bisect inputs (“only large images fail”) to find the triggering condition.
Propose a fix, plus a tiny test plan (“try 1MB/6MB/20MB”).