[BUG] SQLite Migration Ate My Sessions! 😱 (But Desktop Survived!)

[abbabb123]

Description

After upgrading to v1.2.0+, my CLI shows incomplete sessions while Desktop still sees the full history. It's like CLI is on a diet but Desktop is living its best life!

Steps to Reproduce

1. Have many sessions from daily coding
2. Upgrade to v1.2.0+ (SQLite migration happens)
3. Open CLI - notice some sessions are MISSING
4. Open Desktop - ALL sessions are there!

Evidence

Storage	Sessions	Messages
SQLite (CLI)	~1,350	~45,000
storage/ (old flat files)	20 folders	1,456 files

The old storage folder still contains un-migrated data, but CLI only reads from SQLite.

Expected Behavior

ALL sessions should appear in CLI, not just the ones that survived the SQLite migration!

Actual Behavior

• CLI only shows sessions that made it to SQLite
• Desktop reads from the old storage like a time traveler
• Some sessions exist in storage/ but NOT in SQLite
• The migration gave up halfway through

Environment

• OpenCode version: v1.2.1
• OS: macOS

Workaround

Downgrading to v1.1.x restores access to all sessions.

---

PLZ FIX 🙏

The users who upgraded are crying. The sessions we can't see are crying harder.
Desktop is laughing. We are not.

[github-actions]

Thanks for reporting this! Before we dive in, I wanted to check if this might be related to these existing issues:

• opencode should not run session JSON to sqlite migration when started with opencode serve #13611: SQLite migration issues when using opencode serve
• Bug: TUI doesn't pass directory to tui(), breaking session loading #13600: TUI session loading failures

If your issue is distinct from these, we'll prioritize investigating the partial migration you're experiencing. The evidence table showing un-migrated data in the storage/ folder is particularly helpful for debugging this.

[thdxr]

did you try deleting the sqlite database and letting the migration run again?

[thdxr]

hey pushed some more fixes in 1.2.3 can you delete the sqlite file (can find it with opencode db path) and then run it to rerun the migration?

[lee-b]

hey pushed some more fixes in 1.2.3 can you delete the sqlite file (can find it with opencode db path) and then run it to rerun the migration?

Is the sqlite database only a cache? If not, then deleting the DB doesn't sound like a valid solution to DB migration bugs -- it would apply an initial migration, not the buggy migration in question?

[github-actions]

To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.