> ## Documentation Index > Fetch the complete documentation index at: https://flox-changelog-flox-flox-v1-16-0.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # 2026 > What's new across the Flox CLI, FloxHub, and extensions New releases, improvements, and fixes across Flox, in reverse-chronological order. Subscribe to the [RSS feed](/changelog/rss.xml) to follow along. ## Flox CLI v1.16.0 *Draft: summarize what changed in [v1.16.0](https://github.com/flox/flox/releases/tag/v1.16.0), leading with what it lets users do rather than what was merged.* ## Commands on the outputs tab The **Outputs** tab on package version and build pages now lists which executable commands each output provides, so you can confirm a package ships the binary you need before installing it. ## Direct sign-in for enterprise SSO Members of an SSO-connected organization can follow a direct link to sign in through their identity provider, bypassing the email-entry screen. ## Run cleanup when the last shell exits The new `hook.on-deactivate` manifest section runs a Bash script once, when the last activation of an environment exits — the teardown counterpart to `hook.on-activate`. See [deactivating environments](/concepts/activation#deactivating-environments). ## Instant re-publish `flox publish` now detects an already-published build before building the package, so re-publishing an unchanged package returns immediately instead of paying for a full build first. ## Tunable auth reminders Quiet the "You are not logged in to FloxHub" reminder with `flox config --set auth_notifications false`. Separately, unauthenticated users now see a warning — at most once every 8 hours — that resolving packages will require FloxHub authentication in an upcoming release; see [go.flox.dev/auth](https://go.flox.dev/auth). ## Also in this release * `flox service` is now an alias for `flox services`. * Variables from `[vars]` behave predictably in repeated and stacked activations, and experimental plugin scripts can now read them. * Clearer errors for package file collisions, for Nix expression builds that can't be parsed, and for packages whose `systems` names a system missing from `options.systems`. After upgrading, exit all current activations or reboot before activating again. See the [v1.15.0 release notes](https://github.com/flox/flox/releases/tag/v1.15.0) for the full list of fixes. ## VS Code extension v1.1.0 The Flox VS Code extension now restarts the extension host more smoothly when a reload is needed, and activation is more reliable: the environment's `PATH` consistently wins on startup, control characters in environment values no longer break activation, and the services view no longer lists the auto-start setting as if it were a service. See the [v1.1.0 release notes](https://github.com/flox/flox-vscode/releases/tag/v1.1.0). ## Self-service SSO setup Organization owners can configure an enterprise SSO connection from the organization **Settings** page — no manual setup required from the Flox team. ## Uninstall packages from the environment page Packages listed on the environment detail page now have a remove button, so you no longer need to navigate to the package detail page to uninstall. ## Clearer activations and prompts Activations now announce the environment they enter, the shell prompt shows just the environment name — including environments named `default`, which you can hide again with `hide_default_prompt = true` — and `flox -q activate` is now silent in every mode. ## Changed defaults * `x86_64-darwin` is no longer an implicit default system, because nixpkgs drops it from LTS releases after 26.05. It stays valid when listed explicitly in `options.systems`, and the current system is always included. * `flox activate` no longer adds the environment's `sbin` directory to `PATH` by default — opt back in with `flox activate --add-sbin`. ## Also in this release `flox search` now accepts terms such as `c++`, `g++`, and terms written in non-Latin scripts, and Flox reminds you to run `flox auth login` when you aren't logged in to FloxHub. See the [v1.14.1 release notes](https://github.com/flox/flox/releases/tag/v1.14.1) for the full list of fixes. ## Personal access token improvements The **Personal access tokens** page now shows a usage counter so you can track how many of your allowed tokens are active. Tokens also carry a unique shortcode — visible in the token list — so you can tell which token is which without exposing the secret value. ## Auto-activation Flox now prompts to auto-activate environments when your shell enters their directory, and deactivates them on the way out — packages, environment variables, shell aliases, and services all load with a single `cd`. See the [auto-activation docs](/concepts/auto-activation). ## FloxHub personal access tokens `flox auth login` accepts personal access tokens generated on your FloxHub profile page, supports non-interactive login via `--token-file`, and now stores credentials in your OS keychain instead of plain text — existing tokens migrate automatically. ## Also in this release * Trust every environment from an organization at once with `flox config --set 'trusted_environments.myorg/*' trust`. * Packages that ship `etc/profile.d` scripts have them sourced on activation. * `flox build update-catalogs` is deprecated — catalog inputs for Nix expression builds now resolve and lock automatically during `flox build` and `flox publish`. See the [v1.14.0 release notes](https://github.com/flox/flox/releases/tag/v1.14.0). ## Organization service accounts Organization owners can create service accounts and manage their tokens from a new **Service accounts** tab on the organization page — issue, list, and revoke tokens without leaving org settings. ## Flox skills v1.0.0 Expert Flox guidance for your AI coding agent: the `flox` skill creates and manages reproducible environments, and `floxify` onboards an existing repo — it detects runtimes, package managers, and services, then writes the manifest so `flox activate` is the only setup a new developer needs. Works with Claude Code, Codex, and any agent supporting the [skills.sh](https://skills.sh) standard. See the [v1.0.0 release notes](https://github.com/flox/flox-skills/releases/tag/v1.0.0). ## Auto-activate improvements Declining the auto-activation prompt is now remembered, re-allowed environments return to their correct position in the activation stack, and the prompt no longer hangs on fish. (Experimental — enable with `flox config --set features.auto_activate true`.) ## Custom catalogs in `flox run` `flox run -p owner/pkg -- ...` now runs packages from custom catalogs using an authenticated download path. See the [v1.13.2 release notes](https://github.com/flox/flox/releases/tag/v1.13.2) for the full list of fixes. ## Run packages without an environment `flox run -p -- ` resolves, downloads, and executes a Flox Catalog package in a single step — no environment required. Packages not in the binary cache, such as unfree packages, build from source automatically. ## Containerize dev or run directly `flox containerize` accepts `--mode` to containerize the `dev` or `run` environment without editing the manifest, and `flox build import-nixpkgs` gains `--stability` to select the nixpkgs revision used for the import. See the [v1.13.1 release notes](https://github.com/flox/flox/releases/tag/v1.13.1). ## `flox deactivate` Leave an active environment and return your shell to its previous state without closing it, plus a new `profile.deactivate` section for scripts that run on the way out. ## Build sandbox levels Manifest builds add `warn` and `enforce` sandbox levels alongside `off` and `pure`, with a `sandbox-allow` list for files outside the build closure. ## Faster, clearer environment operations `flox upgrade` output now separates version changes from same-version rebuilds, `flox activate` skips re-locking environments that are already current, and environment creation uses one `nix build` invocation per build-and-link cycle instead of three. See the [v1.13.0 release notes](https://github.com/flox/flox/releases/tag/v1.13.0). ## Flox CLI v1.12.2 Manifest builds can now use `git describe` to set version strings, `flox publish` no longer triggers unnecessary rebuilds, and debug output gains color highlighting to make slow operations easier to spot. See the [v1.12.2 release notes](https://github.com/flox/flox/releases/tag/v1.12.2). ## Default environment shortcut The `-D`/`--default` flag references your default FloxHub environment in any command that accepts `-r`/`--reference`, replacing `-r /default`. ## Smarter install and publish `flox install ^` now appends outputs to packages that are already installed, and `flox publish` skips the rebuild and publish when the exact build has already been published. See the [v1.12.1 release notes](https://github.com/flox/flox/releases/tag/v1.12.1). ## Sign in with Google or GitLab Two new social sign-in options join the existing GitHub login on the FloxHub sign-in page. ## Services auto-start Configure services to start automatically on activate. ## Build catalog updates `flox build update-catalogs` is now public with full docs. See the [v1.12.0 release notes](https://github.com/flox/flox/releases/tag/v1.12.0). ## Package outputs on FloxHub Browse and select package outputs on version and build pages on [FloxHub](https://hub.flox.dev/packages). ## Package deprecation notices FloxHub shows deprecation info in search results and on [package detail pages](https://hub.flox.dev/packages). ## Environment SBOMs Export SPDX and CycloneDX compliance documents for your environments. ## CUDA 12.6 support First-class GPU toolkit support in the catalog. [Read more](https://flox.dev/blog/deploying-hardened-flox-nvidia-cuda-stacks-in-minutes-not-hours/). ## Improved search Package search is now 5x faster. See the [v1.10.0 release notes](https://github.com/flox/flox/releases/tag/v1.10.0). ## Package version and build detail pages Each package in the [FloxHub catalog](https://hub.flox.dev/packages) now has dedicated pages for its version history and individual builds, so you can see exactly what was built and when. ## Dark mode FloxHub now supports light, dark, and system-preference themes, toggled from the navigation bar. ## Package group conflict visibility When a package group has a version conflict, FloxHub now highlights which specific package is holding the group back. ## Kerberos auth preview Enterprise on-prem authentication, in preview. See the [v1.9.1 release notes](https://github.com/flox/flox/releases/tag/v1.9.1). ## Pin package versions A pin control on the package detail page lets you lock a package to its current version or remove the pin. ## Node version detection Flox auto-detects `.node-version` files. See the [v1.9.0 release notes](https://github.com/flox/flox/releases/tag/v1.9.0). ## VS Code extension Manage Flox environments from VS Code. [Read more](https://flox.dev/blog/reproducible-dev-environments-in-your-workflow-with-flox-and-vs-code/). ## FloxHub without an account Browse the Flox catalog and view public environments on [FloxHub](https://hub.flox.dev) without signing in. ## Install and uninstall from the package page Install a package to an existing or new environment directly from its detail page, and uninstall from within the install dialog. ## "In use" chips in search results Packages already installed in one of your environments show an "In use" badge in catalog search results. ## Weekly and monthly upgrade cadence Automated environment upgrades can now run weekly or monthly, in addition to the existing daily option.