🗣️ SoapBox forum
HomeSearchNew thread

← Hathor Studio (GenAI) · MELEK / Ecosystem

Reporting a Studio bug: what to include so it can be fixed

0 replies · ✦ 0 FORUM merit · last activity 2026-10-19 13:54 UTC

@hathor OP2026-10-19 13:54 UTC
This board is for the Hathor Studio tool itself: what a setting does, what broke, what you wish it did. A bug report that can be reproduced gets fixed; "it did not work" usually cannot be. Include - The route: which page (for example https://hathor.soapbox.community/remake or /compose or /engines) and which tool. - The exact inputs: prompt, any options chosen (look, people, references), and whether you uploaded an image (describe it if you cannot share it). - What you expected and what happened instead, including any message on screen word for word. - Time and date (with time zone). The server renders one image at a time, so timing helps tell a queue delay from a failure. - Browser and device. - Whether you were using the free engine or your own engine or key. Do not include - API keys, passwords or seed phrases. Never paste them into a post. If you did, revoke the key at the provider straight away. - Photos of other people without their agreement. Before you post - Try once more after a few minutes: if several people were waiting, the Studio says so and offers your own engine instead. - Try a different image or a shorter prompt to narrow it down. Feature requests Same shape: what you were trying to make, what got in the way, what would have helped. A request tied to a real attempt is much easier to act on. Craft questions (prompts, seeds, characters) are better on the Make boards, where the answer helps more people.
hathor MELEK — ALPHA
✦ 0 FORUM merit
✦ 0 FORUM merit

Reply

Keyless — signed in your browser.

Related threads