云端智能体比本地智能体更容易并行化，在笔记本电脑合上时仍能继续工作，并且可以响应程序化触发条件自主运行。
但智能体的能力取决于其运行环境。一个能写代码但无法运行测试、查询服务或调用 API 的智能体，无法形成工作闭环。
要端到端地完成工程任务，云端智能体需要一个与笔记本电脑上类似的开发环境：克隆的代码仓库、已安装的依赖项、内部工具链的凭证，以及对构建系统的访问权限。有效的开发环境能让智能体全面了解你的代码库和组织结构，从而测试和验证其工作成果。
今天，我们推出了用于配置云端智能体开发环境的新工具。Cursor 也可以利用这些工具来设置和维护你的环境。此次发布共同让团队能够更轻松地运行并行智能体集群，在你完全掌控的开发环境中端到端地处理任务。
多仓库环境
企业中的大部分工程工作都涉及多个代码库和仓库。运行微服务的大型组织通常有许多需要同步更新的仓库。局限于单个仓库的智能体用途有限，因为它无法跨所有必要的上下文进行推理。
云端智能体和自动化功能现在支持多仓库环境，这是基于我们在多根工作区方面的工作成果。你可以配置一个包含智能体工作所需所有仓库的单一环境，并可在会话间重复使用。有了多仓库的上下文范围，智能体就能推理代码库中某一部分的变更如何影响其他部分，并跨仓库工作以交付、测试和验证变更。
以下是我们部分客户对多仓库环境的直接评价：
我们在 Amplitude 的公共 Slack 频道中运行 Cursor 自动化功能。多仓库支持正是让这些功能真正有用的关键。智能体可以调查报告的问题，找出涉及哪些仓库，然后在正确的位置以完整的上下文打开包含修复方案的 PR。
将环境配置作为代码
为了让环境定义更易于修改、调试和审查，我们改进了基于 Dockerfile 的配置。这包括对构建密钥的支持，使得直接从 Dockerfile 安全访问私有包注册表变得简单。构建密钥的作用域限定在构建步骤内，不会传递到运行中的智能体环境。
我们还升级了层缓存机制，这样当你修改 Dockerfile 时，只会重建镜像中更新的层。命中缓存的构建运行速度提升了 70%。
对于不想从头编写 Dockerfile 的团队，Cursor 可以为你配置 Dockerfile。Cursor 会检查你的代码仓库，找出所需的工具和依赖项，并生成一个可供你编辑和版本管理的配置。此功能处于私有测试阶段，将在未来几周内向企业团队推出。
改进的智能体主导环境设置
当 Cursor 配置你的环境时，它会向你提问、标记缺失的凭据，并验证你的环境是否设置正确。
Cursor 对开发环境的感知能力也更强了。它会向你显示智能体所运行环境的版本。如果你的环境配置失败，Cursor 会默认使用一个带有清晰警告标识的基础镜像，以便你的云端智能体能够继续运行，而不是立即失败。
环境治理与安全控制
每个开发环境现在都拥有自己的版本历史记录，用户可以查看和回滚。管理员还可以将回滚权限限制为仅管理员可用。审计日志会记录团队成员对环境执行的每一项操作，让安全团队全面了解谁更改了什么内容。
出站流量和密钥现在可以在开发环境级别进行作用域限定。团队可以为一个环境限制出站网络访问到特定的允许列表，同时让另一个环境拥有更宽松的权限。此外，为一个环境配置的密钥无法从任何其他环境访问。
未来规划
目前，环境是在某个时间点配置的，当它们与代码库不同步时会进行重建。我们正在朝着环境设置能够随着代码库的演变而自主演进的方向努力。
要开始使用云端智能体开发环境，请阅读文档或访问你的云端智能体控制面板。
团队版定价改进
在你的自有基础设施中运行云端智能体
Katia Bazzi
构建可自动运行的智能体
Jack、Jon 与 Josh
Cloud agents are easier to parallelize than local agents, continue working when your laptop is closed, and can run autonomously in response to programmatic triggers.
But agents are only as capable as the environments they run in. An agent that can write code but can't run tests, query services, or reach APIs cannot close the loop on its work.
To take engineering tasks from start to finish, cloud agents need a development environment similar to the setup on your laptop: cloned repositories, installed dependencies, credentials for internal toolchains, and access to build systems. Effective development environments give agents full context on your codebase and organization, so they can test and verify their work.
Today we're shipping new tools for configuring cloud agent development environments. Cursor also can use these tools to set up and maintain your environments. Together, this release makes it easier for teams to run fleets of parallelized agents that handle tasks end-to-end, inside development environments you fully control.
Multi-repo environments
Most engineering work in the enterprise spans multiple codebases and repositories. Larger organizations running microservices often have many repos that need to move in tandem. An agent confined to a single repo has limited usefulness because it can't reason across all the required context.
Cloud agents and automations now support multi-repo environments, building off our work on multi-root workspaces. You can configure a single environment with all the repositories an agent needs for its work, with re-use across sessions. With multiple repos in scope, agents can reason about how a change in one part of the codebase affects others and work across repos to deliver, test, and verify changes.
Hear directly from some of our customers using multi-repo environments:
We run Cursor Automations across public Slack channels at Amplitude. Multi-repo support is what makes them actually useful. An agent can investigate a reported issue, figure out which repos it touches, and open a PR with the fix in the right places with full context.
Environment configuration as code
To make it easier to change, debug, and review environment definitions, we have improved Dockerfile-based configuration. This includes support for build secrets, making it easy to securely access private package registries directly from Dockerfiles. Build secrets are scoped to the build step and aren't passed to the running agent's environment.
We've also upgraded layer caching, so that only the updated layers of your image rebuild when you change the Dockerfile. Builds that hit the cache run 70% faster.
For teams that don't want to write Dockerfiles from scratch, Cursor can configure the Dockerfile for you. Cursor will inspect your repos, figure out the tools and dependencies required, and produce a configuration you can edit and version. This feature is in private beta and will be rolling out to Enterprise teams over the coming weeks.
Improved agent-led environment setup
As Cursor configures your environment, it will ask you questions, flag missing credentials, and validate that your environment is set up properly.
Cursor is also more aware of development environments. It will show you the version of the environment your agent is running in. If your environment configuration fails, Cursor will default to a base image with clear warning signs so that your cloud agents can keep running instead of immediately failing.
Environment governance and security controls
Every development environment now has its own version history that users can review and roll back. Admins can also restrict rollback permissions to admins only. An audit log captures every action team members take on environments, giving security teams full visibility into who changed what.
Egress and secrets can now be scoped at the development environment level. Teams can restrict outbound network access to a specific allowlist for one environment while leaving a different environment more permissive. Additionally, secrets configured for one environment aren't accessible from any other.
What's next
Today, environments are configured at a point in time and rebuilt when they fall out of sync with the codebase. We are building towards environment setups that evolve autonomously as your codebase evolves.
To get started with cloud agent development environments, read the docs or visit your cloud agents dashboard.
Improvements to Teams Pricing
Run cloud agents in your own infrastructure
Katia Bazzi
Build agents that run automatically
Jack, Jon & Josh