Open-by-id URL for the cloud agent

Support Help
, ,
1

Hi,

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**

  1. A way to open a specific SDK-created cloud agent by id after automation (HTTPS, an app deeplink).

  2. 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

Thanks.

7

Hi @Kristian_Rusyn Thanks for the forum post!

Yes, this is supported, but the URL shape is path-based rather than query-based.

For a cloud agent id like:

bc-e39a7c9c-5321-47a5-9440-7783e721d04f

use:

https://cursor.com/agents/bc-e39a7c9c-5321-47a5-9440-7783e721d04f

For opening in Cursor Desktop, the deeplink form is:

cursor://anysphere.cursor-deeplink/background-agent?bcId=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!