Can't Share Cloud Agent with Team Members

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

In the cursor cloud agent web ui, when I share a cloud agent with my teammate, they can only view it. Why can’t they add their own messages? It seems useless for it to be readonly since the only reason you want to share it is if you are passing it off to a teammate. I will have to make a ui wrapper around the api to allow them to add follow up messages.

Steps to Reproduce

Make a cloud agent. Copy the link to it or hit share and copy that link. Send it to a teammate and have them open it up. They can’t see the chat input and can’t create a pr from it or anything, they can only view it.

Expected Behavior

They should be able to add follow up messages, make prs, and everything the original creator can do.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.0
VSCode Version: 1.105.1
Commit: ea48594a09b2e8d1fd6fb5db8502d43815a1e1a0
Date: 2025-12-09T06:33:08.669Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.5.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

1 Like

Hey, thanks for the report. We need to check with the engineers whether this is expected behavior or a bug.

A few questions to understand the situation:

  1. Is your teammate logged into Cursor with an account that’s part of your team/workspace?
  2. Did you try sharing via the Share function in the UI or just copy the URL?
  3. Does your teammate see any errors or is the chat input simply missing?

I’m escalating this to the engineers. According to the docs (Web & Mobile | Cursor Docs), collaboration should be possible, but it’s unclear how this works for shared links.

They do belong to my team and workspace. I tried sharing through both the share link and copying the url. The chat is simply missing with no way for them to add a follow up message.

Thanks for the clarification. This is a known issue - even team members see the Cloud Agent as read-only when opening a shared link, even though they are in the same workspace.

The problem is that shared links don’t grant full editing rights - this is a limitation of the current sharing implementation in Cloud Agents.

For now, please try:

  • Opening the Cloud Agent directly from Cursor IDE or cursor.com/agents via workspace login (not through the shared link)
  • Creating a separate Cloud Agent for the teammate instead of sharing

The team is already working on this.

Sounds good any eta? Considering making a ui wrapper using the cloud agents api and allowing my teammates to send followups through that but don’t want to make the effort if this is going to be a day or two thing

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

The feature to share background agent links within the team doesn’t seem to be working. People can only access agents they’ve created.

Steps to Reproduce

  • Go to cursor.com/agents
  • Create a new agent
  • Copy the link (either from the URL or from “Share Link” in the … menu)
  • Send it to someone else on the team and ask them to open it
  • Teammate will not be able to open it

Expected Behavior

Any user on the team opening the link can see the background agent chat / changes

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

N/A (Cursor web)

For AI issues: which model did you use?

N/A

For AI issues: add Request ID with privacy disabled

N/A

Does this stop you from using Cursor

No - Cursor works, but with this issue

Thanks for the clarification.

I talked to the team, and this is not a bug but a missing feature. It’s supposed to work this way.

Since this is a known limitation of the current implementation (not a bug), could you please create a Feature Request in the Feature Requests section?

This will help:

  • Users understand it’s a planned feature
  • The community vote on the priority of this feature
  • Track the development status

Thanks!

Even though it says this should be possible right in the docs?? I swear there was one day where this worked but not anymore. Anyway if its in the docs it should be high priority imo. If anyone else is facing this issue you can use this as a workaround in the meantime https://v0-cloud-agents-interface.vercel.app/

1 Like

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.