Midjourney Thinking Mode: A Rerun Checklist
Midjourney AI Team · October 14, 2026 · 6 min read
Midjourney Thinking Mode gives a nearly right image another try with your prompt. Use it when the scene is close but one detail is wrong. An object may be missing, a sign may have the wrong letters, or the layout may ignore your brief. Does the new image fix that flaw without losing the parts that worked? That is the test, not whether it looks more striking.
The feature is an early test on the Alpha website. The October 8 announcement introduces the lightbox action, and the October 7 changelog describes support for V8.2 standard and edit jobs. This guide offers a review method, not a claim that we measured its success rate. It also does not promise the same control on third-party services.
Start with a defect you can name
Choose an image that has one clear failure. “The lamp should be left of the book” is a useful test. “Make this better” is not: you could prefer the new lighting while overlooking the same layout mistake. Save the starting image and its full prompt before trying another version.
Separate the brief into facts and taste. Facts include object count, relative position, exact wording and the required shape of the image. Taste includes warmth, grain and how polished the scene feels. Review facts first. A beautiful result with the wrong product name may still be unusable.
Here is a suggested practice prompt, not the original prompt for any image shown in this guide:
A matte ivory desk lamp to the left of a closed navy notebook,
both on a pale stone table. One small card in front reads "NORTH".
Soft light from the right, quiet background, eye-level product photo.For this exercise, the lamp, notebook, card and word provide separate checks. Do not add five more props to make the test look complex. A small, clear brief makes the cause of failure easier to discuss and the next action easier to choose.
Find the thinking rerun in the lightbox
On Alpha, open an eligible job in the lightbox and look for Rerun (Thinking) near the lower-right controls. The screenshot below shows the action beside the ordinary rerun button. It is a location reference, not a before-and-after comparison or proof that the feature improved that particular image.
Read the job context before clicking. Confirm that you are reviewing the intended V8.2 image rather than an older result with a similar thumbnail. If you cannot see the action, do not invent a prompt flag as a substitute. Check the current Alpha interface and account availability; an experimental rollout can change.
Keep the original export separate from the new result. There is no need to rename every image in a large library. A simple pair of files for this one decision is enough. Also note the prompt and settings you can inspect, so a later reviewer knows what the image was meant to do.
Compare the result with the brief, not your memory
Open both versions at the same display size. First check the named defect. Then inspect the parts that were already right. Look at the whole composition before zooming into letters, edges or hands. A close crop can hide a new problem elsewhere in the frame.
In the practice scene, read the card one letter at a time. Count the main objects and check which side of the notebook holds the lamp. Then ask whether the lamp still has a plausible base, shade and shadow. These are separate observations; do not combine them into a vague “quality improved” score.
Use a small acceptance record:
| Check | Accept when | Reject when |
|---|---|---|
| Required text | Every letter matches the brief | A word looks close but is misspelled |
| Object placement | The stated left/right relationship holds | Better styling hides the same layout error |
| Unchanged essentials | The product and useful framing remain suitable | The correction introduces a new major defect |
| Delivery format | The output fits the intended placement | A required crop removes important content |
Leave the outcome blank until you inspect your own files. Midjourney reports promising tests, but the announcement does not supply a universal success rate. It does not mean that every rerun preserves identity, exact geometry or all details outside the problem area.
Choose a rerun, an edit or a clearer prompt
Use the thinking rerun when the existing prompt already states the requirement well. If the prompt contradicts itself, first fix the wording. A model cannot resolve a brief that asks for a centered object and empty space in that same location without making a choice for you.
For a small local change in an otherwise approved frame, consider an editing workflow instead. State the region and intended change, then inspect the untouched areas. Our lightbox editing guide covers that kind of comparison. Thinking Mode and targeted editing answer different questions; neither removes the need to review the output.
Do not change the prompt, style references and several parameters while judging a thinking rerun. You may get a useful picture, but you will no longer know which change mattered. When you need a new creative direction, start a separate exploration rather than treating it as a clean test of one control.
Stop when the result meets the task
Decide the stopping rule before you keep generating. For a draft concept, a readable label and correct layout may be enough. For a final product image, exact markings or geometry may need further work outside the generator. Name those requirements instead of chasing a result that is merely more dramatic.
Save the chosen version with one sentence explaining why it won. For example: “The card is readable and the lamp remains left of the notebook; the base still needs manual cleanup.” That note preserves both the improvement and the remaining limitation. It is more useful to the next person than calling the image perfect.
In short, treat Thinking Mode as another route to a specific correction. Keep your brief small, compare the full frame, and keep the original until you have checked the new result. The control is useful only when it helps you make a clearer decision.
Read the Thinking Mode announcement and October 7 Alpha changelog for the release context. For a wider prompt review process, see our prompt fundamentals guide.