Cursor 云 Agent 开发环境：多仓库支持与可配基础设施
Cursor 推出云 Agent 开发环境新工具，支持多仓库配置、Dockerfile 即配置（含构建密钥和层缓存加速 70%）、Agent 引导式环境验证以及环境级治理（版本历史、审计日志、出口/密钥作用域）。企业团队可运行端到端并行 Agent 舰队，在完全可控的环境中完成代码编写、测试、查询和 API 调用。环境配置失败时回退到基础镜像，保证 Agent 持续运行。
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.
与本地代理相比，云代理更易于并行化，在笔记本电脑合上时仍能持续工作，并且可以响应程序化触发器自主运行。
但代理的能力受限于其运行环境。一个能写代码却不能运行测试、查询服务或访问 API 的代理无法闭环完成工作。
要从头到尾完成工程任务，云代理需要一个类似于你笔记本电脑配置的开发环境：克隆的仓库、安装的依赖项、内部工具链的凭据，以及构建系统的访问权限。有效的开发环境为代理提供代码库和组织的完整上下文，使其能够测试和验证工作成果。
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.
今天，我们推出了配置云代理开发环境的新工具。Cursor 也可以利用这些工具来设置和维护你的环境。此次发布使团队能够更轻松地运行并行代理集群，在你完全掌控的开发环境中端到端处理任务。
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:
AmplitudeDecagonSnykBILT
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.
Steven Cheng
Senior Engineering Manager, Amplitude
多仓库环境
企业中大多数工程工作涉及多个代码库和仓库。运行微服务的大型组织往往拥有许多需要同步变更的仓库。局限于单一仓库的代理用途有限，因为它无法跨所有必要的上下文进行推理。
基于我们在多根工作区（multi-root workspaces）方面的工作，云代理和自动化现在支持多仓库环境。你可以配置一个包含代理工作所需所有仓库的环境，并可跨会话复用。当多个仓库纳入范围后，代理能够推理代码库某一部分的变更如何影响其他部分，并跨仓库交付、测试和验证变更。
以下是一些使用多仓库环境的客户反馈：
AmplitudeDecagonSnykBILT
“我们在 Amplitude 的公共 Slack 频道中运行 Cursor 自动化。多仓库支持是它们真正发挥作用的关键。代理可以调查报告的问题，找出涉及哪些仓库，并在正确位置提交带有完整上下文的修复 PR。”
——Steven Cheng，Amplitude 高级工程经理
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.
环境配置即代码
为了更方便地更改、调试和审查环境定义，我们改进了基于 Dockerfile 的配置。这包括对构建密钥（build secrets）的支持，可以直接从 Dockerfile 安全地访问私有包注册表。构建密钥限定在构建步骤范围内，不会传递到运行中的代理环境。
我们还升级了层缓存，因此当你更改 Dockerfile 时，仅重新构建镜像中更新了的层。命中缓存的构建运行速度提升 70%。
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.
对于不想从头编写 Dockerfile 的团队，Cursor 可以为你配置 Dockerfile。Cursor 会检查你的仓库，分析所需的工具和依赖项，并生成一个可供编辑和版本化的配置。此功能目前处于私有测试阶段，将在未来几周内向企业团队推出。
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.
改进的代理引导式环境设置
当 Cursor 配置你的环境时，它会向你提问、标记缺失的凭据，并验证环境是否设置正确。
Cursor 还对开发环境有了更强的感知能力。它会显示代理运行环境的版本。如果环境配置失败，Cursor 会默认使用一个包含明确警告标志的基础镜像，从而让你的云代理能够继续运行而不是立即失败。
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.
下一步计划
目前，环境是在某个时间点配置的，并在与代码库不同步时重建。我们正致力于构建能够随代码库演变而自主进化的环境设置。
要开始使用云代理开发环境，请阅读文档或访问你的云代理仪表板。