/m/.
You can inspect configs, tokenizers, and READMEs without downloading the
weights, weights stream only when you actually cat them.
For credential setup, see HF Models Setup.
Install
Config
Reading, not writing
This mount is read-only, the way agithub mount is. A Hub write is
a commit, and a POSIX write cannot say where a commit ends, so echo >,
rm, cp and mv are refused here rather than silently making one commit
per file. The hf CLI is the write half: hf download --local-dir
puts a copy on a ram or disk mount, which is an ordinary writable filesystem,
and hf upload sends it back as a single commit.
Filesystem Layout
Maps model repo files (config, tokenizer, weights, etc.) to virtual paths. For example,sapientinc/HRM-Text-1B mounted at /m/ exposes:
Example
Shell Commands
Every read command in HF Buckets’ set works here, as do the text processing and path utilities, which only read. What does not is the File Operations group: this mount is read-only, sorm and touch are refused, as is any command asked to write into it.
Use Cases
- Model card inspection: Read configs, tokenizers, READMEs without pulling multi-GB weight files
- Compatibility checks:
jqoverconfig.jsonto verify architecture before committing to a download - Pinned revisions: Mount a specific commit/tag for reproducibility