[DOCS] Interactive mode docs omit how edits to recalled prompt-history entries behave during further history navigation

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/interactive-mode

Section/Topic

Keyboard shortcuts and Command history

Current Documentation

The page currently says:

| Up/Down arrows or Ctrl+P/Ctrl+N | Move cursor or navigate command history | In multiline input, first moves the cursor within the prompt. Once the cursor is already on the top or bottom edge, pressing again navigates command history |

Later in the same page it says:

Submitting the same prompt twice in a row records one history entry, so pressing Up steps to the previous distinct prompt Use Up/Down arrows to navigate (see keyboard shortcuts above)

And earlier it also says:

| Esc + Esc | Clear input draft, or rewind | When the prompt input contains text, double Esc clears it and saves the draft to history so Up recalls it. When the input is empty, double Esc opens the rewind menu to restore or summarize code and conversation from a previous point |

What's Wrong or Missing?

Changelog v2.1.149 says:

Fixed editing a recalled prompt-history entry losing the edit when navigating further up/down with arrow keys

The interactive-mode docs explain how to recall history entries and how drafts can be saved into history, but they do not document the expected behavior after a user recalls an older prompt and starts editing it.

That leaves a gap in the command-history contract: the page does not say that edits to a recalled history entry should remain attached to that in-progress draft while the user continues moving farther up or back down through history.

Without that guidance, readers cannot tell whether losing their edit is a bug, an intentional overwrite, or a limitation of history navigation.

Suggested Improvement

Add a short note to the Command history section clarifying the expected behavior for edited recalled entries.

For example:

After you press Up to recall a previous prompt, you can edit that recalled text before submitting it. If you keep navigating further up or back down through history, Claude Code preserves your in-progress edit so it is still there when you return to that draft.

It would also help to mention that this applies to both Up/Down and Ctrl+P/Ctrl+N history navigation.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/interactive-mode | Primary command-history documentation for recalling prompts, editing drafts, and using Up/Down navigation |

Total scope: 1 page affected

This behavior was fixed in v2.1.149, so documenting it would make the expected prompt-history workflow explicit for users on current versions.