Skip to content

minor fix : /undo after a agent did some task does undo the work of that agent but doesnt removes the agents tab ( still can access with ctrl + left /right arrow) #2612

Closed

Description

@aptdnfapt

/undo after an agent did some task does undo the work of that agent but doesn't remove the agent's tab (still can access with Ctrl + left/right arrow).
To test this in OpenCode, tell the main agent to spawn a sub‑agent to make a random comment. (During this time you can see what the agent is doing using Ctrl + left/right arrow.)
Then when the agent is done, type /undo and the edit of that agent will be gone, which is expected, but then if you press Ctrl + left/right arrow, it will still show that chat. This is not intended, right?

Activity

  1. github-actions commented on Sep 15, 2025

    @github-actions
    Contributor

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

    Feel free to ignore if none of these address your specific case.

  2. rekram1-node commented on Sep 15, 2025

    @rekram1-node
    Collaborator

    seems like that shouldn't be intended

  3. OpeOginni commented on Sep 15, 2025

    @OpeOginni
    Contributor

    Im Taking a look at this issue and noticed 2 things.

    • The same issue comes up when checking session timelines, you can see messages that were reverted, is this also intended? if not I have already made a fix for it.
    • The child sessions are only given the parent session ID, idealy we can add a parent message ID as well, so before navigating using the keybindings it checks if the parent message was reverted and if so its not going to be navigated to.
      • Also cleaning of the reverted message will clear the child session as well.

    What do you think @rekram1-node?

  4. OpeOginni commented on Sep 15, 2025

    @OpeOginni
    Contributor

    Tested this solution and it works well, happy it handles deleting of child sessions when the trigger message was "COMPLETELY" reverted without way of coming back. But then again might not be what should be intended.

    Update or feedback on this is welcomed, and apologies if I went a bit much with the changes (touching schema), couldn't wait for confirmation before working on a solution 😅

  5. rekram1-node commented on Sep 15, 2025

    @rekram1-node
    Collaborator

    @adamdotdevin what is the expected UX here?

  6. rekram1-node commented on Dec 28, 2025

    @rekram1-node
    Collaborator

    [automated] Closing due to 90+ days of inactivity. Feel free to reopen if you still need this!

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