Flox Files

Auto activation

Flox now prompts whether to auto-activate environments in the current directory and parent directories. After an environment is approved, it is subsequently activated whenever the shell enters the directory containing the environment, and it is deactivated when the shell leaves that directory.

Auto-activated Flox environments work just like normal Flox activations, so this provides an easy way to load packages, environment variables, shell aliases, and services all with a single cd.

Auto-activation requires the Flox prompt hook to be installed, which can be done by activating a default environment in your shell's RC files.

For more details, see https://flox.dev/docs/concepts/auto-activation

Authentication changes

• flox can now authenticate with FloxHub personal access tokens. Tokens are generated in FloxHub on the user profile page. To login, run flox auth login --token-file or export FLOX_FLOXHUB_TOKEN
• flox auth login now supports non-interactive authentication via --token-file <PATH>
• flox auth login now stores your FloxHub token in your operating system's encrypted credential store (macOS Keychain / Linux Secret Service) by default, instead of in plain text. On systems without a keyring, it falls back to a 0600 plain-text file and warns you. Existing plain-text tokens are migrated into the keyring automatically and safely. Use flox auth login --insecure-storage to force plain-text storage, and flox auth status to see where your credential is stored.
• flox auth login --insecure-storage is now a persistent preference: the FloxHub token stays in plain text in flox.toml on subsequent commands instead of being moved into the OS keyring on the next invocation. Use flox auth login --insecure-storage --once to store plain text for a single login without changing the preference, and flox config --delete floxhub_token_storage (or --set floxhub_token_storage keyring) to switch back to keyring storage.

Other features and changes

• Users can now trust all environments from an organization with a single config entry: flox config --set 'trusted_environments.myorg/*' trust. The interactive trust prompt also offers this as a one-step option when activating an untrusted remote environment.
• flox activate -D now proceeds when your FloxHub token has expired, instead of forcing a re-login, since the expired token still carries a valid handle.
• Packages installed to an environment that provide Bash script in the etc/profile.d directory now have those scripts sourced on flox activate, in lexical order alongside scripts provided by Flox itself.
• An experimental [plugins] manifest section is now available for storing free-form data for installed plugin packages. It is not yet stable, so its shape may change.
• flox build update-catalogs is deprecated. Catalog inputs for Nix expression builds are resolved and locked automatically during flox build and flox publish.

Fixes

• flox deactivate and auto-deactivation now work when the active environment's directory has been deleted (e.g. a removed git worktree), instead of erroring with "Did not find an environment" on every prompt.
• Fish shell users using auto-activation (cd-triggered) will now see the flox [env] prompt prefix, matching the behavior of interactive flox activate.
• Fixed INFOPATH inside activated environments so info manuals installed outside the environment (e.g. the built-in emacs manual) remain discoverable.
• Deactivating from within a subshell no longer fails with PID XXX is not attached to the activation.

Download Links

• DEB (x86_64-linux)
• DEB (aarch64-linux)
• RPM (x86_64-linux)
• RPM (aarch64-linux)
• OSX (x86_64-darwin)
• OSX (aarch64-darwin)

[!NOTE] You can find the SHA256 checksums for Flox 1.14.0 and SHA512 checksums for Flox 1.14.0 online.