Hugging Face Hub 2.4.0 adds file-copying support for Buckets and several practical fixes for its command-line tools. For AI teams moving datasets and models around the Hub, Xet-backed files can now be copied between Buckets without being downloaded first.
Hugging Face Watch analysis
What happened
The update covers HfFileSystem, the Hub CLI, webhooks and cache verification. Hugging Face’s v2.4.0 release notes say copying into a Bucket now works from the same Bucket, another Bucket, or a model, dataset or Space repository. Copying from a Bucket back to a repository is not supported yet.
The release also adds extension-version checks and allows hf extensions update to recreate an extension’s virtual environment when its Python installation no longer starts. Other fixes include clearer authentication advice for private repositories and rejecting cache filenames that could escape the cache folder through path traversal.
Our top picks
- Copy files into Buckets
Copying now works from Buckets and Hub repositories; Xet files are copied by hash without being downloaded. - See which CLI extensions are outdated
hf extensions list shows installed and latest versions, with checks limited to once a day. - Repair broken Python extensions
The update command can recreate an extension’s virtual environment when its Python installation has stopped working. - Get a more useful private-repo error
The Hub now suggests checking authentication when access without a token looks like a misspelt repository name. - Block cache path traversal
Cache filenames containing ../ or absolute paths are rejected instead of resolving outside the cache folder. - Make webhook creation less fussy
Creating a webhook without specifying a domain now watches both supported domains, including discussions.
Why it matters
These are not new model capabilities, but they smooth out the plumbing around models, datasets and developer workflows. The Bucket changes are the standout: Xet files can move on the Hub by hash, while other repository files still need to be downloaded and uploaded. The release draws a clear boundary too: copying from a Bucket back to a repository is not available yet.
The CLI fixes are the sort of maintenance people notice most when they are missing. Extension status is easier to check, a broken environment can be repaired, and a private-repository authentication problem gets a more helpful nudge than “repository not found”.
Our read
This is a worthwhile infrastructure release: less faffing with file transfers, fewer dead-end CLI errors, and one useful cache-safety fix. Teams using HfFileSystem or Hub extensions have concrete reasons to look at the upgrade. Just check the copy direction you need before building a workflow around Buckets; this road is not yet a two-way street.
What to watch
- Whether later releases add copying from Buckets back to repositories.
- How the once-daily extension checks behave for teams managing many extensions.
- Whether the cache and webhook fixes resolve the reported edge cases in real workflows.
Discussion spark: Would you move dataset workflows to Hub Buckets now, or wait until copying back from a Bucket to a repository is supported?
Sources and evidence
- [v2.4.0] Copy files into Buckets with HfFileSystem, outdated CLI extension hints (29 October 2026, 15:29 UTC)
not affiliated with or endorsed by Hugging Face