[Desktop] Can't steer a message and send it as an interrupt
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
In the desktop app, if you steer a message, you can't then send it "as an interrupt" rather than "after the next tool call". There's no button to do so. If you click the stop button, it stops the thread entirely. Then, there's only a "copy" button on the steered message that never actually got submitted. The only path to send it again is sending another silly followup like "^" or "do the above task" or something like that, which seems stupid.
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
Start in the desktop app's handling of steered messages and the stop/interrupt controls; reproduce the issue by steering a message while a tool call is pending and compare the available actions. Done means the steered message can be submitted as an interrupt without stopping the thread, with a usable way to retry it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100