Hello there, I have an self hosted automation that is triggered by some random internal user where I used a service account key for it. The problem I have is that other users cannot see the prompt in the cursor dashboard. So I would like to know how to make this prompts viewable for all cursor users in my team. Thanks in advance!!
Hey, quick note:
Automation visibility in the dashboard is controlled by the automation scope. For teammates to see the prompt, the scope must be Team Viewable or Team Editable, not Private. Runs started via a service account key belong to the service account, and teammates can see them on the team-scoped agents page.
Main point: this only works on the Teams or Enterprise plan. Based on what we see, your account is currently on Free (subscription canceled) and not part of a team, so you can’t share automations or their runs yet since this feature is tied to a team plan.
If you upgrade to the Team plan and create an automation with scope Team Viewable or Team Editable, it should show up. More details: Automations | Cursor Docs
The problem is that this flow is not an automation, is just myself using the agents api v0 to trigger a agent in the self hosted agents, so the scope is not visible in the dashboard. Also my subscription is the enterprise one, but it’s not visible as a enterprise one because it’s an alias.
Thanks for the clarification, that makes it clearer now.
When an agent is triggered directly via POST /v0/agents using a service account key, not via Automation, the run belongs to the service account itself, not to the user who called the endpoint. Because of that, other teammates won’t see this run in the personal view on cursor.com/agents. That page only shows each user their own runs.
For teammates to see service-account-triggered runs, including the prompt, you need to use the team-scoped agents page: go to cursor.com/dashboard then switch to the team, then Agents, or open /t/<team-slug>/agents. This page shows runs owned by team service accounts, and it’s available to members of an Enterprise team.
A few notes about the alias situation so we can understand what’s happening:
- Which account did you use to create the service account key, your Enterprise account or
vnc***@gmail.com(alias)? If the key was created from an account that doesn’t have team context, the service account won’t be attached to the Enterprise team, and teammates won’t be able to see its runs at all. - When you log in to
cursor.comand open the team-scoped agents view, do you see your service-account-triggered run there or not? - Can you share the team slug or team name, or the Enterprise account email via DM? I want to confirm the alias is correctly linked to the tenant.
Docs: Service Accounts | Cursor Docs, Cloud Agents API | Cursor Docs
Where do you switch to the team, then agents in the interface? Could you show me some prints of this switch option please? Also this is my enterprise account, and I’m not seeing this teams option
Today I noticed that prompt sharing works for some teammates, but not for all, but still the follow-ups from our teammates for our self hosted agents aren’t working. I enabled the team followups, but maybe I’m missing something. Is there a way to debug this issue on our side? If needed we tried the follow-up on this agent chat bc-82497841-0a4a-4951-a9be-5d948529a119
