Help us fix bugs faster - how to write a good bug report

[BarsatZulkarnine]

Bug reports are coming in fast and that's great, but a lot of them are hard to act on without enough context to reproduce the problem.

If you're reporting a bug, here's what actually helps:

The minimum:

• What you did, step by step
• What you expected to happen
• What actually happened
• How you're running Odysseus (Docker, manual Python, macOS app, Windows)
• Which model/provider you're using

What moves things from "hard to fix" to "fixed":

• A short screen recording showing the issue happening. Loom, QuickTime, whatever - just something we can watch
• Logs. If you're on Docker: docker compose logs --tail=200 odysseus. If manual: check your terminal output. Paste the relevant lines
• Browser console errors (F12 -> Console tab) for anything UI related

What makes a report hard to act on:

• "It doesn't work" with no other context
• Screenshots of just the error message without the steps that caused it
• No mention of install method or OS

The more context you give, the faster someone can pick it up and fix it.