Found a Lorah beta bug? Here's what actually helps

Things will break during the beta. A useful bug report saves a surprising amount of back-and-forth.

Please include:

• Lorah version
• Windows or macOS
• provider or endpoint type involved
• what you were trying to do
• what you expected
• what actually happened
• the shortest reproduction steps you can find
• the error text, if there was one

Screenshots are useful when the problem is visual.

Please don’t post API keys, licence codes, private documents, conversation content, Project Memory, customer/client information, raw workspace exports, local filesystem paths, or private endpoint/LAN details in a public thread.

If the bug involves anything sensitive, send us Modmail instead of posting it publicly. Start with a redacted description. If we need additional diagnostics, we’ll ask for the smallest thing needed to investigate it.

A useful title is specific:

rather than:

And one request from me: tell us when you think the bug might actually be a provider or local-model problem. You don’t need to diagnose it. Just tell us what model/endpoint was involved. Separating Lorah failures from provider/configuration failures is part of what this beta needs to teach us.

Bug reports don’t have to be polished. Reproducible beats polished.