Active sessions can be lost after a hard power-off before they appear in session list

[Bilalmd01]

Description

I lost several active OpenCode sessions after my laptop froze and I had to perform a hard power-off.

After rebooting:

• opencode session list did not show any of the active sessions.
• The conversations appear to be unrecoverable.

This seems like OpenCode may not be persisting session state frequently enough, causing complete loss of active conversations after an unexpected shutdown.

The missing sessions are not present in the session table, and there are no corresponding rows in the message or session_message tables.

The database itself appears healthy.

The log only contains process startup messages for the lost instances and never logs a session.id, suggesting the sessions may never have been committed before the crash.

Plugins

No response

OpenCode version

1.17.13

Steps to reproduce

1. Start an OpenCode session with opencode:

2. Work in the sessions for a while.

3. Simulate an unexpected shutdown (kernel panic / hard power-off).

4. Reboot.

5. Run:

   opencode session list

Screenshot and/or share link

No response

Operating System

Ubuntu 24.04.4 LTS

Terminal

Bash

[github-actions]

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

• [FEATURE]:[Feature Request] Native background session autosaver / crash recovery mechanism #32713: Feature request for native crash recovery/autosaver that describes the same root problem — sessions lost after abrupt shutdown (power failure, terminal kill) before SQLite is flushed
• Session conversation history lost after restart on Windows 11 (Atlas) — terminal TUI #33277: Session conversation history lost after restart (similar symptom of sessions not appearing after reboot)
• Windows Desktop: Session data tidak persist antar restart (session processor Aborted) #28449: Session data not persisting across restarts on Windows Desktop (same symptom, different platform)

If your issue is specifically about the SQLite write not being committed before shutdown (i.e., a durability/WAL flush issue), it may be a distinct bug worth keeping open. Otherwise, consider adding a "+1" or additional context to one of the existing issues above.