[FEATURE] Direct Read + Write feature for VS Code Virtual Workplaces like ABAP File system
Status Open
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 4 comments · opened Mar 13, 2026
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
Not able to directly make read write operations from VS Code Claude Extension for Virtual Workplaces (like ABAP File system)
Proposed Solution
Extend the feature to read/write to virtual workplace
Alternative Solutions
_No response_
Priority
Critical - Blocking my work
Feature Category
CLI commands and flags
Use Case Example
_No response_
Additional Context
_No response_
4 Comments
+1 for this feature request.
The root cause is that the VS Code extension operates via an embedded CLI/terminal rather than using the
vscode.workspace.fsAPI, so it cannot access any registered FileSystem Provider.Suggested approach: Have the VS Code extension use
vscode.workspace.fsfor all file read/write/search operations when running inside VS Code. This would unlock support for every virtual filesystem at once, rather than needing per-provider workarounds.+1 for this feature request. I'm experiencing the exact same issue with the Oracle SQL Developer Extension for VS Code.
This is a significant limitation for anyone using Claude Code alongside database development extensions in VS Code. Would love to see this prioritized.
+1 Overleaf workshop support would be hugely beneficial.
+1, the official ABAP Development Tools for VS Code from SAP also have this issue when trying to use Claude Code