Linear Integration not working with new Automations Feature

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

So trying to setup the cool new automations feature!

The goal is when a new Linear issue gets created, have Cursor take a first crack at it.

I got everything set up, but when I create a linear issue, the automation isn’t getting triggered, I don’t see anything in my run history. I have Linear, Slack, and Github all connected.

I also don’t fully understand the Issue Created in Linear structure, because it then asks you to link it to a GH repo? Is this GH repo the one where Cursor will attempt to create the PR? If that’s the case I’d actually like to ideally be able to link it to two repos, because my project isn’t a monorepo, so it would be nice if I could provide multiple repos and have it figure out which one the changes need to be in. This could be two different automations I suppose but would be nice to combine.

Steps to Reproduce

Go through the steps to create a new Linear Automation(link Github, Slack, and Linear), enable the workflow, create a Linear ticket, no workflow is created.

Screenshots / Screen Recordings

Screenshot 2026-03-05 at 12.09.29 PM.png
Screenshot 2026-03-05 at 12.09.29 PM.png1940×1962 263 KB

Operating System

MacOS

Version Information

In Browser

Does this stop you from using Cursor

No - Cursor works, but with this issue

2 Likes
3

Hey, thanks for the report. Automations launched just yesterday, so some early bugs are expected. Let’s try to narrow this down.

A few things to check:

  1. Go to https://cursor.com/settings. Under Integrations, confirm Linear is connected and shows the right workspace. Try disconnecting and reconnecting Linear.

  2. In Linear, make sure the Cursor integration has access to the team where you’re creating the issue. Go to Linear Settings > Integrations > Cursor.

  3. After reconnecting, create a new test issue in Linear and check Run History again.

  4. Also try turning the automation off and back on after reconnecting.

About linking to multiple repos: right now each trigger is tied to one repo. Your idea to set up two separate automations, one per repo, and let the agent decide which one is relevant is probably the best approach for now. That said, feedback noted.

Let me know if any of this helps, or if it still isn’t triggering after reconnecting Linear.

4

Same issue here. I reconnected the Linear workspace, still not working. “Run Test” also does nothing. The Linear automation appears to not work at all.

1 Like
5

Hi Dean,

I tried all the above steps and am still having the same issue. Looks like Alexandru above is also having the same issue. Would appreciate if you guys could look into it!

Thanks!

6

I was coming hear to say the same thing, but tried one more step before I posted, and it worked:

In Linear, I at-mentioned cursor on an issue (“@cursor do xyz”) and it responded that I had to authorize the connection. (Everything else already appeared to be fully connected.)

Once I clicked the link it gave me to authorize the connection, then everything suddenly started working - cursor cloud agents responded to my mentions, and also the Linear-based triggers started firing. :tada:

2 Likes
8

Oh nice, this did actually fix it in the sense that now when I go and create a new linear issue, it spins up the automations. That said, it’s kinda half baked because whenever my coworkers open the issue, it still isn’t triggering. I have to duplicate the issue, only then will the triggers fire. Really buggy implementation by Cursor, wish they took the time to actually test before shipping this

@deanrie Can the team please look into this?

11

Hey, glad the @cursor mention in Linear helped with the initial issue.

About issues from teammates not triggering the automation, that’s a known bug. Right now the automation requires everyone who creates an issue to have an authorized connection to Cursor. If your teammates don’t have Cursor accounts, or they haven’t completed authorization via an @cursor mention in Linear, the triggers won’t fire.

A couple questions so I can better understand what’s happening:

  1. Do your teammates have Cursor accounts?
  2. Have they tried doing an @cursor mention in Linear as well to complete authorization?

The team is aware of this issue.

12

My teammates don’t have cursor accounts. I don’t think it’s realistic to expect every team member whose using Linear to being a cursor user. A large portion of our tickets are filled by the non-technical members of our team, and even on the engineering side not everyone uses Cursor, this feature seems kinda pointless if you have to ask everyone to auth into Linear via cursor

13

That’s a totally fair point. Requiring every team member in Linear to have a Cursor account and log in is honestly unrealistic, especially when tickets are created by non-technical users.

Right now this is a limitation of the current implementation. Triggers are tied to authorized users. I’ve passed this feedback to the team so automations can run on tickets from any user in a Linear workspace, even if they don’t have Cursor. I can’t promise a specific timeline yet, but your report helps us prioritize it.

I’ll share updates here if there’s any news.

14

Getting this issue my end, everything setup but not finding the repo. When it connects it gives a 400 in the UI

:warning: Could not access repository unicorn-mafia/unicorn-mafia. The repository may no longer exist, may have been renamed, or your GitHub/GitLab connection may need to be updated. Update your connection in the dashboard.

15

This is very limiting for teams that receive Linear tickets from non-eng team members. Is there a timeline for when this will get fixed? Are there any workarounds that the Cursor team would advise?

16

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

Hi,

I have an automation set up to monitor Linear for created tickets in a specific team space. However, right now it is not triggering when a Slack workflow creates a ticket, but does trigger when I create a ticket manually. This leads me to believe that the issue is something to do with tickets created by other bots (Slack in my case).

Steps to Reproduce

  1. Create a new automation and connect Linear and Github MCP
  2. Trigger the automation when an issue is created in Linear
  3. Observe difference in behavior when user creates a ticket in Linear vs when a Slack workflow or other bot creates a ticket in Linear

Expected Behavior

I’m expecting that any ticket created, regardless of owner/source should trigger this automation

Operating System

MacOS

Version Information

Version: 2.6.19
VSCode Version: 1.105.1
Commit: 224838f96445be37e3db643a163a817c15b36060
Date: 2026-03-12T04:07:27.435Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

19

+1 for this issue from our team, just to help with priorities :slight_smile:

I’ll try to work around this with webhook triggers, maybe that works with any user creating the issue

20

+1 here as well, hitting the exact same issue

21

We had this problem and came up with a temp solution until it’s fixed by cursor.

We set up a webhook to be fired from Linear when a new issue is created. That webhook is listened to by an N8N flow which then reshapes the data and sends another webhook which is listened to by Cursor.

A faff but it works!