2.0 - A step in the wrong direction

Ideas Feedback
100

2 months ago I had a variant of this ‘parallel Cursor instances per worktree’ workflow working well.

I’d run one instance of Cursor per background agent.

The processing power was being handled in the cloud (by their equivalent of GitHub Codespaces).

So I had the parallel versions of the editor, but my MacBook could handle it, and battery life was better.

Then background agents broke, and it hasn’t been fixed since.

It’s frustrating that it broke 2 months ago, and even though @deanrie said the team are working on a fix, there hasn’t been one.

Meanwhile, Cursor 2.0 has been released :cry:.

I wish broken things would be fixed before flashy 2.0 releases.