Where Does hut Store Config and Tokens?
hut reads instance tokens from ~/.config/hut/config on Unix (~/Library/Application Support/hut/config on Mac), plus .hut.scfg per repo.
Last updated
hut keeps account credentials in one config file and project associations in the repos themselves. The user config names sr.ht instances with OAuth tokens (or token commands like pass). The .hut.scfg file in a repository records its tracker and list so commands resolve context automatically.
That split keeps tokens out of repositories entirely. Copy the user config to a new machine and every hut command works; the per-repo files travel with clones through git itself. The --config flag overrides the user file location for testing.
Where hut stores this, by platform
~/.config/hut/config
Instance blocks with access tokens or token commands. Respects XDG_CONFIG_HOME when set. Guard this file; its tokens act as your account on every configured instance.
~/Library/Application Support/hut/config
Same config role on macOS under Application Support. Per-repo .hut.scfg files work identically across platforms since they live inside the repos.
Frequently asked questions
hut rejects my credentials. Where do I check?
Open the hut config file and check the instance block. Tokens live per instance name, and --instance selects among them. A wrong token presents as authentication failure, not a missing-file error.
How do I pin a tracker to a repository?
Add a .hut.scfg file at the repo root naming the tracker and mailing list. hut commands then default to those resources instead of demanding flags every time.
Notice an outdated path? Let us know.