Indeed. Maybe autoconfiguring the child nix process is debatable, but at least nh should show a warning.

I'm looking at adding this in, is running nix config show and parsing out the JSON a good approach for reading the experimental features?

Yeah, I was thinking the same. It shouldn't add much overhead, and there's no need to parse the whole json, just what we need

So there seems to be an issue with this approach: I am running Lix 2.92 and they seem to have changed the command to return a bit enum of the experimental features, while Lix <2.92 and Nix just return an array of the enabled features.

After further consideration, I don't think that it is worth it to add a check within the code, maybe some sort of FAQ entry about this is the best approach?