Linear integration No access to repository issue 2

Support Bug Reports
, , ,
1

Describe the Bug

[I’m just reopening this post: Linear integration No access to repository issue]

Where does the bug appear (feature/product)?
Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug
When you reconnect Linear to another Cursor, integration stops working.

Steps to Reproduce

Steps to Reproduce
Connect Cursor account with Linear and GitHub
Check that everything is working
Disable all integrations
Log in to another Cursor account and set up integration with the same Linear and Github.
I get an error from Cursor in Linear “:warning: No access to repository…”

Expected Behavior

In Linear, it says when launching the Cloud Agent from which account it is trying to launch it. (Very useful if you work in a team)
Integration does not give errors, but starts working with a new account.

Operating System

MacOS

Version Information

Cloud agents

Does this stop you from using Cursor

Yes - Cursor is unusable

8

Hi @bernatfortet Sorry for the inconvenience. This is a known class of bugs that we’re tracking and I’ve added your report here to the bug report. We’ll let you know any updates!

9

Hi Kevin, is there any type of workaround? Any way to reset anything? Clear caches?

10

Hi @kevinn checking again. is there any workaround? There’s absolutely no way for me to use Linear at all?

11

Hi @bernatfortet Sorry for the delay. Can you try this?

Sign into the new Cursor account.

  1. Go to cursor.com/linear and complete the per-user “Authorize with Linear” flow.

  2. On that same account, confirm Dashboard → Cloud Agents has GitHub connected, a default repo set, and the usual Cloud Agent setup.

  3. Retry delegating the Linear issue to Cursor.

There’s a chance that this works because it is based on a per user flow rather than per team flow. The bug hasn’t been fully sorted out yet but there’s a chance that this can work for you.

12

after doing this, the issue improves but agents are still not working. I’ll add more detail soon.

13

it’s showing

:warning: Could not find repository RestorationScope/restoration-scope in any of your connected SCM providers. Make sure the repository exists and you have access to it, or specify the full URL (e.g., repo=https://github.com/owner/name).

but my organization repo is “Restoration-Scope” not “RestorationScope”.
Not sure where it got the string without “-”