Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Native chat composer: Up/Down arrow recall of sent messages

Open Beginner friendly
  • Is something wrong?
#1,762 1 comment 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
csharp
Domain
desktop

Research direction

Start with src/OpenClaw.Tray.WinUI/Chat/ReactorChatComposer.cs and read how VirtualKey.Up and VirtualKey.Down currently handle the slash-command popup. Add sent-message recall with the described empty-draft and popup-priority behavior; verify in the native composer that Up recalls messages, Down moves forward to the empty draft, and the popup still takes priority.

Written by the indexing model from the issue text.

Description

clawsweeper:needs-maintainer-review clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster P3

What: In the native chat composer, pressing Up arrow on an empty box should recall the previous sent message, and Down should step forward again (like a shell, and like the gateway's web chat).

Why: Re-sending or tweaking a recent message currently means retyping or copying it. The gateway's web chat (the "Use gateway's web chat interface" / UseLegacyWebChat path) already has this, so anyone who relies on it has to keep the legacy switch on. If that switch is ever removed, the native composer needs this too.

Where: src/OpenClaw.Tray.WinUI/Chat/ReactorChatComposer.cs. VirtualKey.Up / VirtualKey.Down are handled only for the slash-command popup; there is no sent-message history.

Suggested behaviour: Up on an empty box (or with the caret on the first line) loads the last sent message, repeated Up goes further back, Down moves forward and ends on the empty draft. The popup keeps priority when it is open.

Related: #1674 (Enter sends from the multiline composer) is merged, but as far as I can tell it is only in the prerelease v2026.9.9-alpha.3, not in the 2026.9.8-1 release. Observed on 2026.9.8-1.

Dominant language
C#
Stars
2.2k
Forks
321
Avg merge
4d 14h
Merged PRs (30d)
196

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openclaw/openclaw-windows-node

All issues in openclaw/openclaw-windows-node

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.