[Bug]: v0.15.0 Tauri on Windows cannot create new sessions - reverting to v0.14.0 fixes it

[dayesann]

App Variant

Tauri

Operating System & Version

windows 11

Issue Summary

After upgrading to v0.15.0, the Tauri app cannot create new sessions. Clicking "New Session" does nothing - no error, no loading indicator, no session created. Reverting to v0.14.0-dev-20260427-0ba13713 immediately fixes the issue.

Steps to Reproduce

App Variant

Tauri

Operating System & Version

Windows 11

Issue Summary

After upgrading to v0.15.0, the Tauri app cannot create new sessions. Clicking "New Session" does nothing - no error, no loading indicator, no session created. Reverting to v0.14.0-dev-20260427-0ba13713 immediately fixes the issue.

Steps to Reproduce

1. Install CodeNomad v0.15.0 Tauri (codenomad-tauri.exe) on Windows 11
2. Launch the app
3. Open a Git project folder
4. Click to create a new session
5. Result: Nothing happens. No session is created, no error message appears.

Expected Behavior

A new session should be created and the OpenCode agent should start responding.

Actual Behavior

• No visible response when clicking "New Session"
• No error messages in the UI
• ~/.config/codenomad/instances/ directory remains empty
• OpenCode process never spawns

Environment

• CodeNomad: v0.15.0 (codenomad-tauri.exe)
• OpenCode CLI: v1.14.40 (installed via npm, available in PATH)
• Node.js: Managed Node v22.22.2 (bundled at ~/.config/codenomad/node/v22.22.2/win32-x64/node.exe)
• OS: Windows 11

Root Cause Analysis

After investigating the source code and comparing v0.15.0 with v0.14.0, I identified several potential regressions:

1. Managed Node.js changes (PR Don't depend on Node anymore #346, fix(desktop): show explicit missing Node errors #336): v0.15.0 removed the external Node dependency and introduced managed Node.js. On Windows, the spawn spec for .exe files may not handle paths correctly, especially if the managed Node binary path contains spaces or special characters.

2. OPENCODE_CONFIG_DIR isolation (Issue [Bug] Fail to Load Agent Properly When Opening #384): The bundled opencode-config template at resources/server/dist/opencode-config is used instead of user config. In v0.15.0, this directory structure may have changed (now at dist/opencode-config instead of a separate directory), potentially causing config loading failures.

3. Workspace spawn spec (spawn.ts): The buildWindowsSpawnSpec function handles .cmd/.bat wrapping but .exe files (like the managed node.exe) may not receive proper argument escaping on Windows.

4. No error feedback: When the OpenCode process fails to spawn, the workspace.error event is published but the UI does not surface it, leaving users with no indication of what went wrong.

Workaround

Downgrade to v0.14.0-dev-20260427-0ba13713 or use Server mode:

Expected Behavior

Related Issues

• [Bug]:Cannot create new session with Code Nomad #392 - Same symptom (Tauri on Windows, "Nothing happens")
• [Bug] Fail to Load Agent Properly When Opening #384 - OPENCODE_CONFIG_DIR isolation issue
• [Bug]: Version 0.15.0 wants to install node, and it can't read existing sessions #390 - v0.15.0 session reading issues

Logs

The instances directory at C:\Users\yunlight\.config\codenomad\instances\ is empty, confirming no sessions were ever created. The server's opencode-config directory exists at C:\Users\yunlight\AppData\Local\CodeNomad\resources\server\dist\opencode-config\ with proper contents.

---

Confirmation: This is definitely a v0.15.0 regression. The exact same environment works perfectly with v0.14.0.

Logs & Screenshots

No response

Additional Context

No response

[shantur]

Hey @dayesann,

Thanks for using CodeNomad and creating an issue.
Would you be able to try the build here - https://github.com/NeuralNomadsAI/CodeNomad/releases/tag/v0.15.0-dev-20260505-ecfbc9e5 and see if it works