Subscribe
Sign in
Cursor
The AI Code Editor
Start new thread
Sundar Arvind

Multi Window Vibe Coding for Max Efficiency

by

Hi all,

Our team @ Arthos, a Music AI startup, uses @Cursor for everything (we actually have a massive budget in house for the usage based pricing :) ). I've always wondered if it's possible to open the same repository on multiple windows, and vibe code non conflicting features.

Has anyone tried this? What happens if Cursor edits the same file with 2 different agentic instances?

Super curious to know more!

163 views

Add a comment

Replies

Best
Tijs Teulings

Sounds like this workflow is better suited to agents that can pick up tasks from github issues like the copilot asynchronous agent setup. Developers use git for a reason right. Like you would not want devs messing with code in a shared directory you also don’t want agents to do that. Instead they each work on their own checked out version of the repository and create PRs like a regular dev. Then this is no issue.

Melih Can Demir
I'm excited to try it out. Shadow Workspace supports this type of multi-window editing, but there's always a risk, especially when adding new features from different windows. When editing the same file at the same time, conflicts or corruptions can occur. Sometimes changes are lost or incompletely applied.

I failed miserably to do that, but I also didn't try too hard because now we can just go and use background agents, also if one is ok with unchecking the privacy option.

Xinjie

Would love to try that too. What I’ve tried is split the project based on modules, then open each module separately in Cursor. If needed, I create symbolic links between them for reference.