Making Flox Better for People and Machines

This week we shipped Flox v1.14.1, which focuses on making Flox more consistent, reliable, and easier to use as you work in your environments.

So, for example, Flox now tells you which environment you’ve entered, along with whether you activated it directly, in-place, or via auto-activation. Shell prompts that previously showed chatty labels (like owner/name (local)) now show just the environment name, while flox -q activate is now genuinely quiet: it no longer prints activation traces to the terminal. The flox search command also accepts common terms it used to reject, including c++, g++, and terms encoded in non-Latin scripts.

The v1.14.1 release also gives you better visibility into what’s happening as environments change or move between systems. For instance, updating and re-locking an older environment could sometimes result in packages being silently dropped; Flox now warns you when that happens. And if an environment has been locked to a different platform (e.g., Apple Silicon-based macOS) and can’t run on your system (e.g., x86 Linux), Flox now surfaces this error and tells you which platforms it will run on. We also made improvements to both activation and auto-activation, so environments behave more consistently as you auto-activate and/or move between shell sessions, or work with remote FloxHub environments.

Serving Both People and Machines

If you just use the Flox CLI, you might not know you depend on FloxHub, but you do: Whenever you search for packages, install or upgrade software, or resolve dependencies, FloxHub does that work. We’re committed to bringing this same focus on reliability, consistency, and ease-of-use to the FloxHub services that back the Flox CLI, too.

For example, Flox v.1.14.0 shipped with support for personal access tokens (PAT) and service account tokens (SAT). Both give the Flox CLI a way to authenticate to FloxHub without an interactive login: PATs represent individual users, while SATs give CI, agents, and other automation their own FloxHub identity and access level.

As more developers, CI systems, and (especially) AI agents use Flox to search for and resolve packages, we need the ability to protect the service from abusive or runaway automation, and keep resolution responsive for everyone. This week’s v1.14.1 release starts to lay the groundwork for that. Check out https://go.flox.dev/auth to learn more about which commands will need authentication.

Although we're encouraging authentication, FloxHub sign-up is completely free. Free-tier users will continue to enjoy access to all free features and benefit from future improvements we ship in the Flox CLI. And because many CLI workflows depend on FloxHub, free-tier users will also benefit from better support and a faster, more available experience as we invest in the parts of the service that people and machines are using most heavily.