Docker Sandboxes aren't containers; they are based on on microVMs with their own kernel. but they aren't just rebranded microVMs either. they have a secret manager, and your agent only ever sees a placeholder token.
macOS 27.3 scoping full disk access to specific folders is overdue. the "ask each time" option is kinda funny for agents though, nobody is at the keyboard at 3am to click allow. one more reason to give them their own macOS VM
verifying is the hard part and most teams still point the same agent at both. the one that wrote the code also wrote the tests, so of course they agree. i run throwaway agents with no memory that break the code on purpose, just to see if the tests notice
What does software engineering look like when generating the code becomes cheap and verifying it is the hard part? A rare podcast focused on everything around building software, with @satyanadella. Timestamps:
00:00 Intro
02:12 Microsoft’s open-source shift
04:15 Building VS
codex desktop in full access mode once sent slack messages with my name without asking me. that is on me, but a lot of devs run it like that. the agent needs its own box, not your session
Linux containers share a kernel. Docker Sandboxes don’t.
Docker Captain @yagcidev shows how your coding agent gets its own microVM, Linux kernel, and Docker Engine, with limits on what it can reach on your machine.
Read more: bit.ly/4eFXkDT