anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-23 02:36:57 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Queued message interrupts todolist execution #3341

New Issue
Closed
opened 2026-02-16 17:39:42 -05:00 by yindo · 5 comments
yindo commented 2026-02-16 17:39:42 -05:00
Owner
Copy Link
Copy Source

Originally created by @tinmarr on GitHub (Dec 5, 2025).

Originally assigned to: @rekram1-node on GitHub.

Description

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

  1. Start a session and ask it to make a list and then execute on the list
  2. Wait for it to make the list and start on the first point
  3. Send a new message while it's working (message will be queued)
  4. Observe how the agent is interrupted.

Screenshot and/or share link

https://opencode.ai/s/7FJ4YLac

Operating System

Arch Linux

Terminal

Ghostty

Originally created by @tinmarr on GitHub (Dec 5, 2025). Originally assigned to: @rekram1-node on GitHub. ### Description 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 1. Start a session and ask it to make a list and then execute on the list 2. Wait for it to make the list and start on the first point 3. Send a new message while it's working (message will be queued) 4. Observe how the agent is interrupted. ### Screenshot and/or share link https://opencode.ai/s/7FJ4YLac ### Operating System Arch Linux ### Terminal Ghostty
yindo closed this issue 2026-02-16 17:39:42 -05:00
yindo commented 2026-02-16 17:39:42 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Dec 5, 2025):

This issue might be a duplicate of or related to existing issues. Please check:

  • #5122: Proposes context injection at natural breaks during generation (addresses how queued messages should be handled)
  • #4319: Agent gets stuck or encounters exceptions during task execution (similar interruption symptoms)
  • #1734: ESC not working reliably on agent hangs (related to interruption during active execution)
  • #684: Interrupt sometimes has no effect (related reliability of stopping execution when queued messages arrive)

Feel free to ignore if your specific case differs from these.

@github-actions[bot] commented on GitHub (Dec 5, 2025): This issue might be a duplicate of or related to existing issues. Please check: - #5122: Proposes context injection at natural breaks during generation (addresses how queued messages should be handled) - #4319: Agent gets stuck or encounters exceptions during task execution (similar interruption symptoms) - #1734: ESC not working reliably on agent hangs (related to interruption during active execution) - #684: Interrupt sometimes has no effect (related reliability of stopping execution when queued messages arrive) Feel free to ignore if your specific case differs from these.
yindo commented 2026-02-16 17:39:43 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Dec 5, 2025):

How do you used queued messages, because I think there are people who expect the current behavior

@rekram1-node commented on GitHub (Dec 5, 2025): How do you used queued messages, because I think there are people who expect the current behavior
yindo commented 2026-02-16 17:39:43 -05:00
Author
Owner
Copy Link
Copy Source

@tinmarr commented on GitHub (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.

@tinmarr commented on GitHub (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.
yindo commented 2026-02-16 17:39:43 -05:00
Author
Owner
Copy Link
Copy Source

@alto4truth commented on GitHub (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)

@alto4truth commented on GitHub (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)
yindo commented 2026-02-16 17:39:43 -05:00
Author
Owner
Copy Link
Copy Source

@tinmarr commented on GitHub (Dec 7, 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)

@tinmarr commented on GitHub (Dec 7, 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)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#3341
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?