Skip to content

OpenCode 1.2.21 stops working in WSL folders that are symbolic links to Windows paths #16596

@gswelter

Description

@gswelter

Description

I encountered an issue where OpenCode version 1.2.21 fails to respond in chat when running in a WSL folder that is a symbolic link pointing to a Windows path.

Expected behavior:

OpenCode should work in symbolic link folders just as it works in native Linux folders.

Actual behavior:

OpenCode 1.2.21 becomes unresponsive in chat when the working directory is a symbolic link to a Windows path.

Additional notes:

  • Tested in a native Linux folder (not a symlink) - works correctly
  • Downgraded to version 1.2.20 - works correctly in the same symbolic link folder
  • Issue appears to be introduced in version 1.2.21

Plugins

No response

OpenCode version

1.2.21

Steps to reproduce

Environment:

  • WSL (Windows Subsystem for Linux)
  • Working directory: ~/projects/newapp/ → symbolic link to /mnt/c/Users/MyName/OneDrive - Blah/Documents/Projects/newapp

Steps to reproduce:

  1. Create a symbolic link in WSL pointing to a Windows path (e.g., ln -s /mnt/c/Users/... ~/projects/newapp)
  2. Navigate to that folder and start OpenCode
  3. Try to use any agent - no response in chat

Expected behavior:

OpenCode should work in symbolic link folders just as it works in native Linux folders.

Actual behavior:

OpenCode 1.2.21 becomes unresponsive in chat when the working directory is a symbolic link to a Windows path.

Additional notes:

  • Tested in a native Linux folder (not a symlink) - works correctly
  • Downgraded to version 1.2.20 - works correctly in the same symbolic link folder
  • Issue appears to be introduced in version 1.2.21

Screenshot and/or share link

No response

Operating System

Windows 11, WSL

Terminal

No response

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingwindows

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions