Repository navigation
Multi-pane/window setup Fails (1.4.0 - SqliteError) #21443
Description
Description
The first OpenCode launch actually succeeds,but opening a new pane/window(shft+alt++) in Windows10-Ubuntu-Wsl-WindowsTerminal results in SqliteError-
(Note -Linux Bash is too slow and is not usable )
SqliteError-
PS Microsoft.PowerShell.Core\FileSystem::\\wsl.localhost\Ubuntu-24.04> wsl
ubuntu_0@DESKTOP-123:~$ opencode
Error: Unexpected error, check log file at /home/ubuntu_0/.local/share/opencode/log/2026-04-08T040527.log for more details
Failed to run the query 'PRAGMA journal_mode = WAL'
---> Inorder to resolve this issue - "Cleared Sqlite.db and log files in \wsl.localhost\Ubuntu-24.04\home\ubuntu_0.local\share",
but the error still persists.
---------------------------------||| Analysis |||----------------------------------
--->For analysis,attached opencode directory.zip after a new attempt at multi-pane/window execution.
The first OpenCode launch actually succeeds:
service=db path=/home/ubuntu_0/.local/share/opencode/opencode.db opening database
service=db count=10 mode=bundled applying migrations
It fully opens the DB and even starts TUI plugins.
A few seconds later second log starts:
2026-04-08T03:53:59 creating instance
and then stops abruptly.
That strongly indicates the second pane is trying to open the same SQLite WAL database while the first OpenCode session is still active.
OpenCode 1.4.0 currently does not reliably support multiple concurrent instances sharing the same DB path.
So the second pane crashes during:
PRAGMA journal_mode = WAL
because the first pane already owns the WAL shared memory region.
This perfectly matches “second pane fails” behavior.
Plugins
No response
OpenCode version
1.4.0.
Steps to reproduce
Screenshot and/or share link
No response
Operating System
Windows 10 -Wsl - Ububtu 24.04
Terminal
Windows Terminal
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Apr 8, 2026
This issue might be a duplicate of existing issues. Please check:
If your issue is the same, please consider adding your details there instead.
github-actions commentedon Jul 3, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.