We’re at #NixCon2026 ❄️ The booth is up, the Flox team is here, and we’re super happy to be spending the next few days with the #Nix community in Kraków. Come say hi, talk Nix, grab some swag, and hang out with us! See you around! 😎

Just wrapped up an amazing day at @WeAreDevs with a Lego Salon collab event with @floxdevelopment @apify and @runpod . So many people came out to have fun after the conference building Legos, chatting up what they saw, and cheering on our 3 winning groups. So much fun, everyone!

Every NixCon, the same feeling: so excited I can barely sleep. 😄

We’re coming to NixCon 2026! We’ll be in Kraków from September 25–28 to catch up with the #Nix community and share what we’ve been working on. Come say hi at our booth, grab some swag, and catch the Flox team on stage: 🟣 @ronefroni Nix State of the Union 2026 and Nixing Artificial Intelligence 🟣 Yannik Sander: Adding to the Pile, or How to Extend nixpkgs 🟣 @garbas Flox lightning talk See you in Kraków! Full schedule: buff.ly/UR2zBC4

Flox v1.16 is out, with two additions: `flox run` and a new plugin system for secrets management. `flox run` lets you run packages from the Flox Catalog without creating an environment or installing anything: `flox run jq` Flox resolves the package that provides the command and runs it on-demand. If multiple packages provide the same command, you can select one and Flox will remember your choice. Or you can specify it explicitly with `--package`. This is especially useful in CI: `flox run --package python312 -- python hello.py` The new secrets plugin system provides pre-built integrations with 1Password, HashiCorp Vault, OpenBao, Infisical, and other providers. Secrets remain with the upstream provider; Flox retrieves + makes them available in the environment at activation. No custom logic required. Learn more about `flox run` and secrets management with Flox plugins 👉 buff.ly/FdFbDLN

Wrapping @DevOpsDaysPDX 2026! TL;DR: the platform work you've already done is what saves you when AI hits your pipeline. Best talk for me: Daniel Sauble's Nix ignite. Containers fix reproducibility yet wreck DX. Nix fixes both, down to glibc. Also got to meet the Flox folx IRL!

Starting to write up the NixOS State of the Union, what do you want to talk about?

Happy to show you what are we cooking at @floxdevelopment ... Would also like to learn what are you current problems to make sure we fix them for you.

“Skills are software” There’s a great discussion about agents in this @fallthroughfm episode with @ronefroni and @jambay. A skill might start as a Markdown file, but it can also rely on scripts, packages, runtimes, MCP servers, and other resources. And those dependencies change. So the same agent can behave differently depending on where or when it runs. James shares an example of a company using Flox to capture the full environment behind its agents. If something goes wrong, they can recreate the exact set of tools, dependencies, and runtime the agent was using, reproduce the failure, and see what happened. We’re still figuring out a lot about how agents will change software development, but making the environment around them reproducible feels like a pretty useful place to start. Lots more in the full episode. Thanks to @sudomateo and @skriptble for having us! Watch here: buff.ly/ClOSMPu

The Go podcast let us hijack an episode to talk about Nix n Flox. 😅 (❤️ @sudomateo & @skriptble) Dug a bit into.. Why Nix can feel hard. Why there's 5+ paths for every goal. Bringing Nix to work. And what we are cooking at @floxdevelopment #NixCon very soon ;) #NixOS

GO Podcast where we chatted @nixos_org complexity and also @floxdevelopment (disclaimer : we do dive into Flox and a lot of opinionated happy paths in it) - fallthrough.skriptble.press/…

The faster agents build, the less tolerance there is for inconsistency in the environments where they work. Reproducibility is what ensures that AI agents always build, test, and debug in exactly the same environment. Reproducibility also ensures that what they build is portable, reusable, and trustworthy at runtime. In the clip below, @ronefroni explains why reproducibility becomes more important as AI-generated code accelerates. Captured at PlanetNix 2026.

Nix is the way, it's the correct substrate for a lot of projects and potentially for Omarchy Cinque. A lot of folks seem to be mentioning what we've built over at @floxdevelopment. No nixlang. Built with Rust. Happy to volunteer and get Nix into more hands here.❄️

@jambay demo'd the new @floxdevelopment Determinstic Agentic Stacks side by side with our friends at @inngest , @nebiusai , and @MiniMax_AI. Shoutout to our friends at @UnikraftCloud who swung by and are geniuses behind some incredible MicroVM speed! #nixos

Join us for the AI in Production meetup next Tuesday at 6pm at the Inngest HQ in San Francisco! Our CPO, James Bayer, will be joining Mitchell Anderson from Inngest and Sujee Maniyam from Nebius for an evening of talks, demos, and conversations about what’s actually working (and what isn’t) when AI moves past the prototype stage. If you’re building with AI agents, infrastructure, models, or anything else that needs to survive beyond experimentation or prototyping, come and hang out! luma.com/inngest-77ls

The AI in Production Meetup is back! Our friends at @nebiustf and @floxdevelopment are joining us in the Inngest loft to chat about what they're building, what broke, and how they keep production code secure, scalable, and.... idk, savage? → 6 PM food & networking → 6:30 PM lightning talks with Q&A Our gorgeous space was completely at capacity last time, so register ASAP: luma.com/inngest-77ls

Flox is growing! Welcome to the team, Justin, Alan, and David 👋 Justin joins us as DevRel Lead, helping us create useful technical content and build stronger connections with the developer community. Alan joins as an AI-First Engineer, bringing experience from BlinkRx, DoorDash, and Slack, and a focus on making AI part of how engineering teams actually build and ship software. David also joins the engineering team, bringing experience across mobile, backend, developer tooling, infrastructure, and AI. We’re excited to have you all on board. Let’s go! 🚀

Try @floxdevelopment. It's cool.

Today we're announcing two new credential types for FloxHub: Service Account Tokens and Personal Access Tokens. Purpose-built credentials for people and machines. - Service Account Tokens: org-owned, scoped, expiring, instantly revocable - Personal Access Tokens: your access in SSH, containers, and CI Full writeup: buff.ly/V8BG1CF

Auto-activation is here for Flox environments. cd into a directory with a .flox folder and the environment turns itself on. Leave, and it turns off. Nested environments and services come along automatically. Your environments become one less thing to think about: they handle themselves so your workflow keeps moving. Read the full post here: buff.ly/6zCiCnu Services in more detail: buff.ly/bIOjfzO