Nixmac

nix-darwin is one of those things i keep hearing is worth it but never actually get around to learning because the config syntax scares me off every time. this is the first "plain english to nix" pitch that's made me want to actually try it instead of just bookmarking it. since it applies changes for you, does it keep the old generation easily reachable if a plain english request builds something you didn't actually want, or do you have to know nix well enough to roll back yourself

Setting up a new Mac has always been my least favorite afternoon, hunting down settings I only half remember. Cooper, being able to simply say what I want and having a way to redo it later sounds genuinely freeing.

Since nix-darwin setups often need to manage secrets like SSH keys or API tokens, does Nixmac integrate with something like agenix or sops-nix, or is that left entirely up to the user?

I run a laptop plus a Mac mini I use for local model work, and config drift between the two is exactly the kind of thing Nix is supposed to solve but plain-English descriptions make me wonder about. If I describe a setup in English on one machine, is the generated config meant to be portable to a second machine as-is, or does Nixmac bake in host-specific assumptions (hardware, installed apps) that I'd need to redo per machine? Basically: is the "plain English" step a one-time per-machine thing, or does it produce something closer to a shared base config with per-host overrides layered on top?

The plain-English layer over nix-darwin sounds interesting. Is Nixmac mainly meant for generating an initial macOS config from natural language, or does it also help maintain and edit an existing nix-darwin setup over time? I’m curious how much control it exposes when someone wants to inspect or tweak the generated config directly.

The plain-English → generated Nix → safe-apply loop is the right shape for the people Nix usually scares off, but the safety hinges on what I can see before it runs. Does it show the generated Nix diff for review before applying, and is each apply a rollbackable nix-darwin generation I can revert if a vague request compiles to the wrong thing? Curious how it handles an ambiguous request — ask to clarify, or guess and let me roll back?

The hard part of nix-darwin isn't writing the initial config, it's understanding why a rebuild failed three weeks later when you've forgotten what you changed and the error message is a wall of Nix evaluation trace. Curious whether Nixmac helps with that debugging side, or whether it's mostly focused on the generation step. Also wondering how it handles the gap between what someone asks for in plain English and what's actually available in nixpkgs or the darwin module set, since a lot of the friction in practice comes from options that exist in theory but have subtle constraints you only discover by reading the source.

Tried it on my M2 and was surprised how the natural language description actually translated into clean nix code without me editing anything. The dry-run build before applying was a nice touch for someone who breaks their config weekly.

Curious how it handles apps you download outside of Homebrew or the App Store, like random .dmg utilities, can Nixmac pick those up or do you have to manually add them to the config?

Initially my personal shell script, I saw how it could replace me as the de facto person they go to for help with "tech stuff". I especially think it's neat because Nix is considered to have a high learning curve, yet is the perfect tool for those that could be considered the least tech savvy.