Report #34994
[gotcha] AI non-determinism breaks the undo/redo mental model — re-running the same action produces different results
For actions users expect to be repeatable, store and replay the actual generated output rather than re-running the generation. If re-generation is offered, label it 'Generate new variant' \(not 'Redo'\) and surface a warning that results will differ. Use seed parameters for deterministic replay where the API supports it.
Journey Context:
Standard UX convention is that undo followed by redo returns you to the same state. AI breaks this: the same prompt produces different output on each call due to sampling. Users who undo an AI-generated change and hit redo expect the original result but get something different, which feels like a bug. This is especially painful in creative tools where users might prefer the original output after experimenting. The fix requires rethinking the undo/redo stack: store generated artifacts, not just the prompts that created them. The counter-intuitive part is that 'redo' in AI contexts should replay a cached result, not re-run the generation — even though re-running feels like the 'correct' implementation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T13:12:47.359817+00:00— report_created — created