[Feature Request] Use ArrowUp/ArrowDown to recall sent messages in the composer

[evepupil]

Motivation

In Codeg 0.30.7, when the message composer is focused, pressing ArrowUp does not put the latest sent prompt back into the input. This makes iterative prompts slower.

Expected behavior

• ArrowUp recalls the latest sent message; repeated presses move to older messages.
• ArrowDown moves forward and restores the draft at the newest entry.
• Multiline messages keep normal caret movement until the first/last line boundary.
• CJK IME 候选导航和 / 命令补全保持正常。

Related: #7 (closed, unmerged PR).

Environment

• Codeg 0.30.7
• Windows

[dawNotPoi]

Before picking this up, one scoping question.

The same behavior was attempted in #7 (closed unmerged). Its review listed four things a workable version must get right: never intercept Arrow keys during IME composition, only navigate when the caret sits at the first/last document boundary, stash and restore the in-progress draft, and define what happens when a recalled entry is edited. All four were treated as fixable — the review said the core logic was right — so I read this as a design question rather than a rejected feature.

The composer is now a shared Tiptap rich-text editor (chat, task and automation surfaces), so I would scope any history state to the chat composer only and leave Arrow behavior in the task/automation editors untouched.

Could you confirm which shape you would want, if any?

1. Recall only the single most recent sent prompt (closer to Slack/Discord, much lower interaction risk), or
2. Full multi-entry Up/Down cycling (Codex/terminal-style).

If Arrow-based history is not something you want in a chat-style composer, that is a fine answer too — I will leave #744 alone.

[evepupil]

I'd prefer option 2: full Up/Down history cycling in the chat composer, like Codex and Claude Code. After sending a message, Up should put the latest sent prompt back into the input so I can edit and resend it. Repeated Up should visit older prompts; Down should move forward and restore my unsent draft at the end. Please keep CJK IME, multiline caret movement, and slash-command navigation working normally.

[dawNotPoi]

Thanks @evepupil — option 2 then. Your list matches what I would cover: IME-safe Arrow handling, caret-boundary gating for multiline, draft stash/restore, and defined behaviour when a recalled entry is edited.

@xintaofei before I open a PR, could I get the maintainer's confirmation on scope? This changes composer interaction, and the previous attempt (#7) was closed unmerged, so I would rather agree on shape first:

1. Is full Up/Down history cycling in the chat composer only acceptable, leaving the task and automation composers on default Arrow behaviour?
2. Do the constraints from the feat(chat): arrow-key send history in MessageInput #7 review still stand — never intercept Arrow keys during IME composition; only navigate when the caret is at the first/last document boundary; stash and restore the in-progress draft; define what happens when a recalled entry is edited?
3. Any preference on persistence: session-only history, or persisted across restarts?

Happy to be assigned #744 if you want it tracked. If Arrow-based history is not something you want in a chat-style composer, that is a fine answer too and I will leave the issue alone.

[xintaofei]

@dawNotPoi @evepupil
Thank you for the follow-up discussion on this issue; here are some of my thoughts:

1. The up and down arrow keys cycle through user messages from the current session; this does not apply to new sessions.
2. Message scrolling is triggered only when pressing the up or down arrow keys while the cursor is at the first or last line of the input.
3. Content previously entered in the input box can be restored by scrolling back down after having scrolled up to view other user messages.

Please feel free to reach out if there are any further questions.

[dawNotPoi]

Implemented in #756: ArrowUp/ArrowDown cycle the session's sent prompts, with the caret landing on the edge it travelled from. Behaviour summary is in the PR.