Where Does Pants Store Config and Cache?
Pants reads pants.toml in the repo root and caches builds in ~/.cache/pants, with pantsd state beside it.
Last updated
Pants keeps repo config in pants.toml files committed with the code, while the heavy cache lives outside the repo in the user cache home. The pantsd daemon adds its own state and logs beside the cache.
Wiping the cache is always safe and only costs rebuild time. Repo config travels with git checkouts, so fresh clones behave identically without any machine setup beyond the bootstrap script.
Where Pants stores this, by platform
~/.cache/pants
Build cache plus pantsd state and logs. Repo config in pants.toml at the root. Clear the cache folder to force full rebuilds when results look stale.
~/Library/Caches/pants
Same role on Mac. The bootstrap pants script in the repo pins the Pants version, so cache formats stay consistent per checkout.
Frequently asked questions
how do i clear the pants cache
Stop pantsd and delete the pants cache folder for your OS. Next run rebuilds everything from the repo config, slowly but correctly.
where is pants configured
In pants.toml at the repository root with optional per user overrides in ~/.config/pants. Machine specific paths belong in the user file, never the committed one.
Notice an outdated path? Let us know.