While testing Forge on Linux I noticed a couple of behaviors:
- Forge automatically creates a
~/forge folder to store its data
- Inside repos, Forge also creates a
./plans folder automatically
Using these locations is bad etiquette for Linux programs, especially with no confirmation or option to change via config (not that I could find in the docs anyway).
The preferred locations for storing user scoped files are ~/.config and ~/.local.
For per repo files, a single dot folder can cleanly tuck away most files (compare to .git). The main exception there would be files that go under version control, such as AGENTS.md or similar.
While testing Forge on Linux I noticed a couple of behaviors:
~/forgefolder to store its data./plansfolder automaticallyUsing these locations is bad etiquette for Linux programs, especially with no confirmation or option to change via config (not that I could find in the docs anyway).
The preferred locations for storing user scoped files are
~/.configand~/.local.For per repo files, a single dot folder can cleanly tuck away most files (compare to
.git). The main exception there would be files that go under version control, such asAGENTS.mdor similar.