AI 2026: The Lack of Cmd+Z, a Major Obstacle
Le brief IA que les pros lisent chaque soir
Les 7 actus IA du jour, décryptées en 5 min. Gratuit.
Inclus dès l'inscription : notre sélection des meilleurs guides & comparatifs IA.
Choisis ton rythme
Gratuit · Pas de spam · Désabonnement en 1 clic
The Absence of Undo in Modern AI Products
In the technological landscape of 2026, artificial intelligence products such as ChatGPT, Claude, and Gemini stand out for a notable absence: the undo function. While the command Cmd+Z has become a universal standard in software since the 1980s, current AI tools have not integrated this essential feature.
The Legacy of Cmd+Z
The undo function originated in the 1970s at Xerox PARC, thanks to Larry Tesler and Tim Mott's Gypsy editor. This concept was institutionalized in 1987 with the Apple Human Interface Guidelines, which made Cmd+Z a central element of the user experience on Mac. This functionality has become an invisible infrastructure, allowing users to easily revert their actions.
Undo did not arrive in a fully developed form. Its origins trace back to Xerox PARC in the 1970s, with Larry Tesler and Tim Mott's Gypsy editor, the first text editor without modes. Mode-less editing made undo possible because it allowed the system to maintain a single history of user actions, rather than separate histories by mode.
In 1987, the Apple Human Interface Guidelines codified Edit > Undo as a fundamental element of the system. Every Mac application that opened a window inherited a Cmd+Z shortcut and an Edit menu item that meant the same thing: undo the last action.
The Limitations of AI Without Undo
Today, attempting to undo an action in tools like ChatGPT or Gemini using Cmd+Z yields no results. Users can only refresh the page, thus losing their work, or use the regeneration function, which merely replaces the existing content without going back.
Open ChatGPT, Claude, or Gemini today. Generate a paragraph. Press Cmd+Z. Nothing happens.
You can refresh the page and lose the entire generation. You can hit Regenerate and replace the generation with another, which is the closest thing to "going back" that the product offers, but is actually a forward operation, not a backward one.
Undo means: I performed an action a moment ago, and I want to take it back; it should only cost me a single keystroke, and I want the system to be in the state it was before I acted. AI products have nothing that satisfies all four of these properties at once.
User Strategies in Response to This Gap
In the absence of an undo function, users are adopting workarounds. The more savvy users systematically copy the AI-generated text to the clipboard, while others prefer to take screenshots to keep a visual record of their interactions.
I co-founded browser extensions that sit alongside ChatGPT, Claude, and Gemini. I have read every user review of these tools. Two specific behaviors recur among thousands of users:
-
The first is the reflex Cmd+A → Cmd+C. Advanced users select all and copy the AI's output to the clipboard before doing anything else, every time. They have learned that the next click could be destructive and that the keyboard shortcut they learned will not save them.
-
The second is the screenshot reflex. Less technical users take a screenshot of the AI's response before typing the next message, as they do not trust that the response will still be there if something goes wrong. The clipboard is too abstract. Pixels are not.
Branching: An Imperfect Solution
In response to this issue, companies have introduced branching functions. OpenAI, for example, allows users to split a conversation into a new thread via a menu option. Anthropic and Google have also implemented similar solutions. However, these options are cumbersome and require complex navigation, far from the simplicity of a single Cmd+Z keystroke.
The industry's response in 2025 and 2026 has been branching, not undo. OpenAI shipped a branching function in the new chat: hover over a message, click on More actions, and split the conversation into a new thread. Anthropic shipped editing for branching in Claude's web app and added a /branch command as well as secondary discussions in Claude Code. Google shipped prompt editing branching in Gemini. All three call this their "go back" function.
Branching is heavy, deliberate, and requires navigation. It demands that the user knows that branching exists, finds the interface element, makes a decision about preserving the parent, and then switches from one thread to another. Cmd+Z is none of that. Cmd+Z is a single keystroke at the syntactical level of the output, with no navigation cost.
Imagining an Effective Undo for AI
For an undo function to be effective in AI products, it should allow for reversibility at the output level and be accessible with a single keystroke. This would ensure a smooth and intuitive user experience, in line with Norman's design principles for error and Nielsen's heuristic.
If a designer working on ChatGPT, Claude, or Gemini were to sit down today to design undo, four properties would be essential. They derive directly from Norman's design principle for error and Nielsen's heuristic #3.
-
The first is reversibility at the output level, not just at the conversation level. If a user generates a paragraph, edits two sentences, and hits Regenerate, undo should restore the previous paragraph as a recoverable state, not just the last turn.
-
The second is ambient access with a single keystroke. No menus, no hover states, no chevrons. Cmd+Z and Cmd+Shift+Z on every surface, including read-only views of generations.
Brief IA — L'actualité IA en français
L'essentiel de l'actualité de l'intelligence artificielle, décrypté et expliqué chaque jour.