When saying @cursor Implement to the agent in Linear, it starts two background agents with the exact same query on the Background Agents dashboard. I’ve only seen this starting yesterday. It’s doing it for every single issue.
Steps to Reproduce
Just create an issue in Linear and comment @cursor Implement and see if it starts two background agents as well.
Hey, I don’t want to spam I know you guys are doing amazing work.
But this Linear integration is currently unusable because of the double agent spawn. It breaks everything, causes the agent to fail with error. I’ve set up the perfect workflow with Linear and background agents automatically updating statuses, running tests, etc. and I’m unable to use it at all currently because of this issue. It’s absolutely number 1 for me and I guess for all people using Linear integration.
Thank you.
Since a few days nearly every task i push from Linear to Background Agents gets 2 agents working on its
Steps to Reproduce
Push a ticket from Linear to Cursor background agent and its creates 2 agents. One includes documentation, one does not, the one that does not actually get created as a PR in Github.
Any word on this issue? I’m also seeing two background agents spawn for each task I assign to Cursor. It makes the feature nearly unusable because I don’t know which one attaches to the Linear task and it also creates two branches/PRs in Github.
Actually, it’s a process that selects the best option when two agents work on the same task. This leads to a higher-quality result. We’ll also improve the visual part of this process.
