Cloud Agents
Cursor Cloud Agents: Settings & Configuration
Workspace admins configure Cloud Agents from the Cloud Agents dashboard. The settings cover environment management, default model and repository, network access modes, security toggles for agent summaries, and team features such as long-running agents and follow-ups. Changes to team feature settings save instantly and affect new agents immediately.
On this page
How do I manage Cloud Agent environments?
The Environments view lists the saved environments available to your team, and each one can be scoped to a single repo or to a group of repos. Opening an environment shows everything that defines how an agent starts. The list below covers what you can review inside one.
- The repositories it applies to
- Whether it uses a snapshot or
.cursor/environment.json - The update script that runs before an agent starts
- Runtime secrets and build secrets
- Network access settings
- Version history and setup runs
Three actions drive changes to an environment. Use Update with Agent to have Cursor inspect the current environment and propose a new setup, New Setup Run to have Cursor start setting up the environment fresh, and Restore from version history to make a prior environment version active again.
What do the default settings control?
Default settings decide what a run uses when it does not specify the choice itself, so they smooth out the most repetitive prompts. The list below maps each default to its effect.
- Default model – the model used when a run does not specify one. Pick any model that supports Max Mode.
- Default repository – when empty, agents ask the user to choose a repo. Supplying a repo here lets users skip that step.
- Base branch – the branch agents fork from when creating pull requests. Leave blank to use the repository's default branch.
How do I control network access for Cloud Agents?
Network access settings control which network resources Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. can reach, and user and team settings support three modes. The table below maps each mode to what it permits.
- Mode
- Allow all network access
- What it permits
- No domain restrictions.
- Mode
- Default + allowlist
- What it permits
- The default domains plus any domains you add.
- Mode
- Allowlist only
- What it permits
- Only domains you explicitly add.
| Mode | What it permits |
|---|---|
| Allow all network access | No domain restrictions. |
| Default + allowlist | The default domains plus any domains you add. |
| Allowlist only | Only domains you explicitly add. |
Users, team admins, and environment owners can all configure network access. Environment-level settings can inherit user or team policy, add an environment allowlist, or define their own access mode.
What do the security settings do?
All security options require admin privileges, and they govern how much of an agent's work is exposed and who can steer it. The list below covers each toggle.
- Display agent summary – controls whether Cursor shows the agent's file-diff images and code snippets. Disable this if you prefer not to expose file paths or code in the sidebar.
- Display agent summary in external channels – extends the previous toggle to Slack or any external channel you've connected.
- Team follow-ups – controls whether team members can send follow-up messages to cloud agents created by other users on the team.
What team feature and follow-up settings can admins set?
Team admins can enable or disable team-wide capabilities, and these changes save instantly and affect new agents immediately. Two features sit here: Long running agents, which controls whether team members can run agents for extended durations, and Computer use, which controls whether agents can use computer interaction capabilities and is available to enterprise teams only.
Team follow-ups let team members send follow-up messages to cloud agents created by other users on the same team, which helps when a teammate starts an agent and you need to course-correct or continue the work while they're unavailable. Team admins control this from the Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. security settings with three options, mapped in the table below.
- Setting
- Disabled
- Behavior
- Only the original creator can send follow-ups to their agent. No team follow-ups are allowed.
- Setting
- Service accounts only
- Behavior
- Team members can send follow-ups to agents created by a service account, but not to agents created by other human users.
- Setting
- All
- Behavior
- Any team member can send follow-ups to any agent on the team, regardless of who created it.
| Setting | Behavior |
|---|---|
| Disabled | Only the original creator can send follow-ups to their agent. No team follow-ups are allowed. |
| Service accounts only | Team members can send follow-ups to agents created by a service account, but not to agents created by other human users. |
| All | Any team member can send follow-ups to any agent on the team, regardless of who created it. |
Enabling team follow-ups means a user can influence the execution of a cloud agent that runs with another user's secrets and credentials. A follow-up message can instruct the agent to read environment variables, print secrets to logs, push credentials to an external endpoint, or perform actions using the original creator's access tokens.
A team member with limited permissions could escalate their access by directing an agent that holds a more privileged user's secrets. Cursor recommends treating this setting with the same care you would give shared SSH keys or service credentials.
Frequently asked questions
Who can configure Cloud Agents settings?
Workspace admins configure Cloud Agents from the Cloud Agents dashboard. Network access can be configured by users, team admins, and environment owners, while all security options require admin privileges. Team feature settings are controlled by team admins.
How do I roll back an environment to a previous version?
Open the environment in the Environments view and use Restore from version history to make a prior environment version active again. Each environment also exposes its version history and setup runs for review.
When do team feature changes take effect?
Changes to team feature settings save instantly and affect new agents immediately.
Sources & last verified
Cursor ships frequently. Facts verified against primary sources on June 29, 2026.