[BUG] Archive action causes 4+ hours of session data loss on Windows Desktop #20903

Description

When clicking the "Archive" button in OpenCode Desktop for Windows, all conversation history from the current session that hasn't been persisted to the database is permanently lost. This is a critical data loss bug.

Impact

• Severity: Critical (data loss)
• Affected Users: All Windows Desktop users
• Data Lost: 4+ hours of conversation history (in my case)

Steps to Reproduce

1. Open OpenCode Desktop on Windows 10/11
2. Start a new conversation and chat for several hours
3. Do NOT manually save/export the conversation
4. Click the "Archive" button in the session list
5. The current session disappears from the list
6. All messages from ~17:57 to ~21:40 are permanently lost

Expected Behavior

• Archiving a session should save all pending messages to the database first
• Archived sessions should be recoverable via an "Unarchive" function
• Users should be warned if there are unsaved messages before archiving

Actual Behavior

• Session data in memory is NOT persisted before archiving
• No confirmation dialog warns about unsaved data
• No way to recover the archived session
• Database shows no record of the lost conversation

Technical Evidence

Database Query Results

Queried ~/.local/share/opencode/opencode.db:

SELECT id, slug, title, time_updated FROM session ORDER BY time_updated DESC LIMIT 10;

All sessions were last updated BEFORE 17:00, but I was actively chatting until 21:40.

File System Analysis

Checked ~/.local/share/opencode/storage/session_diff/:

• All session diff files are empty (2 bytes, content: [])
• No session data persisted between 17:57-21:40

Timeline

Root Cause Analysis

Based on source code review and database analysis:

1. Session auto-save mechanism is broken - Messages are not being persisted to the database in real-time
2. Archive action does not trigger a save - Clicking archive should flush pending messages first
3. No warning dialog - Users are not warned about unsaved data before archiving
4. No recovery mechanism - Archived sessions cannot be recovered

Suggested Fixes

Immediate (Critical)

1. Add confirmation dialog before archiving if there are unsaved messages
2. Force save pending messages before executing archive action
3. Add warning toast if archive is attempted with pending data

Long-term

1. Implement proper session persistence - Auto-save messages every N seconds
2. Add unarchive functionality - Allow users to recover archived sessions
3. Add session backup - Create backup before destructive operations

Workarounds (for users)

Until this is fixed, users should:

1. Regularly export conversations using /export command (Ctrl+X X)
2. Avoid clicking "Archive" button until the bug is fixed
3. Use TUI version (opencode command) - community PR feat: add session archive/unarchive support to TUI #13961 adds archive/unarchive support

Related Issues

• [FEATURE]:希望添加「恢复归档会话」的功能，而不是归档就删除了会话。 #15980 - 希望添加「恢复归档会话」的功能
• 误操作点到归档了，如何能回撤这个操作~ #15677 - 误操作点到归档了，如何能回撤这个操作
• 当一个对话被"归档"，要去哪里找回它 #12888 - 当一个对话被"归档"，要去哪里找回它
• [FEATURE]: Unarchive session #16000 - [FEATURE]: Unarchive session

Related PRs

• feat: add session archive/unarchive support to TUI #13961 - feat: add session archive/unarchive support to TUI
• feat(session): add archive undo + unarchive command #16212 - feat(session): add archive undo + unarchive command

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

Windows 11

Terminal

OpenCode Desktop App