[Bug]: Typed composer text is lost when clicking Stop during a pending approval prompt
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 23k
- Forks
- 5.9k
- Avg merge
- 11h 14m
- Merged PRs (30d)
- 357
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are named. Reproduce on the desktop app with a pending multiple-choice prompt, type a free-form response, and click Stop; trace the composer and thread state involved. Done means typed drafts are preserved per thread or are submitted as free-form answers instead of being discarded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, typescript
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100