We run Cursor Cloud Agents from CI using the official @cursor/sdk (Agent.create with cloud: { repos: [...] }). Runs finish successfully; we get a stable bc-… agent id and we try build URLs like:
https://cursor.com/agents?id=<bc-id>
or cursor://agents?id=<bc-id>
**but these links don’t work.
What we are looking for**
A way to open a specific SDK-created cloud agent by id after automation (HTTPS, an app deeplink).
Clarity on who can open that URL: only the user who owns the CURSOR_API_KEY, the whole team, org admins, service-account runs, etc.
Example id (from a real run, for repro if useful): bc-e39a7c9c-5321-47a5-9440-7783e721d04f
Access is still permission-gated. The link is not publicly accessible - if a user doesn’t have access, they’ll get an error when reaching it. A signed-in user needs access to that cloud agent, typically the agent owner or a member of the same team with access to the underlying repo. Service-account-created agents can be managed via the API/SDK using the service account key, and team members with the right team/repo access should be able to open the web link.
So go ahead and give that a shot with example ID you’ve shared and let me know if you have any questions!
Make sure that you have the same repo that you have for your cloud agent open in the Cursor IDE and that are signed in to the same account. If you are on a different project or signed into a different account, the deep link likely won’t work.
Hey @kevinn , the error on the web version is: “Cloud agent not found…”.
For the desktop link, it only opens the Cursor app but does not select the correct agent.
I tried running the agent using the Cursor token from my Enterprise employee account. In that case, the agent appears in my Cursor app, but the links still do not work.
I also tried running the Cursor agent using the Enterprise service account and then opening the links using my employee account within the same Enterprise workspace. In that scenario, I get the same errors, with the only difference being that the cloud agent does not automatically appear in my employee account — which is expected, since it was launched from the Enterprise service account.
This workflow is something we are actively trying to enable within Match Group, where AI agents launched from a shared Enterprise service account can later be accessed and continued by different team members within the same Enterprise workspace.
If this is not currently supported, please consider this a feature request.
Hi @Kristian_Rusyn, Thanks for the detailed explanation and examples. You’re right: this workflow is not currently supported.
Cloud agent sessions are scoped to the account that created them, so an agent launched from a shared Enterprise service account cannot currently be opened or continued by other members of the same Enterprise workspace via the open-by-ID links which explains the “Cloud agent not found” behavior and why the desktop link can open Cursor without selecting the expected agent.
I launched a feature request on your behalf so that we can get some more attention on this!
In the meantime, the best workaround is to launch the agent from the same user account that needs to continue it later.
Thank you so much @kevinn for creating a feature request. Just to let you know that this feature could be almost a deal breaker for us, hope that the Cursor team shares the same vision as we do about it and could implement it asap.
Hey Kevin , I tried to open the links of agents I launched from my own employee account. And the result is the same, they don’t work . Also the buttons on the cloud agents opened in Cursor Desktop application behave oddly:
