When I try to create an automation on https://cursor.com/automations/new, I get a toast in the bottom that says “Team-scoped automations require a team context”. I am not on a team plan, I just have an individual plan, but I was under the impression I can still create automations…
Steps to Reproduce
Go to the new automation page while logged into my account.
Fill in the following automation info (as captured by clicking the copy as JSON button in the top right):
{
“name”: “CodeRabbit Review Response”,
“triggers”: [
{
“git”: {
“pullRequest”: {
“repos”: [
“XXX - can only post 2 URLs as a new user”
],
“repo”: “XXX - can only post 2 URLs as a new use”,
“prAction”: 4,
“commenterAllowlist”: [
“coderabbitai”
],
“commentContains”: “”
}
}
}
],
“actions”: [
{
“mcp”: {
“server”: {
“name”: “Linear”
}
}
},
{
“prComment”: {}
}
],
“prompts”: [
{
“prompt”: “Please review the unresolved code review comments on this PR and address them if appropriate.\n\nFor suggested changes that diverge significantly from the original stated goal for the PR (see Linear), ask for confirmation from the user before implementing.”
}
],
“model”: “composer-2”,
“memoryEnabled”: true,
“scope”: “team_visible”
}
From the JSON it looks like the scope is set to “team_visible” even though I am not on a team plan.
Hi @beige_mode I’m sorry the inconvenience, and thank you for reporting. Yes, this is the same issue as the one you linked to in your post. On individual plans (Pro/Ultra), the web “Create automation” flow defaults the automation scope to a team-scoped value, which the backend then rejects with the Team-scoped automations require a team context error you’re seeing.
We have a bug report raised, and I’ve linked this forum thread to it so I can notify you when it is fixed.
In the meantime, you can still create local Automations on your Cursor App. I realize this is not ideal, but could still be a good way to experiment with automations while we patch the Cloud Automations bug. Thank you for your patience!
How do you create local Automations on our Cursor App? I can’t find such an option.
Edit: Didn’t find local Automations but I did find a work around.
Note: If you don’t know how to use devtools & terminal commands, I would suggest you wait for their fix.
Open your browser devtools, ensure network requests are logged, create your automation, see the error, find the request to /api/automations/create-automation , then right click, use “Copy > Copy as cURL’” and paste to an editor. Find AUTOMATION_SCOPE_TEAM_VISIBLE and swap it to AUTOMATION_SCOPE_USER
It will probably be at the end of the json payload like ..."scope":"AUTOMATION_SCOPE_TEAM_VISIBLE"}' so swap that to "scope":"AUTOMATION_SCOPE_USER"}'
Then copy the edited cURL command from your editor and paste it into your terminal and run it. The command should have all your cookies/session tokens etc needed to make the request as if the web browser did.
If it worked then you can see your automation on https://cursor.com/automations - If you see it, you can close your browser tab that you used to create it initially as it isn’t needed now.
Automation: daily 04:00 PDT trigger on a GitHub repo (main branch)
Tools enabled: Memories, Send to Slack, Read Public Slack Channels, Open Pull Request
Model: GPT-5.5 Medium
Environment: Cursor Cloud
OS: macOS (web app, latest Chrome)
Clicking Create surfaces the same toast — “Team-scoped automations require a team context.” Adding myself to the notify list for the patch. Thanks for the quick triage.
I got a popup to use some new feature to run automations on a schedule. I tried to create the default bug fixing automation but I deleted the Slack tool because I don’t use that. When I try to create it I get a tiny popup in the corner that says “Team-scoped automations require a team context”.
There is no reference anywhere in this feature UI that says anything about the concept of “team context”, or which of the options are implying this team context, or how I can avoid this.
Steps to Reproduce
Well I got the default bug hunting automation and tried to create it.
Expected Behavior
It should actually work and not show a meaningless, tiny but completely blocking error message with no indication of how to resolve it.
Operating System
Windows 10/11
Version Information
There doesn’t appear to be any way to see any version info in the web agent dashboard.