This is an interesting direction for “open” tooling. Combining containerization (Docker) with reproducible environments (Nix) addresses two of the biggest pain points in developer workflows: environment drift and opaque build/runtime assumptions. Running everything inside a container gives isolation and portability, while Nix provides declarative, deterministic dependency resolution that Docker alone doesn’t solve well. The result is closer to a truly reproducible dev and execution environment, which is especially valuable for CI, code review, and long lived projects. The real test will be how approachable the Nix layer is for non experts and whether the abstractions stay transparent rather than becoming another black box. If done right, this could reduce a lot of “works on my machine” overhead without requiring teams to fully buy into heavyweight orchestration or custom infra.

I would contend the nix ecosystem is sloppy, 3 of the primary projects I use are wrong for various reasons. I'm not really sure what's here beyond a prebuilt image with nix and open code, is there?

Can this be adjusted to give the agents access to environments rather than being boxed into them. You want their exec's and fs work boxed in, and likely you also want them to use multiple agents in multiple envs, or have a single agent leverage multiple envs (i.e. with different permissions available for different tasks). You also likely don't need a full on env when you are making an API call with the right secrets