Repository navigation
[FEATURE]: Desktop Session Management Crisis — Restore Delete & Fork actions and unblock stalled PR #11684 #41265
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Summary
The Desktop app (and to a lesser extent the TUI) is in a session management crisis: there is no way to delete a session from the UI, the fork action was deliberately removed over a year ago and never restored, and a working PR that adds a /delete command (#11684) has been sitting unreviewed for 6 months.
This is the single biggest UX gap for anyone who uses OpenCode Desktop daily. Sessions accumulate endlessly with no cleanup affordance, and the only workaround is the CLI (opencode session delete <id>).
Related Issues (all pointing to the same gap)
The problem has been reported multiple times in fragmented issues:
| Issue | Description | Status |
|---|---|---|
| #40786 | Home page session list has no delete/archive entry point | Open |
| #38820 | Right-click to delete sessions on desktop | Open |
| #33129 | Add delete button for sessions in sidebar | Open |
| #37277 | Restore a direct archive action for sessions | Open |
The Fork Button Was Removed and Never Restored
- The fork button was originally added in
fbd9b7cf4(PR feat(app): restore to message and fork session #17092) - It was removed in
311ba4179with the message "fix(app): remove fork session button" as a workaround for a crash ([DESKTOP/WebUI] Forking not possible #18250: "Platform context must be used within a context provider") - It was never restored, despite the crash being platform-specific
- Issue [FEATURE]: Restore fork button on user messages in web/desktop UI #22205 requesting restoration was closed as "not planned"
- A new feature request for Desktop fork button ([FEATURE]: Add "Fork to new session" action from message timeline in OpenCode Desktop #25582) recently auto-closed due to inactivity
Stalled PR: /delete Command (#11684)
- PR feat(tui): add session delete command with confirmation dialog #11684 by @frouo implements a
/deleteslash command with confirmation dialog - It was opened February 1, 2026 — over 6 months ago
- It has zero reviews from maintainers
- Multiple users in the comments are asking for it to be merged
- Meanwhile, the community is resorting to writing external scripts and tools to delete sessions
Technical Evidence
From #40786 (analysis of the app bundle v1.18.14):
HomeSessionRowhas noonContextMenuhandler — right-click does nothing- The archive button is gated behind
SHOW_HOME_SESSION_ARCHIVE = false— a hardcoded constant, so it's never rendered - The delete dialog only exists inside an open session's timeline header menu, requiring users to open a session before they can delete it
Proposed Solutions
- Merge PR feat(tui): add session delete command with confirmation dialog #11684 — at minimum, unblock the
/deletecommand for TUI users who prefer keyboard-driven workflows - Add a delete button to the Desktop Home page session list — either as a hover button, a right-click context menu, or a three-dot menu on each session row
- Restore the fork button — the original crash ([DESKTOP/WebUI] Forking not possible #18250) was a platform context issue that should be investigated properly rather than removing the feature entirely
- Consolidate the fragmented requests — there are now 4+ open issues asking for the same thing; a coordinated response would help the community
Impact
As a daily Desktop user, my session list grows indefinitely with no way to clean it from the UI. The only option is to open a terminal and run opencode session delete <id> — which feels like a developer alpha tool, not a v1.18 product. For users who are less comfortable with CLI, sessions are effectively permanent.
This issue was filed after researching #40786, #38820, #33129, #37277, #22205, #25582, #11684, and the commit history. It consolidates multiple fragmented requests into one actionable report.
Activity
github-actions commentedon Aug 8, 2026
This issue might be a duplicate of existing issues. Please check:
Since this issue intentionally consolidates those requests, maintainers may want to close the individual issues in favor of this one, or vice versa.
mausch commentedon Oct 3, 2026
STOP CLOSING these issues as duplicate / obsolete / old automatically.
There are now countless people having created an issue about this and even submitted PRs and they all get automatically closed.
Is anyone actually managing this project any more?