about opencode's vscode extension

[Mathew149]

Description

GitHub Issue for OpenCode

Title

incorrect file reference format "In @" when opening OpenCode from VSCode (Windows)

Issue Description

When opening OpenCode from VSCode extension on Windows, the file reference format in the dialog shows incorrect formatting:

Current behavior:

• Shows: In @Homework/file name
• The "In " prefix is unnecessary
• File path uses forward slash / instead of Windows backslash \

Expected behavior:

• Should show: @Homework\file name
• No "In " prefix
• Use correct Windows path separator \

Environment

• OS: Windows 10/11
• VSCode extension: sst-dev.opencode version 0.0.13
• Extension file: ~/.vscode/extensions/sst-dev.opencode-0.0.13/dist/extension.js

Reproduction Steps

1. Open a file in VSCode on Windows (e.g., a file in Homework folder)
2. Use VSCode keyboard shortcut (Ctrl+Esc) to open OpenCode
3. Observe the text automatically inserted in the OpenCode dialog
4. The text shows: In @Homework/文件

Root Cause Analysis

Found in /dist/extension.js (compressed code):

Issue 1: "In " prefix

// Line around 32 in the compressed code
c&&(await h(t,`In ${r}`),n.show())

Should be:

c&&(await h(t,`${r}`),n.show())

Issue 2: Path separator

// Path generation logic
c=`@${o.workspace.asRelativePath(n.uri)}`

VSCode's asRelativePath() API returns relative paths with OS-specific separators, but on Windows it should convert to backslash \ for consistency with Windows file path conventions.

Possible Fix

Fix 1 - Remove "In " prefix:

In extension.js, change:

await h(t,`In ${r}`)

to:

await h(t,`${r}`)

Fix 2 - Convert path separator for Windows:

Option A: In the VSCode extension, modify the path generation:

c=`@${o.workspace.asRelativePath(n.uri).replace(/\//g, "\\")}`

Option B: Better approach - Handle this in the OpenCode server side to normalize paths regardless of OS:

• Convert all paths to Unix format with / for cross-platform consistency
• Or preserve OS-specific format based on client OS

Additional Context

• The @ syntax for file references is great
• The automatic file context when opening from VSCode is a useful feature
• Only the formatting needs adjustment for better UX on Windows

Alternative

Consider using Unix-style paths (@Homework/file name) universally if the backend handles paths in a platform-agnostic way, which might be simpler than OS-specific formatting.

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

[github-actions]

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

• The issue title is generic ("about opencode's vscode extension") and doesn't describe the actual bug
• The description appears to be AI-generated (structured with multiple headers, root cause analysis, code diffs, and fix proposals — all hallmarks of AI-generated content, which we don't accept)
• Required template fields are left as placeholder text: OpenCode version, Steps to reproduce, Operating System, and Terminal are all "No response"

Please edit this issue to address the above within 2 hours, or it will be automatically closed.

---

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

• vscode extension: adding file to opencode doesn't work in 1.0+ #3947: VSCode extension file path insertion not working (similar: VSCode extension inserting file references)
• [Bug] Windows paths with different separators (backslash vs forward slash) treated as different directories in Web UI #12940: Windows paths with different separators (backslash vs forward slash) treated differently (similar: Windows path separator bug)
• [FEATURE]:The OpenCode extension for VS Code to be used in a Windows environment. #8128: OpenCode VS Code extension in Windows environment (related: VSCode + Windows context)

If you believe this was flagged incorrectly, please let a maintainer know.

[github-actions]

This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.

Feel free to open a new issue that follows our issue templates.