Muse may ask questions or present a plan before it changes the canvas. Use these steps to keep the request scoped and intentional.
Answer clarification questions
A question can allow one answer, several answers, free text, or a structured input. Some choices include a visual preview.
Select the answer that matches your intent.
For a multi-step question flow, choose Continue to move forward or Back to revisit an earlier answer.
Use Review answers before the final confirmation.
Choose Edit to change an answer, then Confirm answers.
Pause and resume
Choose Pause for now in a multi-question flow to save your progress. You can start a different request while the question is paused. Choose Resume to return to the saved step.
A simple one-question card uses Confirm and does not show the pause flow.
Review a proposed plan
Confirm the target Visuals or layers.
Check what Muse will change and what it will preserve.
Edit any plan copy that the interface marks as editable.
Choose No, revise the plan to return to the prompt and explain the correction.
Approve the change
Choose Yes, implement this plan only when the plan is ready. Approval starts execution immediately and locks that plan.
Send a message during a run, when available
In editors with mid-run messaging, select the working Visual and check the message box hint before sending.
Send into this run or Enter sends a text-only correction for Muse to read before its next step. Check for Read by Muse; a message that arrived after the run ended was not read during that run.
Cmd/Ctrl+Enter queues a separate request to start after the run finishes. Attached images, staged skills, and sizes queue instead of going into the active run.
Review queued messages above the input. Edit or remove them before they start; Send now, when shown for a text-only message, sends it into the run it is waiting for.
Stop, review, or undo
Use the stop control to end the active run.
Completed runs can report success, review needed, stopped, reverted, or failed.
A completed result may show before/after images, a summary, issues, elapsed time, and usage details.
Use Undo only when it is offered for the result. In editors with per-Visual runs, the newest non-reverted result for each Visual can remain undoable even after work finishes on a different Visual. Undo can be refused if someone changed an affected Visual during or after the run; it must not discard those edits. Older editors may offer Undo only for the latest completed run.
If a request fails to send
Check the connection and send it again. Your conversation history and paused question progress are restored when available.