Crash on startup when OPENCODE_CONFIG_DIR points to a non-existent directory

[weiconghe]

Bug Description

OpenCode crashes on startup when OPENCODE_CONFIG_DIR points to a directory that does not exist.

Steps to Reproduce

1. Set Windows user environment variable OPENCODE_CONFIG_DIR to a path (e.g. D:\JavaTool\OpenCode\opencode-skills)
2. Install/update OpenCode Desktop (NSIS installer wipes the install directory during auto-update)
3. Launch OpenCode

Expected Behavior

OpenCode should start normally and create the config directory if it does not exist.

Actual Behavior

The server process crashes with ENOENT: no such file or directory when ensureGitignore tries to write .gitignore into the non-existent OPENCODE_CONFIG_DIR.

Error: ENOENT: no such file or directory, open D:JavaToolOpenCodeopencode-skills.gitignore

Root Cause

In packages/opencode/src/config/config.ts, ensureGitignore uses fs.writeFileString which does not create parent directories. When ConfigPaths.directories() returns a path that does not exist on disk (e.g. after auto-update wipes the install dir), the write fails with ENOENT. The error is fatal because the call site uses Effect.orDie.

Environment

• Windows 11
• OpenCode Desktop (latest, auto-updated)

[github-actions]

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

• OPENCODE_CONFIG_DIR crashes on startup if directory is read-only and missing .gitignore #23040: Same root cause — ensureGitignore crashes on startup when OPENCODE_CONFIG_DIR points to a directory where .gitignore cannot be written. That issue covers a read-only directory; this one covers a non-existent directory. They share the same fix area (ensureGitignore / Effect.orDie).

If your issue is distinct (non-existent directory vs. read-only directory), it may be worth referencing #23040 for context.