What happened
When a user submits a follow-up while a turn is already running and chooses adjust direction immediately (steer), the follow-up is accepted and applied to the active turn. However, after the task finishes, the same follow-up still remains in the pending-message card above the composer, with Edit and Delete actions.
This leaves the UI showing the message as though it were still queued even though it has already been consumed. In the observed case, the follow-up asked Maka to comment take on a newly created issue. The comment was successfully posted and the final response confirmed it, but the follow-up card continued to display the same message.
Expected: once an immediate-direction adjustment has been accepted/consumed, its pending-message card should be cleared. After the task completes, no stale follow-up should remain above the composer.
How to reproduce
- Open a session in Maka Desktop.
- Submit a task that runs long enough to add another message while it is executing.
- While the task is running, submit a follow-up message.
- Choose adjust direction immediately rather than waiting for the current task to finish.
- Let the task consume the follow-up and finish.
- Confirm that the follow-up took effect and appears as accepted in the conversation/result.
- Observe that the same follow-up still remains in the pending-message card above the composer.
Environment
- Maka commit:
6fca2f51e
- OS and version: macOS 15.6
- Surface: Desktop
- Node.js version, if running from source: v24.19.0
Logs, screenshots, or additional context
The stale card displays the consumed follow-up with Edit and Delete controls after the final response has already confirmed that the requested action succeeded. This may incorrectly suggest that the message is still waiting to be sent.
Generated with assistance from Maka.
What happened
When a user submits a follow-up while a turn is already running and chooses adjust direction immediately (steer), the follow-up is accepted and applied to the active turn. However, after the task finishes, the same follow-up still remains in the pending-message card above the composer, with Edit and Delete actions.
This leaves the UI showing the message as though it were still queued even though it has already been consumed. In the observed case, the follow-up asked Maka to comment
takeon a newly created issue. The comment was successfully posted and the final response confirmed it, but the follow-up card continued to display the same message.Expected: once an immediate-direction adjustment has been accepted/consumed, its pending-message card should be cleared. After the task completes, no stale follow-up should remain above the composer.
How to reproduce
Environment
6fca2f51eLogs, screenshots, or additional context
The stale card displays the consumed follow-up with Edit and Delete controls after the final response has already confirmed that the requested action succeeded. This may incorrectly suggest that the message is still waiting to be sent.
Generated with assistance from Maka.