Checked main at ed9b7ca9c5. No matching duplicate or existing fix PR found in the open backlog. The current composer stores text entered during a multiple-choice request as a question answer, separately from the thread draft; when that request disappears, it switches back to the thread draft and prunes the resolved answer. This is source inspection, not a confirmed runtime reproduction. Started the isolated web dev environment, but stopped during database seeding before exercising the flow. Leaving this open for maintainer review because changing the pending-request answer lifecycle requires approval-related review under the triage rules. macOS desktop and the remote SSH scenario remain unverified.
[Bug]: Typed composer text is lost when clicking Stop during a pending approval prompt#8963
Loving T3 Code, using it daily to drive agents on a second machine. Sharing this one in case it helps.
When the agent asked a multiple-choice question (pick 1/2/3), I didn't want any of the options, so I typed what I actually wanted into the composer. The choice card stayed pending, so I clicked Stop to interrupt, and everything I had typed was discarded. I had to retype the whole message.
Expected: composer drafts survive Stop (persist per thread), or typed text while a choice is pending gets submitted as a free-form answer.
Seen on the desktop app v0.0.37 on macOS, thread running against a remote SSH-launched environment.
Thanks for the great tool.