Nushell

For managed Nushell deployments, treat the shell configuration files as part of the package design rather than relying only on the executable. The Nushell configuration guide documents explicit startup flags: use nu --config <file> for an alternate main config and nu --env-config <file> for an alternate environment config. It also documents launch modes such as nu --login and nu --commands <commands>, which are useful for smoke tests, automation jobs, and staged rollouts where a packaged default config must be validated before it is copied into user profiles.

On Windows, avoid hard-coding a guessed profile path in detection or remediation scripts. Nushell exposes its effective config directory as $nu.default-config-dir, and the configuration docs also describe vendor autoload folders under that config tree for application-provided scripts. If an enterprise package deploys shared completions, modules, or policy-like defaults, verify them by launching nu --config/--env-config with the exact files you are staging, then let user-profile remediation place the files under the resolved Nushell config directory.

Source: Nushell configuration documentation.