[PR #13522] feat: Restore queued messages into textarea #14700

Open
opened 2026-02-16 18:19:28 -05:00 by yindo · 0 comments
Owner

Original Pull Request: https://github.com/anomalyco/opencode/pull/13522

State: open
Merged: No


What does this PR do?

Fixes #13520
When a tool call is rejected, put the queued message(s) back in the text input

If you paste a large clearly AI generated description here your PR may be IGNORED or CLOSED!

How did you verify your code works?

I tried to out manually and recorded a video:

https://github.com/user-attachments/assets/b521540a-94fa-4b24-bb2a-9885af1503c9

https://github.com/user-attachments/assets/07354261-67db-4457-b6a4-375d0ad868f0

Ode to the Queued Message

A tool call rejected, cast into the void,
The words you had typed, so cruelly destroyed.
You'd queued up your thoughts while the agent was spinning,
Then poof — they were gone. Not a glorious beginning.

Someone looked on at this sorrowful fate,
Where messages vanished behind a locked gate.
"This simply won't do," they declared with conviction,
"We'll restore every word — no more silent eviction."

In prompt.ts they wrote, fifty-seven lines new,
A net to catch messages falling right through.
The prompt input learned a compassionate art:
When rejection strikes down, give the words back their start.

The TUI component got patched up as well,
The event types aligned, and the processor fell
In line with the fix — just a single line each —
To bring lost keystrokes back within the user's reach.

Two videos recorded, the proof plain to see:
What once disappeared now returns, flowing free.
So type while you wait, queue your thoughts without dread —
PR thirteen-five-twenty-two catches what's said.

**Original Pull Request:** https://github.com/anomalyco/opencode/pull/13522 **State:** open **Merged:** No --- ### What does this PR do? Fixes #13520 When a tool call is rejected, put the queued message(s) back in the text input **If you paste a large clearly AI generated description here your PR may be IGNORED or CLOSED!** ### How did you verify your code works? I tried to out manually and recorded a video: https://github.com/user-attachments/assets/b521540a-94fa-4b24-bb2a-9885af1503c9 https://github.com/user-attachments/assets/07354261-67db-4457-b6a4-375d0ad868f0 ### Ode to the Queued Message > > > A tool call rejected, cast into the void, > The words you had typed, so cruelly destroyed. > You'd queued up your thoughts while the agent was spinning, > Then poof — they were gone. Not a glorious beginning. > > Someone looked on at this sorrowful fate, > Where messages vanished behind a locked gate. > "This simply won't do," they declared with conviction, > "We'll restore every word — no more silent eviction." > > In prompt.ts they wrote, fifty-seven lines new, > A net to catch messages falling right through. > The prompt input learned a compassionate art: > When rejection strikes down, give the words back their start. > > The TUI component got patched up as well, > The event types aligned, and the processor fell > In line with the fix — just a single line each — > To bring lost keystrokes back within the user's reach. > > Two videos recorded, the proof plain to see: > What once disappeared now returns, flowing free. > So type while you wait, queue your thoughts without dread — > PR thirteen-five-twenty-two catches what's said. >
yindo added the pull-request label 2026-02-16 18:19:28 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#14700