Creation threads
Keep prompts, references, settings and outputs together, reuse a request and organize active or archived threads.
On this page
A thread keeps the requests and results for one piece of work together. Use it for a scene, campaign or comparison you expect to revisit. My Library holds the media; the thread holds the iterations around it.
Choose where a request goes
In the image composer, Send in lets you choose New thread or an existing thread. Save as thread saves a new draft before generation. Open workspace opens the thread overview.
A thread can contain repeated image requests, video work and a carousel card. Check the Creator and inputs before adding another request to an existing thread.
Reuse an earlier request
Open the thread. Prompt history reads oldest to newest; All media puts the newest media first. Use Reuse settings to restore an earlier prompt and inputs to the composer. Change the details you need before submitting another request.
Reuse starts another generation when you submit it. Check the model, identity mode, attachments and count; the earlier output is not replaced.
Name and file the work
Rename the thread from its title control. A title can contain up to 160 characters. Under New outputs go to, choose the folder for future results. This changes future output; move existing media from the Library.
Use Pin thread for active work, Archive to put it away, and Move to trash to remove it from the active list. The corresponding actions are Unpin, Unarchive and Restore from trash.
Check draft and job state
Draft saved confirms a saved draft. Draft not saved means you should preserve the prompt and settings before reloading.
A queued request can continue after you close the page. In a comparison, an earlier model’s request can run even if a later request failed. Inspect the thread before submitting the complete comparison again.