The Assistant panel

The panel is a conversation: your messages, Assistant’s answers, and the proposals it puts in front of you when a request would change the document.

The controls

• Message box — type in plain language. Enter sends, Shift + Enter starts a new line.
• Send — sends the message. While Assistant is working it becomes Stop, which aborts the request immediately.
• Quick actions — a small menu of the most common requests, which pre-fill the message box so you can complete them: Price, Ring size…, Metal…, Report, Render view.
• Clear History — starts a new conversation. Assistant forgets the thread; your design is untouched.
• Help — opens this documentation.

How a turn works

1. You ask. Every message travels with a brief snapshot of the design you have open — its type, metals, ring size and layers — so Assistant knows what “it” refers to without you explaining.
2. It reads what it needs. If the question requires more, Assistant fetches it on its own: the full element list with parameters, the pricing breakdown, the Boutique data. A status bubble shows what it is doing, with a ✕ to cancel at any point.
3. It answers, or it proposes. A question gets an answer. A request that changes the document gets a proposal card naming the exact command and its arguments, with Apply and Cancel.
4. You decide. Apply runs the command on the real model and Assistant continues from the result — so “resize it and tell me the new weight” works as one turn. Cancel drops it; nothing is executed.

The conversation keeps its context

Follow-ups work the way they do with a person: “and in yellow gold?”, “make it half a size bigger”, “I don’t like it”. Assistant carries the thread until you clear it, so you can refine a result instead of restating the whole request.

You can also chain several instructions in one message — “prepare the design for production, add the dimensions and make a report using Customer A” — and they are proposed and executed in the right order.

When something goes wrong

• An error bubble carries the message from the model or from the command that failed. The most common one is a missing or exhausted OpenRouter key — see Setting Up Assistant.
• A command that could not run reports back in the conversation, and Assistant explains what it needs — often a design element that does not exist in the current model.
• Nothing happening usually means no design is open: Assistant reads the active document, so an empty Rhino gives it nothing to work with.