VS Code extension for multi-window projects
Built for Multi-monitor developers and teams needing parallel editing sessions or debugging of the same codebase..
“[declined by microsoft/vscode: closed as not planned] Currently VS Code prevents opening a folder more than once which makes it impossible to work on a project …”
The receipts — real demand
“[declined by microsoft/vscode: closed as not planned] Currently VS Code prevents opening a folder more than once which makes it impossible to work on a project in multiple windows (e.g. on multiple displays). @bpasero @dbaeumer @egamma @alexandrudima please raise any obstacles and issues you might foresee with this request. Issues found so far: - [ ] we use the workspace path as identifier to communicate back…”
Full dossier
Unlock the full dossier — free
Every corroborating quote, the source receipts, and the community echo. One email, no payment.
Why this is a gap
Surfaced from a high-intensity complaint with clear willingness to pay and a specific, reachable audience.
The market
Multi-monitor developers and teams wanting to edit the same codebase in parallel windows (e.g., debugging and editing side-by-side). No search volume; the pain (VS Code core rejects multi-window for a folder) suggests demand is real but VS Code's design blocks it deliberately.
Competition & the opening
Workspaces and side-by-side editors exist in VS Code; the gap is true multi-window support for the same folder, which the core team chose not to enable.
What's hard to build
VS Code's single-instance-per-folder architecture is a deep design choice; working around it requires either a custom fork, heavy extension hooks (IPC, state sync), or building atop Codium/Cursor forks. Feasibility 5/10 reflects the architectural barrier.
Why now
Multi-monitor setups are now standard but VS Code's architecture hasn't adapted for true multi-window project workflows.
How you'd monetize
$9.99/mo VS Code extension subscription