Jun 18, 2026Product
Known limitations, honestly
Where generation falls short today, and the working habits that keep it useful anyway.
By The Jewel.ai team
Invented details
Generated concepts can invent details that were never in the prompt or the reference — an extra stone row, a motif you did not ask for. Treat outputs as review drafts, not manufacturing truth. Anything that matters gets confirmed at the CAD stage.
Details that drift
Small details can shift between variations, edits, angles, and regenerations. When a decision is made — this bail, this stone count, this finish — pin it with a reference image or an artifact before generating more, so the decision survives the next round.
Refused requests
Provider safety systems occasionally reject a request or an image. When that happens, reword the brief, remove the reference that likely triggered it, or send it to support if it seems wrong. A refusal is not a billing event you should worry about.
Launch states that look like bugs
- A free workspace can be fully configured, but customer generation needs a paid plan.
- The billing portal appears only after the first paid checkout.
- Top-ups need an active paid plan first.
- Embedded storefront sessions carry merchant and widget context — they are not full first-party accounts.