Skip to content

Queued message interrupts todolist execution #5135

Closed

Description

@tinmarr

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

Activity

  1. added
    opentuiThis relates to changes in v1.0, now that opencode uses opentui
    on Dec 5, 2025
  2. github-actions commented on Dec 5, 2025

    @github-actions
    Contributor

    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.

  3. rekram1-node commented on Dec 5, 2025

    @rekram1-node
    Contributor

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

  4. removed
    bugSomething isn't working
    opentuiThis relates to changes in v1.0, now that opencode uses opentui
    on Dec 5, 2025
  5. self-assigned this
    on Dec 5, 2025
  6. tinmarr commented on Dec 5, 2025

    @tinmarr
    Author

    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.

  7. alto4truth commented on Dec 7, 2025

    @alto4truth

    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)

  8. tinmarr commented on Dec 8, 2025

    @tinmarr
    Author

    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 up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions