Desktop/Web: Missing Revert and Fork actions for messages #6971

Open
opened 2026-02-16 18:05:45 -05:00 by yindo · 2 comments
Owner

Originally created by @bilalbayram on GitHub (Jan 20, 2026).

Originally assigned to: @adamdotdevin on GitHub.

Problem

The desktop/web app is missing the Revert and Fork actions that are available in the CLI TUI. Users cannot:

  • Revert a message (undo messages and file changes)
  • Fork from a message (create a new session branching from that point)

These are essential features for iterating on AI responses.

Proposed Solution

Add message actions to user messages in the desktop/web app, matching CLI functionality:

  • Three-dot menu (on hover) with Revert, Fork, and Copy options
  • Right-click context menu with the same actions

Expected Behavior

  • Hover over a user message → three-dot menu appears
  • Click menu → shows Revert, Fork, Copy options
  • Right-click on message → context menu with same options
  • Revert → removes message and restores prompt text
  • Fork → creates new session and navigates to it
Originally created by @bilalbayram on GitHub (Jan 20, 2026). Originally assigned to: @adamdotdevin on GitHub. ## Problem The desktop/web app is missing the Revert and Fork actions that are available in the CLI TUI. Users cannot: - **Revert** a message (undo messages and file changes) - **Fork** from a message (create a new session branching from that point) These are essential features for iterating on AI responses. ## Proposed Solution Add message actions to user messages in the desktop/web app, matching CLI functionality: - **Three-dot menu** (on hover) with Revert, Fork, and Copy options - **Right-click context menu** with the same actions ## Expected Behavior - Hover over a user message → three-dot menu appears - Click menu → shows Revert, Fork, Copy options - Right-click on message → context menu with same options - Revert → removes message and restores prompt text - Fork → creates new session and navigates to it
yindo added the web label 2026-02-16 18:05:45 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 20, 2026):

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

  • #8885: Ability to fork/revert in desktop app
  • #8689: ability to revert/fork from the ai message, not only from the user's
  • #1789: Feature Request: Add reset or fork tool to let agent reset chat on the previous user message
  • #9660: Desktop: Consolidate message action buttons into single location
  • #5495: Forking a message should retain the input like in /undo
  • #4358: Add "Copy message" option to right-click context menu for user messages
  • #5599: add a /fork command for the convenience of users who prefer to use the keyboard

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

@github-actions[bot] commented on GitHub (Jan 20, 2026): This issue might be a duplicate of existing issues. Please check: - #8885: Ability to fork/revert in desktop app - #8689: ability to revert/fork from the ai message, not only from the user's - #1789: Feature Request: Add reset or fork tool to let agent reset chat on the previous user message - #9660: Desktop: Consolidate message action buttons into single location - #5495: Forking a message should retain the input like in /undo - #4358: Add "Copy message" option to right-click context menu for user messages - #5599: add a /fork command for the convenience of users who prefer to use the keyboard Feel free to ignore if none of these address your specific case.
Author
Owner

@jeremyakers commented on GitHub (Jan 31, 2026):

I see a PR was opened to solve this, but it was closed with no explanation why that I can see: https://github.com/anomalyco/opencode/pull/9665

This seems like a fairly glaring feature parity issue between the UIs?

Personally to me it makes more sense that this should be in the Web UI vs the TUI: Users expect to be able to use the mouse to select a message and click "Undo" on that message when using a graphical UI such as Web or Desktop.

Users generally DON'T expect to use the mouse for the same functionality in a terminal interface.

@jeremyakers commented on GitHub (Jan 31, 2026): I see a PR was opened to solve this, but it was closed with no explanation why that I can see: https://github.com/anomalyco/opencode/pull/9665 This seems like a fairly glaring feature parity issue between the UIs? Personally to me it makes more sense that this should be in the Web UI vs the TUI: Users *expect* to be able to use the mouse to select a message and click "Undo" on that message when using a graphical UI such as Web or Desktop. Users generally *DON'T expect* to use the mouse for the same functionality in a terminal interface.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#6971