正在加载视频...

视频加载失败

Each environment now has its own version history with rollback. An audit log captures every change. Egress and secrets can be scoped per environment. Secrets in one environment aren't accessible from any other.

35,346 次观看 • 5 个月前 •via X (Twitter)

8 条评论

Cursor 的头像
Cursor5 个月前

Cloud agents and automations now support multi-repo environments. Configure a single environment with all the repos an agent needs, and reuse it across sessions.

Cursor 的头像
Cursor5 个月前

Starting today, you can run cloud agents inside fully configured development environments. Set them up the same way you'd set up a laptop for an engineer: cloned repos, installed dependencies, and toolchain credentials.

Cursor 的头像
Cursor5 个月前

Customers like Decagon, Amplitude, BILT, and Snyk use development environments to let their agents handle tasks end-to-end. Learn more:

Viktor 的头像
Viktor5 个月前

Hell fucking yeah guys 🎉🎉🎉

Signal House 的头像
Signal House5 个月前

scoped secrets per env is the unlock. when the agent's messaging creds live in the same scope, the loop closes and otp can ship inside the session

VergingAI 的头像
VergingAI5 个月前

Version history + rollback on the env is huge. Half the pain with agent runs is “it worked yesterday, why is it broken now?”—having a diffable, revertable environment makes failures debuggable instead of spooky.

VergingAI 的头像
VergingAI5 个月前

Env versioning + audit log is the difference between “agent got spooky” and “here’s the exact diff that broke it.” Scoped secrets per env is huge too—agents shouldn’t be able to accidentally wander from staging into prod credentials.

Quincy Mitchell 🔭 的头像
Quincy Mitchell 🔭5 个月前

Make me feel more comfortable with secrets and agents.

相关视频