正在加载视频...
视频加载失败
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 条评论

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.

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.

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

Hell fucking yeah guys 🎉🎉🎉

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

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.

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.

Make me feel more comfortable with secrets and agents.


