[FEATURE]:VS Code integration: Unable to detect full workspace / multi-root projects

[sinbazhou]

Feature hasn't been suggested before.

• I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Problem

When using OpenCode embedded inside VS Code, it cannot properly detect the VS Code workspace.
This is especially problematic for multi-root workspaces (e.g. frontend + backend projects).

Currently, OpenCode:

• Cannot access all workspace folders
• Cannot understand VS Code multi-root structure
• Often only sees a single directory or cwd

This makes it hard to use OpenCode as an in-editor agent compared to tools like Cline or Continue.

---

Expected Behavior

When running inside VS Code, OpenCode should be able to:

• Detect all workspaceFolders
• Support multi-root workspaces
• Access the active editor context
• Optionally sync the active project root

---

Suggested Solutions (Optional)

Some possible approaches:

1. Provide an official VS Code extension using vscode.workspace APIs
2. Add a workspace bridge layer that passes workspace info to OpenCode CLI
3. Allow explicit workspace injection from VS Code (multi-root aware)

---

Use Case

My setup:

• VS Code with multi-root workspace
• Frontend (vue)
• Backend (Flask / Python)

This is a very common full-stack workflow in VS Code.

---

Why This Matters

Without workspace awareness, OpenCode works well in CLI mode,
but loses much of its value when embedded in VS Code.

Better workspace integration would significantly improve adoption
for VS Code users.

[github-actions]

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

• [FEATURE]:Official - OpenCode VS Code extension #11176: Feature request for official VS Code extension that includes project-aware context (automatically picking up current workspace using VS Code APIs)
• Editor integrations #216: Editor integrations tracking - syncing context between editor and agent

Consider adding your specific use case (multi-root workspace support) as a comment on those issues rather than opening a new one.

[nexxeln]

thanks for reporting this. this is a real gap in the current vscode integration.
right now the extension is mostly a terminal wrapper, so it doesn’t fully sync vscode multi-root workspace folders/context yet.
this is already tracked in #11176 and #216, so i’m closing this as a duplicate to keep discussion in one place.