Two concurrent Cursors on the same codebase, any ideas?

Hi,

Before I turn two Cursors on my codebase, I like to hear from anyone who has had any experience with it. In theory it must work.
I want to work in the same folder, not isolated instances.

What could possibly go wrong? :grin:

Yes, but you will have to set up rules so that both of them get and set their info on the same source of truth. Unless you let each of them work on a separate small component then it should work. Otherwise rules → before start get relevant context and after done update the relevant context has it been changed

1 Like

Two in parallel chats or in two cursor apps?

1 Like

Two separate instances. It actually works well. One must just get the hang of it, and things actually beging to accelerate a lot.

1 Like

Now can we get two separate models to talk to each other and determine the best approach to a problem? :slight_smile:

2 Likes

Hello, I was thinking the same thing. It could have been great. Including a free model in the loop might be a good choice. But how?

That would be a great feature request, I definitely would upvote as this could speed up all the handling.

1 Like

Alright, I will see if I can formulate this request.

just did it. If you have proposal for change please add. I think this will end up with making Cursor an AI in itself.

1 Like

Yes you are right :slight_smile: will have a look and add ideas

1 Like