Vibe Check: Sandboxing, Skills, and Surviving Dev to Prod with Temporal

Flox CPO James Bayer joins Temporal's Vibe Check hosted by Melanie Warrick and Cecil Phillip to talk about reproducible software environments, sandboxing your AI agents, and why you should treat skills like software. James gives a live, unscripted demo running the same Temporal environment three ways — directly on macOS with no containers, inside a Docker dev container, and inside Apple's new per-container micro VMs from WWDC — all from a single `flox activate`. Along the way he digs into keeping Claude Code and skills consistent across a team, secrets management, package and skill firewalls for supply-chain safety, and how Flox uses the Nix ecosystem to guarantee the same environment on your laptop, in CI, and in production. Flox separates packaging your software from isolating it, so the same environment runs the same way everywhere — Mac or Linux, x86 or ARM, bare metal or container. Topics covered: Reproducible environments with Flox, separating software packaging from isolation Running one environment three ways: bare macOS, Docker dev container, and Apple Container microVM Default environments and the manifest.toml for keeping utilities consistent everywhere Sharing environments across a team through hub.flox.dev Treating AI skills as software, with roughly 25% shipping with vulnerabilities Registering the Temporal skill with Claude and running a live workflow build Secrets management patterns with Keychain, 1Password, and Vault Package and skill firewalls, plus cross-platform portability across x64, ARM64, and Windows via WSL2 Resources: Flox: https://flox.dev Flox in Five: https://flox.dev/docs (five-minute getting-started tutorial) Flox Hub: https://hub.flox.dev Flox on GitHub: https://github.com/flox Temporal Validated Patterns: https://temporal.io/resources/validat...