huggingface_hub is not legacy | Generated by AI

Home 2026.06

Question: Is huggingface_hub legacy now? Is hf the latest CLI? (I have hf --version → 1.12.0)

Answer:

Not legacy — you’re conflating two things. huggingface_hub is the Python package, and it’s very much current. hf is just the new name for its CLI entry point, which ships inside that same package.

What actually changed:

So:

pip show huggingface_hub   # this is what hf --version reports
hf --help                  # new CLI (huggingface-cli still works but warns)

The new syntax is hf <resource> <action>:

hf auth login              # was: huggingface-cli login
hf download <repo>         # was: huggingface-cli download <repo>
hf upload <repo> <path>    # was: huggingface-cli upload
hf auth whoami
hf repo create <name>

In Python nothing changed — you still import the same thing:

from huggingface_hub import HfApi, snapshot_download, hf_hub_download

Worth verifying the exact rename timeline and which version flipped the default, since CLIs like this move fast and I shouldn’t guess from memory:Confirmed by the sources — and your 1.12.0 tells the whole story:

So: huggingface_hub = the library (current, you’re on 1.12.0). hf = its CLI (current). huggingface-cli = the dead name. You’re fully up to date.

Quick reference for the commands you’ll actually hit on the sec-edgar GPT work:

hf auth login
hf download <org>/<model>           # pulls weights/tokenizer
hf upload <org>/<repo> ./out        # single-commit
hf upload-large-folder <repo> ./ckpt  # resumable, for big checkpoints
hf cache ls --filter "size>1GB"     # new v1.0 docker-style cache mgmt
hf jobs run --flavor a10g-small ...  # run scripts on HF hardware

One env var worth setting on your MI300X box to kill the startup auto-update check in non-interactive runs: export HF_HUB_DISABLE_UPDATE_CHECK=1.

References:


Back Donate