Video yükleniyor...
Video Yüklenemedi
Your agent is reading that .env file and it's maybe fine... until the agent misunderstands you and deletes the production volume (catch my video telling that story). Let me show you how to make that impossible while still making your agent usefully autonomous.
14,876 görüntüleme • 15 gün önce •via X (Twitter)
7 Yorum

if I have to manage my agent then it isn't worth it and I'll just do the work myself. My agent's have access to everything I do, I'll probably regret it one day but for now, weeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee!

This is exactly why agents need to understand the codebase before they act. Knowing what a ".env" file is isn't enough. They need to understand what depends on it, what’s production-critical, and what changes are actually safe. That’s the problem I’m working on with Rune.

Exactly why we are building @stashbase :)

On YouTube:

agent can read .env until it "helps" by deleting prod that's the day-one autonomy trap most people ship open

La clave no es que el agente "entienda" que no debe tocar prod, es que la accion irreversible no pueda ejecutarse sin confirmacion explicita -- sandboxing estructural, no confianza en el juicio del modelo. Autonomia util = reversible libre, irreversible siempre gateado.

Sounds like you need varlock! I know you have a lot of this implemented within Kody… but probably some nice ways to integrate. Will have a look.

