Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Cowork (Windows): arrow-up at top line of input loads prior chat message and hijacks the textarea [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#53107•Fetched 2026-04-25 06:12:11
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Author
iamGTBiamGTB
Participants
github-actions[bot]github-actions[bot]iamGTBiamGTB
Timeline (top)
labeled ×4closed ×1commented ×1cross-referenced ×1

Error Message

Error Messages/Logs

Code Example

None. Failure is silent and visible only in the textarea content.
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

In the Cowork tab of the Claude desktop app on Windows 11, when the typing cursor is on the top line of the input textarea and the user presses arrow-up, the textarea replaces the current draft with the user's previous chat message in the session. Arrow-down restores the current draft. Holding arrow-up iterates back through prior user messages in reverse-chronological order.

Critical secondary failure: while a prior message is loaded into the textarea, typing edits that prior message rather than the current draft, and pressing Enter sends the typed-into-prior-message version. The user can unintentionally edit and re-send a prior message when they only meant to scroll their current draft to the top.

There is no visible indicator that the textarea has been hijacked into a prior-message-edit mode. No setting in Cowork preferences disables this behavior.

What Should Happen?

Arrow-up at the top line of the textarea should either (a) do nothing -- the cursor stays at the top of the current draft -- or (b) provide a clearly-indicated history-recall mode that is opt-in, distinguishable from the current-draft state, and cannot accidentally edit/send a prior message via subsequent typing. The terminal-style up-arrow-recalls-history pattern is a poor fit for a multi-line textarea where the user routinely needs to navigate within their draft.

Error Messages/Logs

None. Failure is silent and visible only in the textarea content.

Steps to Reproduce

  1. Open Cowork tab in Claude desktop app on Windows 11.
  2. In a session with at least one prior user message, draft a multi-line message in the input textarea.
  3. Place cursor on the top line of the textarea.
  4. Press arrow-up.
  5. Observe: the prior chat message replaces the current draft.
  6. Type any character.
  7. Observe: typing edits the loaded prior message, not the current draft.

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

A week ago this behavior didn't exist.

Claude Code Version

2.1.111 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Non-interactive/CI environment

Additional Information

Practical impact

Holding arrow-up to navigate to the top of a long draft (a routine textarea operation) scrolls the chat history instead, often by many messages. Subsequent typing then corrupts a prior prompt. Recovery requires arrow-down to restore the current draft, but the recovery path is not obvious from the UI and the focus cost is meaningful.

extent analysis

TL;DR

The issue can be mitigated by modifying the textarea behavior to prevent it from replacing the current draft with prior chat messages when the arrow-up key is pressed.

Guidance

  • Investigate the event handler for the arrow-up key press in the textarea to determine why it's replacing the current draft with prior chat messages.
  • Consider adding a check to prevent the textarea from loading prior messages when the cursor is at the top line, or provide a clear indicator when the textarea is in "history-recall mode".
  • Review the code changes made in the last week to identify the regression causing this behavior.
  • Test potential fixes by reproducing the issue and verifying that the textarea behaves as expected when the arrow-up key is pressed.

Example

No code snippet is provided as the issue does not include specific code details.

Notes

The issue is specific to the Cowork tab in the Claude desktop app on Windows 11, and the fix may need to account for the terminal-style up-arrow-recalls-history pattern not being suitable for a multi-line textarea.

Recommendation

Apply a workaround to modify the textarea behavior, as the root cause of the regression is likely due to a recent code change and upgrading to a fixed version is not currently an option.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#dependency conflict#environment setup#docker error#permission error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Cowork (Windows): arrow-up at top line of input loads prior chat message and hijacks the textarea [1 comments, 2 participants]