Where Does Breezy Store Config?
Breezy layers config from ~/.config/breezy (breezy.conf, locations.conf, authentication.conf) over per-branch .brz/branch/branch.conf.
Last updated
Breezy keeps three global files with cleanly divided jobs. The breezy.conf file sets defaults and aliases, locations.conf overrides per branch path with wildcards, and authentication.conf isolates credentials so one file carries the strict permissions.
Branches add their own layer through .brz/branch/branch.conf, visible to everyone sharing the branch. Personal overrides for shared branches go in locations.conf, never in the branch file. The brz version command reports the config root when layouts differ by platform.
Where Breezy stores this, by platform
~/.config/breezy
breezy.conf for defaults, locations.conf for per-branch overrides, authentication.conf for credentials. Per-branch .brz/branch/branch.conf sits below globals in precedence. Guard the auth file's permissions.
~/.config/breezy
Same trio on macOS under XDG config home. Legacy ~/.bazaar paths belong to older Bazaar installs; Breezy reads its own folder and never the old one.
%APPDATA%\breezy
The Windows equivalent of the Unix config dir. Branch files keep forward-slash .brz paths on all platforms, so checkouts move across OSes cleanly.
Frequently asked questions
Which file wins for one branch?
Check locations.conf first, then the branch's branch.conf, then breezy.conf. Location-specific sections beat branch files, which beat globals. brz config prints the merged result per option.
How do I migrate Breezy settings?
Copy the .config/breezy folder with tight permissions on authentication.conf. Branch checkouts carry their own branch.conf already, so the global trio is the only migrant.
Notice an outdated path? Let us know.