opencode-desktop-repair

The usual root cause is a poisoned project row in opencode.db whose worktree points at the deleted directory. Run the fix-project.ps1 script in an external PowerShell after fully quitting OpenCode; it deletes the stale project row and its child records while keeping the clean project intact.

This happens when opencode.global.dat contains a UTF-8 BOM, usually from a prior edit with Set-Content -Encoding UTF8 on PowerShell 5.1. The app cannot parse the file, shows an empty project list, and refuses to persist changes. Run fix-global-bom.ps1 to rewrite the file without a BOM.

Corrupt session rows with non-UTF8 directory values or NULL paths make session.list fail with a 'Path is not absolute' error, causing a silent hang. The fix-sessions.ps1 script removes these corrupt rows plus sessions bound to deleted directories.

No. The opencode.db file is WAL-locked while the app runs, so all mutation scripts refuse to execute if an OpenCode process is detected. You can copy the database with shared-read access for read-only diagnosis, but fixes require fully quitting the app first.

The scripts require Windows PowerShell 5.1 and Python 3 on PATH, using Python's built-in sqlite3 module for database access. No additional packages need to be installed, and every script creates a timestamped backup before making changes.