You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I start a todolist, I would expect the agent to run through the entire list (unless I interrupt it with esc), then process queued message afterwards. However, it doesn't seem to do that. The queued message seems to wait for whatever current generation to stop before interrupting it's task.
In all fairness, you can then ask it to resume the previous list and it seems to be able to start from where it left off, but I could imagine it wouldn't always work for longer running tasks.
OpenCode version
1.0.133
Steps to reproduce
Start a session and ask it to make a list and then execute on the list
Wait for it to make the list and start on the first point
Send a new message while it's working (message will be queued)
TBH, I was expecting the same behavior as OP, and I don't know any workaround alterntive approaches. I think it can be quiet useful for queuing something after you already told AI to fix compilation (usually it succeds, so it can after it work on next feature)
I've found that asking it to "add x todo list then continue where you left off" usually works. (it does interrupt, but with big pickle at least it's able to start up again without issues)
Activity
github-actions commentedon Dec 5, 2025
This issue might be a duplicate of or related to existing issues. Please check:
Feel free to ignore if your specific case differs from these.
rekram1-node commentedon Dec 5, 2025
How do you used queued messages, because I think there are people who expect the current behavior
tinmarr commentedon Dec 5, 2025
I use it to give my thoughts on changes faster. Or to get it to start working on other things once it's done.
Also, for smaller tasks, it seems to perform better with queuing vs 1 big task list (on big pickle).
Definitely don't need to change the behavior (you can work around it once you're aware of it) but it just wasn't very intuitive to me.
Closing since it doesn't seem to be an actual bug.
alto4truth commentedon Dec 7, 2025
TBH, I was expecting the same behavior as OP, and I don't know any workaround alterntive approaches. I think it can be quiet useful for queuing something after you already told AI to fix compilation (usually it succeds, so it can after it work on next feature)
tinmarr commentedon Dec 8, 2025
I've found that asking it to "add x todo list then continue where you left off" usually works. (it does interrupt, but with big pickle at least it's able to start up again without issues)